BLOG · ARCHITECTURE
Architecture
Structuring code that lasts: principles, patterns and architecture trade-offs drawn from my architect and lead dev engagements.
LEADERSHIP
Technical debt: why shipping features isn't always the right call
· 5 min read
ARCHI
Strategy Pattern: turning 200 lines of if/else into clean code
· 6 min read
ARCHI
Single Responsibility Principle: your code can finally breathe
· 4 min read
ARCHI
SOLID in .NET: 5 principles that make your code clearer and more maintainable
· 4 min read
REAL TIME
SignalR for your notifications? You may not need it
· 5 min read
← All articles · Even more .NET content on my LinkedIn profile ↗