Paolo Insogna

Come la vedete voi? C'è un post su #HackerNews che mi ha fatto pensare... Hi. I've been in the profession (SW Eng) for about 18 yrs now. A few years from my 50s. Didn't go the managerial route. Stayed technical. My current gig is in a very difficult and complex project written in C. Been there for 2 yrs now and I'm afraid that due to the ancient tech stack and despite being a good engineer I'm loosing my marketability. After enduring bad behavior for nth time (yeah it's a toxic workplace) I decided I had enough and did a round of applications. Mostly for backend positions and mostly for golang positions. I don't have prod xp with golang but it's close to C and every time I've used it it seemed ok. But the problem is that I'm either being ignored or skipped over. All jobs are for seniors in the _specific_tech_stack_. Other positions I've applied for and got no response whatsoever are architects, tech managers and the like. Granded, this regards a turd job market (EU/Greece) but still that's where I am at. Am I toasted for good? I mean, nearing my 50s with my most recent gig writing "C" on it is as good as declaring my career over? Link nel primo commento...

14

16 commenti

Claude 3.5 Sonnet has been my main driver for Cursor in the last few months and last night it seemed like it just got BETTER. Then I saw this today, indeed it was upgraded in coding in particular! But more exciting is this: > Available today on the API, developers can direct Claude to use computers the way people do—by looking at a screen, moving a cursor, clicking buttons, and typing text 🫠 https://lnkd.in/grGXiyev

5

1 commento

Frontend development isn't easy! It is like a marathon and not a sprint. To truly excel, you need to focus on several key areas: * Optimizing Load Times: Fast websites keep users happy. * Creating Reusable Components: Write once, use many times! * Writing Semantic and Accessible HTML: Make your sites user-friendly for everyone. * Crafting Beautiful, Maintainable CSS: Style matters, but so does clarity. * Developing Performant, Organized JavaScript​: Smooth functionality keeps your app running well. * Ensuring Cross-Browser and Device Compatibility: Your app should work everywhere! * Testing and Debugging: A reliable app is a well-tested app. * Understanding User Experience (UX): Create intuitive designs that users love. * Implementing Effective SEO: Help users find your applications easily. * Staying Updated with Trends: The tech world changes fast-keep learning! Remember, progress takes time and effort. Love the journey, challenge yourself, and strive to improve every day.

3

1 commento

29 years ago - press release announcing JavaScript! https://lnkd.in/eHCyiwx2 -------------- How it started: --------------- ☕ 1995: JavaScript, built in 10 days by Brendan Eich, was meant for simple browser interactions. 📜 A humble language mocked as a “toy,” meant for enhancing web pages with basic scripts. --------------- How it’s going: --------------- 🚀 2024: JavaScript is everywhere — web, servers, mobile, and even the desktop! 🌍 97% of websites run on JavaScript. 💻 Revolutionized backend development with Node.js. 📱 The foundation of modern apps through React, Angular, and Vue.js. 🖥️ With Electron.js, JavaScript now powers desktop applications like Slack, VS Code, and Discord — bridging the gap between web and desktop. 🌟 Its influence reshaped the landscape, inspiring other scripting languages. #JavaScript #WebDevelopment #DesktopApps #TechInnovation

24

2 commenti

Monte Carlo programming is amazing. I remember how we used to laugh at some developers who implemented things in a Monte Carlo style: making random changes until testers discovered their latest change actually worked. Today, I write a short piece of text, run it through AI, and request a few changes until the provided code more or less works. Many claim this is actually the future of programming. However, there are several challenges with this approach: one is anonymization. You have no right to send your customers' code to external services. In some cases, though, it's sufficient to anonymize the code and test it. I have written code and published it on my page, so you can: - mark words manually, - apply common patterns, - perhaps one day use local AI to replace sensitive words with alternatives. When AI provides you with the response, you can simply translate it back to get your target code. I will definitely still need to make a few revisions (draws) to improve the code's description, functionality, and appearance, but for now it has served its purpose: it has proven that Monte Carlo Programming has its place.

5

2 commenti

🚫 Stop Over-Engineering! Why You Should Embrace the YAGNI Principle in Software Development 🚫 In software development, it's easy to fall into the trap of building for future needs that may never arise. The YAGNI principle (You Aren’t Gonna Need It) challenges this mindset by encouraging developers to focus on current requirements and avoid unnecessary complexity. In my latest article, I discuss: 🛠 What the YAGNI Principle is and how it promotes simplicity in code. ⚖️ Why over-engineering happens and how YAGNI helps avoid bloated, difficult-to-maintain systems. 💡 Practical examples of how to apply YAGNI in your projects, including a hands-on JavaScript code comparison. 🚀 How following YAGNI can lead to faster delivery, reduced technical debt, and easier code maintenance. Before adding that "just-in-case" feature, remember: You Aren’t Gonna Need It! 🔧 👉 Read the full article here: https://lnkd.in/dUQ_xWXu #SoftwareDevelopment #YAGNI #AgileDevelopment #CodingBestPractices #CodeSimplicity #TechLeadership #SoftwareEngineering #LeanCode

7

Great post series about DDD and JPA I have really enjoyed reading these posts: https://lnkd.in/dNE__8aC I am an strong follower of DDD. However, when it comes to implement persistence, there is always a mismatch. And you must evaluate some trade-offs. Mostly when you are using a RDBMS. It doesn't matter the language, the framework or the ORM framework. This series of posts offers valuable thoughts and suggestions how to address this mismatch when using JPA.

5

🚀 Unlock the Power of C4 Model Diagrams! 🚀 Hey #Developers and #Architects! 🛠️ Are you looking to elevate your software architecture game? Check my latest article on the C4 Model! 🌐 🔍 This article can be particularly useful for Software Architects, Tech Leads, and everyone who wants to have a clear view of the architecture of a system 📚 4 Topics you will find in my article: 1️⃣ Overview of the C4 Model: Learn the basics and why it’s a game-changer for software architecture. 2️⃣ Install and use Structurizr on Windows (with Docker): Understand how to run Structurizr in any system that can use Docker. 3️⃣ Step-by-step guide: Understand how to visualize your system’s modules and their interactions using Structurizr's DSL. 4️⃣ Practical Tips with Structurizr: Get hands-on advice for creating C4 diagrams using Structurizr. Don’t miss out on this insightful read! 📖✨ #SoftwareArchitecture #C4Model #TechLeadership #Coding #Structurizr https://lnkd.in/dWvWKF_D

12

For my C# Advent 2024 entry I prepared a short example on how to build a simple Bluesky Social client in Uno Platform! #csharp #dotnet #csadvent #csharpadvent

10

🐧 The Error Management Trio: what many Software Architects often neglect! 🐧 Hello, fellow developers and tech enthusiasts! 👋 I just published a new article on my blog, and I can’t wait to share it with you. It’s all about the Error Management Trio and how it can significantly impact your software architecture. 🛠️ (Yeah, I came up with that name, and yeah, I'm not good at finding catchy acronyms or names!) 😅 In this article, we'll talk about: 1️⃣ Data Validation: The first line of defense against invalid data. 2️⃣ Transient Errors: Handling those pesky temporary issues. 3️⃣ Fatal Errors: Strategies for when everything goes wrong. 4️⃣ Practical Approaches: Real-world examples and solutions. 5️⃣ Architectural Impact: How each type of error affects your system design. Don’t miss out on these insights! Dive into the article, and let’s discuss how you handle errors in your projects. 💬 #SoftwareArchitecture #ErrorHandling #DataValidation Read the full article here 👇 https://lnkd.in/dn8i2EiE

8

Every iOS developer knows the pain of CoreData. Last year, Apple introduced SwiftData. If you are interested in learning it, this post marks the beginning of a short series about it. In this first episose, you'll learn how to: - Create a project with SwiftData - Define entities and relationships - Display and insert data seamlessly #swiftui #swift #iosdev https://lnkd.in/dR5Eh4wW

5

1 commento

Nextjs does not stop to surprise me. Somebody would say current state of this framework is all mess, but generally I see the value using it comparing it to stimulus, htmx or God forbid, jquery. In this post I would like to highlight several things that are not immediatelly visible: - unconfigurable runtime for middleware, next auth.. Somehow vercel assumes I will spin my app on edge runtime, even I dont had that idea even once. - if you pick next-auth you will definitely be stuck regarding sharing sessions during oauth flows because oauth IDP can get request from one instance behind load balancer, and send the response to another instance behind load balancer. - Any work done in middleware will be dependent on edge runtime??? - I could easily see patterns and antipatterns in nextjs usage and catch all basic terms, but community is slightly confused when you talk about basic fundamental ideas - You have to understand low level principles how all segments of nextjs work, to be comfortable in using it, especially if you want to self host it - I have a feeling vercel overcomplicate some things just to make you use their platform - Learning curve is steep, especially for juniors and mediors - Also, I find self hosting the app in cloud ideal and I dont wanna lock in vercel, so if you are like me, you have to count some hours for unexpected/expected infrastructure work besides all the coding. - api piece is pretty useless if you decide to go with custom backend Saying all these above, I just wanna highlight again that I will keep exploring it and still be curious to see in which direction will framework go in the future but one should be cautious and realistic before picking it.

2

Just discovered a valuable open-source tool at https://lnkd.in/dpHwAVUF that simplifies the documentation process for event-driven architectures. Building documentation with visualisations can be challenging, especially for complex architectures, but I'm excited to explore this tool and streamline the process. #EventDrivenArchitecture #Documentation #OpenSource

7

1 commento

Interesting article about TDD helps to write more better code, but it might take time to find the right path to have the most benefits from a TDD approach  https://lnkd.in/eFDdFqrj 

2

What's the difference between Rust and C#? Well, a lot of articles in internet can tell you that it not so huge and maybe they will be right, but ... I have some service written in C# and I have created it's copy, written in Rust. Definitely, some difference exists. Let's start from memory consumption. I have 5.4Mb in Rust application against 253Mb in C#. It's not a big deal in terms of current memory costs, but if you have a lot of applications and a lot of their stages, than you need to have huge infrastructure just because of memory consumtion. And my favorite one - docker image size. If we're talking about rust, then I can have it as small as 50mb. Of course, it can be even smaller with alpine, but I don't like dances with tambourines to make it work with ssl libraries and cross platform. In case of C# I have about 400mb And of course rust is much faster, but it's not significant with slow db backend. Maybe we will move our project to rust this year, at least some of them #csharp #rust

3

2 commenti

https://lnkd.in/dpF_9xjt thx Marco Testa for sharing << ...This repository offers a modeling technique for designing scalable systems. Every new system should be designed with scalability in mind — scalability is essential for success. With Scalable Modeling, you can embed scalability in your system design from the start... >>

2

I am really impressed with #Anthropic #Claude. I think this is bringing real value to devs. You have to give it a prompt and it will 1. write the code 2. 𝗿𝗲𝗻𝗱𝗲𝗿 𝗶𝘁! 3. It will fix dependencies if some component isn't working 4. It will take follow up prompts only touching or enhancing the part of the code that you ask it to. 𝗠𝗮𝗸𝗶𝗻𝗴 𝗶𝘁 𝗽𝗿𝗲𝗱𝗶𝗰𝘁𝗮𝗯𝗹𝗲, 𝗵𝗲𝗻𝗰𝗲 𝘂𝘀𝗲𝗳𝘂𝗹! Here my use case was related to Nextjs and Tailwindcss

13

If you want to add an event (or reminder) to the calendar using the system calendar view instead of a custom view, take a look at my latest post. "Adding Events to the Calendar in SwiftUI Using Default UI (Calendar Series Part III)," is here to help you streamline the process. 🗓️✨ 🔍 What You'll Learn: - How to effortlessly use the default calendar view without creating a custom one. - Step-by-step instructions for setting up and integrating the controller with SwiftUI. - Tips for checking authorizations and managing dismiss actions. - Essential reminders about permissions and calendar functions. Remember, this series is designed to make your life easier—don't miss out on the previous parts for a comprehensive guide! #swiftui #swift #iosdev https://lnkd.in/dSkuPJ6P

1

1 commento