.NET architecture
Minimal API, layer boundaries, MongoDB, gRPC, streaming. Where to simplify and where structure actually pays off.
Let's talk it through
People often write to me to think through a technical decision. This page explains what I can actually help with, how it usually goes, and what I'm not useful for — so you know what to expect before writing.
What I can help with
AI in production
RAG, hybrid search, MCP, function calling, agent orchestration: model choice, cost, guardrails and fallbacks.
Vibe coding and agent workflows
How to set up hooks, skills, quality gates and multi-model review without turning the assistant into a tech-debt generator.
Developer career paths
What to learn, what to skip, and how a full-stack profile evolves after twenty years on the job.
How it usually goes
You send the context
A couple of lines on what you're building, where you're stuck and what constraints you have. The more concrete, the better.
We talk it through
Over email or on a call, depending on how involved it is. We look at the real problem, not the simplified version.
You get something written
A summary of the options, what I'd recommend and why, plus links to dig deeper on your own.
What I'm not useful for
- Stacks I don't use: Java, PHP, Rust, native mobile.
- Decisions that need someone to know your business better than a conversation allows.
- A service to sell: I do not need to make business out of this, and that is exactly my strength — you write to me to discuss and trade ideas, I have nothing to sell you.
Write to me
- I answer personally. A couple of lines of context are enough to tell whether it is worth talking.