Plenty of architects will draw you a beautiful design and hand it to a team that then builds something else. The design and the code drift apart, and by the time anyone notices, the diagram is fiction.

I build in the architecture I design, so it never becomes fiction. Full-stack .NET and Angular, in production: secure, role-based portals and admin apps; reactive, modular front ends; APIs that hold up under load. I stay close to the code through implementation, performance tuning, and reviews — which is also how the architecture stays honest.

An architect who hasn't shipped code recently is guessing about the things that matter most — how the framework actually behaves, where the performance cliffs are, what the AI tools get wrong. I ship. The design and the implementation move together, reviewed in small layers, so neither one gets to lie about the other.

• Backend: .NET (through 10.x), ASP.NET Core, EF Core, .NET Aspire
• Front end: Angular, TypeScript, standalone components and signals
• Data: SQL Server, Cosmos DB
• Cloud: Azure Functions, Service Bus, AKS
• AI: OpenAI and provider integrations built into real product workflows — automated image and social-copy generation, layered prompt-memory systems, the works