Blog
Notes on working, tools, and whatever else is on my mind.
- A portfolio that agents can readMore people now meet my work through an AI assistant than through my home page. Here is what this site serves to agents, and why each piece is small.
- How I use AI as leverage, not autopilotAI writes a lot of my first drafts now, in code and in content. This is where I draw the line between what the tool does and what stays my job, and the writing that shaped how I think about it.
- Designing for what you can't knowGood software is honest about uncertainty. A small example from a crypto terminal: when the data stops, we say so on screen instead of pretending everything is live.
- Store the history, not just the numberTwo very different products, a crypto terminal and a school savings app, ended up with the same rule for money: never edit a number, only add a record. Why that matters, and what it costs.
- Measure before you choose: why I start with boring technologyData-heavy products attract exciting infrastructure. I usually start with the simplest setup that works, and I make that choice with numbers, so it is easy to explain and easy to revisit.
- Rebuild or refactor? How I decideThe usual advice is never to rewrite a working product. Sometimes it is still the right call. These are the four questions I ask before choosing, and how they played out on a real product.