Loading
Stack
Not everything I've touched the tools I reach for, and the reason.
APIs as contracts, not endpoints that happen to exist: the data model comes first, the routes follow.
Most of the systems I build have a location at the center of them, so geography lives in the database, not in application code.
One frontend framework across nearly every project I've shipped: fewer surprises, faster ramp-up on someone else's code.
Running a service locally and running it in production should be the same operation.
Once a system needs more than one service talking to itself reliably, orchestration stops being optional.
Repetitive work belongs in a pipeline, not in someone's afternoon.
The tools that turn a spatial database into a map someone can actually query.
For the observatory and reporting systems where the interesting question is "search across all of this," not "fetch one row."
The unglamorous layer that decides whether HTTPS and uptime actually happen.
AI tools I use daily for the same reason I automate anything: so the day goes on the decision, not the boilerplate.
Contact
I'm interested in engineering problems worth solving, products that need building properly, and teams where an engineer is trusted to own a feature end to end.
I answer within a day.