Greenfield is a blast.
Brownfield is
the tougher game.

Work

Most of my career has been the systems nobody gets to rewrite from scratch: the ones already in production, already carrying money, prescriptions, or public records. The job is to change them without breaking what people depend on.

Platform migrations

Moving live products between frameworks, data stores and identity providers while they keep shipping. Recent examples: three production mobile apps moved from Xamarin to .NET MAUI with no break in releases, and a patient app's sign-in moving from Keycloak to Auth0, a multi-step cutover I am leading now.

Architecture with a paper trail

Decision records, spikes before commitments and designs that name what they gave up. I would rather spend a week comparing four messaging designs than a year living with the wrong one.

The questions upstream of the code

Most of what I am worth happens before anyone writes code: checking what is actually true, guarding the decisions that cannot be undone cheaply and writing plans specific enough that people argue with them.

Teams that run like small companies

I manage engineers and run the full performance cycle. I have run a product team as a self-contained business inside a larger company: its own roadmap, its own releases, its own results.

AI-assisted engineering you can review

I build the practice around the tools: independent review, claims marked as checked or unchecked and evaluations that catch it when the guidance an agent follows goes wrong. The workspace behind it has its own page.