I build calm software, and I teach it to do the boring parts.

My first real job was building internal tools for a logistics team. Spreadsheet rescue missions, mostly. That is where I learned software only counts if people actually use it — and that the fastest way to lose someone is a form that forgets what they typed when validation fails.

These days I work across the stack. Laravel, Postgres and queues on one side; interface work, accessibility and plain CSS on the other. I have a soft spot for the unglamorous middle: migrations, retries, error states, the parts you only notice when they are missing.

The AI half is not a slogan. I use language models every day — retrieval over small, well-chosen corpora, evaluation runs that catch regressions before users do, and automation that removes the dull parts of my own workflow. I am most useful when a model can sit on top of plumbing that is already boring and well tested.

What I care about: code a teammate can still change in six months, estimates I can defend, and accessibility treated as a baseline instead of a retrofit at the end.