Twenty years in tech, fifteen of them leading teams. I turn problems into engineering ones and then hire people better than me to solve them. I own more than 70 band t-shirts.
This is a list of notable stuff I’ve worked on in my spare time. These projects are mostly for my own amusement, learning something new or just scratching a particular itch. They are mostly unfinished, but have served some purpose.
Sling articles, music and video at it, tell it how much time you have, let it choose. I built the API and a PWA that scraped and stored the links, then realised I was making a CRUD app with search and stopped.
A music studio that lives in the browser tab. Built because I wanted to make noise without installing anything that describes itself as a workstation.
View →An RSS reader that sets your feeds as a newspaper: front page, columns, headlines that earn their size. The news looks better when it stops looking like a database.
View →A record collection you can walk around. Sleeves on shelves in 3D, pull one out, drop it on the deck, let it play. The most fun and least finished thing on this page.
I wanted to be a designer/builder and learned to code as a workaround. The workaround became the career. Frontend, backend, cloud: I learn exactly enough of each to build the thing, then stop.
Prototyping, solving and architecting is the part I actually enjoy, which turns out to be management. I found that out by accident, which is how most people find it out. Fifteen years later: development teams built and scaled, onshore and offshore.
Now it is product leadership: technology in service of value, which in practice means fewer heroics and better defaults. Platforms, golden paths, and the deeply boring infrastructure that lets everyone else look fast.
Whether you write code or lead people, your career is something you get to shape.