Why I Build
I build to think. A project forces a vague idea into a working thing — and the working thing teaches me what was actually true. Reading and talking only get you so far. Shipping is the real curriculum.
How I Choose Projects
I pick projects at the intersection of three things: a real problem I keep hitting, a skill I want to sharpen, and something I would still find interesting after the novelty wears off. If two of three line up, it makes the queue. If only one does, I write a note and move on.
How I Build
Small, ugly, and shipped beats large, beautiful, and theoretical. I aim for an end-to-end v0 in the first session — even if every piece is held together with tape — so the whole shape is testable. Polish is a separate phase.
What I Look For
Compounding assets. A project is worth more if its outputs feed future projects: reusable components, a clean dataset, a habit, a list of people I now know, a piece of writing. One-shot wins are fine. Building blocks are better.
Where to Go Next
Start with the active projects list. Each card has a current question, recent build notes, and what shipped — that is the live state of what I am working on.