I came across this recently thought ir was a very useful article for dot net developers
The big thing about the article is that for each blunder James mentions he clearly provides an alternate solution and they all seemed really clear to me.
OK so I’ve had some awesome questions from Software Engineers about the importance of SOLID principles and the one that is most common is how can I find out about and learn SOLID principles? There’s a lot of great articles and really good videos on the subject but I still think the single best starting point is a most awesome podcast from Scott Hanselman where he interviews SOLIDs author Bob Martin. It’s a great detailed explanation of how SOLID works and I think you’ll find that the practical aspects are really useful in trying to implement SOLID on a day to day basis.
https://hanselminutes.com/145/solid-principles-with-uncle-bob-robert-c-martin
I came across this excellent article recently and while the target audience is Software Architects, in my view this is a great book list for anyone who is looking to grow their software engineering skills in general. I often talk to software engineers about reading books as part of their professional development plan (I’ll over this is in a post soon).
What I really like about this list is that it is actually planned with an approach of building on previous books. So you don’t have to follow this exact list, but what you might think about is the importance/value of having a planned set of books/references to build upon rather than just have a random set of books to read.“
I particularly like the approach of introducing the DDD books later in the path.The foundational aspects of the initial books sets up DDD really well.
https://haitham-raik.medium.com/books-for-great-software-architect-34c81fc70e12
Really quite a neat series starting in Object Oriented Programming (OOP) in C# for those starting out …
https://www.c-sharpcorner.com/article/improve-your-model-classes-with-oop-part-one-the-basics/
Outstanding thoughts by Hanselman giving advice to a young developer. Really great article that I think a lot of developers (should read) …
“… to try not to focus on the syntax of C# and the details of the .NET Framework, and rather to think about the problems that it solves and the system around it.
…
Do you understand how your system talks to the file system? To the network? Do you understand latency and how it can affect your system? Do you have a general understanding of “the stack” from when your backend gets data from the database makes anglebrackets or curly braces, sends them over the network to a client/browser, and what that next system does with the info?”
https://www.hanselman.com/blog/SystemsThinkingAsImportantAsEverForNewCoders.aspx
I’d classify/tag this as off-topic but the reality over the quarter of a century in my professional life in IT, I’ve worked out one thing – you are working/coding better when you are happy. This is about the best video I’ve come across on the subject. I actually found it on c-sharpcorner.com for the record.
looks like there is still a day left:
Doms Code 