Architecture12 min read
Clean Architecture: A Pragmatic Approach (Not a Religious One)
After 8 years of building software for real clients, I've learned that architectural purity sometimes gets in the way of delivering value.
Real insights from 8 years of building software - practical lessons on architecture, testing, client success, and technology choices that actually work in the real world.
After 8 years of building software for real clients, I've learned that architectural purity sometimes gets in the way of delivering value.
I used to be a 100% code coverage zealot until I started working with real clients on real deadlines.
I'm the good kind of lazy - the kind that drives me to automate everything so I never have to do the same thing twice.
The cloud isn't just about hosting anymore. With AI becoming core to modern applications, here's how to architect systems that are both scalable and intelligent.
People ask me all the time: "What's your preferred tech stack?" Here's my honest answer based on 8 years of building real applications.
When my clients succeed, I succeed. This isn't just feel-good philosophy - it's the most practical business strategy I've ever adopted.
Running multiple Claude Code agents simultaneously, each owning an independent ticket — here is what that pipeline looks like, what works, and where I still run into friction.
AI agents are good at reading code. The problem is that reading code and understanding a codebase's architecture are different things. Here's what I found works.
Provider-agnostic interfaces, cost routing across 7 LLM providers, streaming RAG pipelines — the architecture patterns I use in production across .NET, Python, and Next.js.