A list of various resources (books, sites, blogs, tutorials, ...) I find useful in my journey as a developer.
The Clean Coder - Robert C. Martin
Not a book about technologies, but about the actual person who writes code. Robert C. Martin uses his 40+ years of experience to describe what it takes to be a professional developer. Most of the points I feel myself agreeing to.
A book every aspiring professional developer should read, and keep it close by to reference to it again when staying professional gets tough.
Framework Design Guidelines - Conventions, Idioms, and Patterns for Reusable .NET Libraries - Krzysztof Cwalina, Brad Abrams
A must-have book on your shelve when writing .NET code, especially re-usable and shared libraries, within your project, team, company or worldwide.
Written by the creators of the .NET Framework, it contains a lot of do and don'ts and falls back on real-life examples during the creation of the framework.
I just realize there's a new updated 3th edition available.
Domain Driven Design: Tackle Complexity in the Heart of Software - Eric Evans
Though I've not had the chance to finish this book, the DDD principle comes back over and over again in various development patterns and architecture.
For example, it is fundamental in successfull MicroServices architecture.
DDD is a concept every enterprise architect should be familiar with these days.
Writing High-Performance .NET Code - Ben Watson
I bought this book because the subject interested me (and it was on sale). The book is hard to read and goes very deep in concepts such as Garbage Collection and other low-level APIs.
After reading this, you understand a lot more about the internals of .NET and the compiler. It makes you also realize that .NET is not just some high-level framework, but when understanding enough can compete with other low-level languages such as C and C++.
Management 3.0 - Leading Agile Developers, Developing Agile Leaders - Jurgen Appelo
I'm not a manager, and never want to be one. But inevatible, when working as a senior developer on large projects, you get to know some of the company's structure.
I bought this book to help me understand more management, and maybe become a better technology lead. The ideas explained here are very interesting and I can see how things will certainly improve.
Unfortunatly, I have not seen a practical environment that comes close to it. But it's worth understanding and aiming for it.