Architecture & Technical Direction
I define boundaries and contracts, then stay involved when implementation puts those decisions under pressure.
Work
I do not separate architecture from delivery. These are the areas where I usually move between design, implementation, review, and production diagnosis.
I define boundaries and contracts, then stay involved when implementation puts those decisions under pressure.
Most of the code I write is C# around business workflows, APIs, persistence, and integrations.
I work on queues, contracts, retries, ownership, and the awkward edges where systems fail independently.
AWS, containers, infrastructure as code, delivery pipelines, and diagnosing what actually happened in production.
Authentication, authorization, sessions, SSO, and deciding which component is allowed to trust which identity.
I use models where they add value, while keeping validation, confidentiality, cost, and business effects outside them.
Working principle