Martin Hasoň

🤵 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 komentářů

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 komentáře

✨ First open source PR in years. First blog post ever. First time adding Cassandra support to Testcontainers-dotnet? Yep, Gavin de Kock just did all three. And it was smooth sailing. 🚢 From spotting a missing module to contributing it with ease, Gavin shares how friendly the Testcontainers OSS community is—and how simple it is to spin up Apache Cassandra for .NET integration testing using Docker. A fun read and a great reminder that open source is open for everyone. 🙌 Check out the post and try it yourself: http://spklr.io/6048APQn #Docker #Testcontainers #OpenSource #DotNet #ApacheCassandra #IntegrationTesting #DeveloperExperience

40

2 komentáře

Is a .NET Developer the Most Important Part of a Team? 🤔💡 In the world of software development, every role plays a crucial part in building a successful product. But let’s talk about .NET developers specifically, are they the backbone of the team? ✅ .NET developers are often responsible for creating the core functionality of an application, ensuring scalability, security, and performance. ✅ They bridge the gap between front-end experiences and back-end logic, making sure everything runs smoothly. ✅ With the power of C#, ASP.NET, and cloud integrations, they enable businesses to build robust and scalable solutions. But here’s the reality: a team’s success isn’t about one role it’s about collaboration. 🚀 UI/UX designers create intuitive interfaces that keep users engaged. 🔗 DevOps engineers ensure smooth deployment and scalability. 🔍 QA testers catch bugs before they impact users. 📈 Project managers & product owners align technical work with business goals. So, while .NET developers are critical, no single role is the "most important." Instead, the best teams thrive when each member brings their expertise and works together toward a shared vision. What do you think? Is there a "most important" role in development teams, or is it all about teamwork? #DotNet #SoftwareDevelopment #TechTeams #Collaboration

21

8 komentářů

Niagara Developer Series Video 1 - Getting environment ready This will focus on setting up your dev environment with IntelliJ Community Edition, installing JAVA, making sure your license and properties are ready for developing and testing in Niagara, and making sure nodeJS in installed on your laptop/PC. I have used VS code to do some development BUT really that's only for the UX modules. For the entire video series, I will be using IntelliJ. You will also notice, I don't set up my environment variables. You really don't need to do that at all. The only time I ever do it is if I'm developing a UX module only and I want to test my code in the browser. Here are the java files for the code I've been working on. The link will continue to be added to the more code I add. Eventually there will be a github repository. https://lnkd.in/eG5p2wY7

46

1 komentář

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 komentář