Software Engineering

This is the connective tissue for everything else on this page — every domain I work in eventually needs a frontend, an API, or a database that doesn't fall over. Six years in, the interesting problems for me aren't usually the framework choice; they're the boundary conditions: what happens under real traffic, what happens when the schema needs to change under load, what happens when the product pivots and half the assumptions in the codebase no longer hold.

I own products end to end — frontend, backend, database administration, and the deploy pipeline that gets it all into production — because the seams between those layers are where most reliability problems actually live. A clean frontend backed by a fragile API isn't a finished product, it's a demo with a nicer coat of paint.

Beautiful is nice to have. Reliable is the job. I'd rather ship something a little plainer that survives a traffic spike than something polished that falls over the first time it matters.