Alfie Nash

I started out writing backend services for a logistics company, which taught me that the hardest part of software is rarely the code — it is deciding what deserves to exist.

These days I work alone, usually embedded with a small team for three to six months. The shape of the work varies, but the pattern rarely does: understand the constraint that actually binds, cut the surface area in half, then build the remaining half properly.

I care about latency, legibility, and leaving behind something the next person can reason about. I am unreasonably particular about typography, empty states, and error messages — the parts of a product that show up on the worst day someone has with it.

Outside of work I restore mechanical keyboards, run slowly, and keep a long list of books I have started.