Piotr Orlowski

🤵 Tech Lead: "We will start using DDD in our project!" 🤔 Me: "Cool! Is it Domain-Driven Design?" 🤵 Tech Lead: "Yes!" 😃 Me: "Nice! What will we do then?" 🤵 Tech Lead: "First, we will extract interfaces from all our DAOs and call them ‘Repositories’. Then, we will create big objects using ‘Factories’ instead of services..." That was a real conversation between my tech lead and me back in 2009. We tried to introduce DDD into a project. It didn’t go well. The codebase became even more complicated. And we concluded that DDD was a waste of time and didn’t work. Years later, I see many developers falling into the same trap - thinking DDD is just about repositories, factories, and aggregates. ❌ DDD is NOT about your code. Just because you have tactical patterns doesn’t mean you’re doing DDD. ✅ DDD is about understanding and structuring complexity: 🔹 Finding the right language to communicate with business. 🔹 Breaking down a complex domain into meaningful parts. 🔹 Understanding relationships between those parts. 🔹 Prioritizing: What’s core? What’s supporting? What can we buy? 🔹 Clarifying who owns and implements each part. 🔹 And only THEN, applying tactical patterns in code. Did anyone else start with “coding” DDD before understanding the strategic part? 😃

437

66 komentarzy

I can’t stress this enough: To become a Senior engineer you don’t need to complicate things. What you need is to focus your efforts on being pragmatic, business-oriented, and solution-oriented. I’ve seen too many talented mid-level devs shooting themselves in the foot by: 👉🏻Adding unnecessary abstraction layers “for future flexibility” 🤦‍♂️ 👉🏻Implementing design patterns that solve problems that don’t exist 👉🏻Building “elegant” solutions that take 3x longer to ship. Meanwhile, senior devs are out there asking the right questions: 👉🏻”Whats the simplest solution that works?” 👉🏻”What are we actually optimizing for?” 👉🏻”Will this help the business or just my ego?” Your promotion isn’t blocked by lack of complexity, actually it’s blocked by too much of it. Save your creative energy for problems that actually need complex solutions.

679

46 komentarzy

Use the Toolbox Panel in Visual Studio 2022 The Toolbox panel is well-known to developers who previously worked with WinForms. It was used to hold controls. In modern application development, we can also use this panel to store code snippets that we frequently use across different projects. ✔️ To open the panel, click View -> Toolbox or use the Ctrl+Alt+X shortcut. ✔️ To add a snippet, select the desired lines of code and drag them into the panel. You can then rename the snippet for convenience. ✔️ After that, you can drag and drop the snippet into the relevant parts of your code in other projects and solutions. Make your coding faster with this simple Toolbox tip. If you found this helpful, please repost it 📢 #csharp #dotnet #softwaredevelopment #visualstudio

44

4 komentarze

Has Gartner found the missing link between developer experience and productivity? The good news: 67% of teams who reported a high quality developer experience exceeded productivity expectations. But here's the bad news: only 17% of developers said they are satisfied with their developer experience. Only 17% !!! So why don't more organizations try to improve developer experience? We asked Abi Noda this question on our Steering Engineering podcast. Abi makes the point that developer experience has a branding problem, with executives saying "don't we already let our developers work from home and we give them lots of perks?". Even the term "developer experience" itself is problematic and can be misunderstood. Check out the podcast on Spotify or wherever you get your podcasts: https://lnkd.in/eAHxPSaq

59

1 komentarz

📖 More than halfway through reading "Balancing Coupling in Software Design" by Vlad Khononov https://lnkd.in/eapjZHbU I keep it by the side (tab) as I write my Speaker Book, and I am so impressed by how Vlad embarked on this simple, common topic of coupling in software and was able to bring out all the nuances of science, physics, maths, and so on. Well, I meant how he explains connascence, strength, distance, volatility, balance, etc., about coupling. 😃 Amazing! Those who've been in the industry long enough to know SSADM and have read the thoughts and books by Peter Coad and Edward Yourdon would feel nostalgic, and it is remarkable how Vlad incorporates these into modern thinking. The pure joy of reading quality content! 🙌 #AWS #Serverless #cloud #softwarearchitecture #coupling #ssadm #TheSpeakerBook #TheServerlessBook

36

1 komentarz

Even though I am understandably heavily biased towards using RestAssured .Net for my C# API testing needs, a lot of companies use RestSharp for that purpose. That's why I keep maintaining the open source RestSharp workshop I created a few years ago (before I even started working on RestAssured .Net), and I just published another update: * I updated examples and exercises around retrieving and verifying response header values * The workshop materials now also run on .NET 9 * All dependencies are bumped to their latest versions You can find a link to the workshop materials (code examples, exercises and answers and a full slide deck) via the link in the comments.

23

1 komentarz