Dev Secrets

Architectural characteristics (non-functional requirements) are the "invisible" qualities that make the difference between a fragile app and a reliable, production-ready system.

Many senior .NET developers are thrown into architectural roles without guidance. So to lead effectively, you must proactively build the skills no one ever formally taught you.

Defaulting to MediatR in every .NET project adds unnecessary complexity and cost. Often, a simple use case class does the job better.

When you're faced with architectural uncertainty, don’t guess. Run a spike to explore options quickly, reduce risk, and make smarter decisions like an architect would.

If monoliths are too tangled and microservices too complex, a modular monolith strikes the balance. It gives clear boundaries, high cohesion, and maintainability without the chaos of distributed systems.