Building systems that scale, engineering practices that last, and AI tools that make both better.
I'm a software architect working at the intersection of distributed systems, cloud platforms, supply chain engineering, and artificial intelligence.
I care about architecture beyond diagrams: how systems behave in production, how teams make technical decisions, and how to turn complexity into reliable, maintainable software.
My approach is pragmatic. I favor clear boundaries, observable systems, engineering autonomy, and automation that solves real problems—not complexity for its own sake.
- Distributed architecture: designing and evolving services, integrations, and cloud-native platforms.
- Engineering enablement: improving development workflows, technical standards, and developer autonomy.
- AI-augmented engineering: exploring coding agents, multi-agent workflows, MCP integrations, and context-aware tooling.
- Platform reliability: connecting delivery pipelines, observability, and operational feedback to architectural decisions.
- Modernization: evolving legacy and enterprise systems incrementally, with attention to business continuity.
I'm particularly interested in how AI changes the way we engineer software, not just how quickly we write code.
That includes agent orchestration, human–AI collaboration, developer tooling, and systems that learn from execution feedback while keeping engineers in control of decisions.
| Area | Tools & technologies |
|---|---|
| Backend & integration | C#, .NET, Python, APIs, event-driven systems |
| Cloud & infrastructure | Azure, Kubernetes, Terraform, containers |
| Delivery & operations | Azure DevOps, CI/CD, Datadog, observability |
| AI engineering | OpenAI Codex, LLMs, agents, MCP, RAG |
| Architecture | Distributed systems, cloud-native design, technical governance |
Strategy beats intensity. Structure beats noise.
Good architecture should help teams deliver and operate software with confidence. I believe in making decisions explicit, keeping systems understandable, measuring what matters, and choosing the simplest solution that meets the real constraints.
A snapshot of my hands-on work with AI-assisted engineering:
Usage is a snapshot, not a measure of engineering quality. What matters is what gets designed, shipped, and improved.





