I own things through production

I work across the stack frontend interfaces, backend architecture, and the infrastructure that puts both into production. Most of what I build is meant to run for years and be maintained by someone who is not me.

That shapes how I work. I reach for clear architecture over clever solutions, because clever code is a debt someone pays later. I write decisions down before they get argued about. And I would rather carry a feature through deployment and stay with it afterwards than hand it over at review.

The part of engineering I find most interesting is the second delivery of the same message retries, replays, duplicate events. Designing for that before the happy path is what separates a system that survives contact with real users from one that needs watching.