Hi there 👋

Learn why UseRouting() must always come before MapGet() in ASP.NET Core and how the middleware order impacts your request pipeline.

Bad middleware doesn’t just break requests, it breaks entire tenants. Learn the anti-patterns to avoid in your ASP.NET Core SaaS architecture and how to fix them.

TL;DR Code reviews should teach, not just catch bugs. Stop nitpicking syntax and start building autonomous developers. Focus on architectural patterns, ask guiding questions instead of giving orders, and eliminate multi-team approval bottlenecks that delay delivery. Good reviews create learning opportunities that scale your team’s expertise. Code reviews shouldn’t be about catching syntax errors or enforcing personal preferences. They’re your best tool for spreading architectural knowledge and building stronger development teams. But most teams get this wrong, creating bureaucratic bottlenecks instead of learning opportunities. ...

Discover how using custom middleware for authentication in ASP.NET Core SaaS APIs leads to cleaner, faster, and more maintainable code compared to traditional authorization filters.

Master SOLID principles with real C# examples, interview questions, common pitfalls, and clean architecture tips for maintainable, testable code.

TL;DR: Most developers only encounter closures during interview prep or basic counter examples. This post dives into how closures power real-world frontend scenarios: event listeners, encapsulation, memoization, and reactive programming. Walk away with patterns you can use today. Every JavaScript developer has seen the classic closure examples: counters that increment, multiplier functions that return other functions. These textbook cases teach the concept but leave you wondering when you’d actually reach for closures in real frontend work. ...

A senior developer’s perspective on writing less code, focusing on architecture, mentorship, and team productivity.

In multi-tenant SaaS applications, custom middleware gives you the earliest hook in the request pipeline, even before dependency injection kicks in. Middleware runs at the very beginning of your pipeline, providing access to raw request data before any transformations occur.

TL;DR Repeating logic across controllers (like logging or header checks)? Move it to middleware. Modifying requests/responses in controllers? Middleware handles that cleanly and early. Your services use HttpContext? Extract that logic into middleware for cleaner, testable code. If your services are bloated or you’re duplicating logic across controllers, middleware might be the extension point you actually need. Many developers reach for filters or services first, when middleware would’ve been faster, simpler, and more maintainable. ...

Constructor injection is your first clean architecture decision. Learn how to write testable, decoupled ASP.NET Core code using built-in DI, scoped lifetimes, and mocking techniques.