shipped projects · postmortems · talks on flow
where I look for the state of flow — Side projects, the job, the search for impact. The only room with a clock on the wall.
"Vibe coder" is a scapegoat. There have always been people who care about the work and people who ship whatever compiles — AI just stopped hiding which is which.
There have always been people who care about the work and people who ship whatever compiles. AI didn’t create that split; it removed the friction that used to disguise it.
The tooling isn’t the tell. Your process is.
Shipped a Hyrox app days before my own SOLO debut. Real users found what was fundamentally useless in an afternoon — things no amount of manual testing in my bubble had surfaced.
You can manual-test inside your own assumptions forever and learn nothing. I shipped a Hyrox app on May 14, days before my own SOLO debut — and real users found what was fundamentally useless in an afternoon.
Not broken — useless. The things I’d assumed were enough to matter weren’t the ones that did, and no careful clicking in my own bubble would ever have told me. Take the leap, or stay comfortably wrong.
Shipped my first solo iOS app — a workout timer. Thought the hard part was behind me. The hard part was getting anyone to find it.
Shipped my first solo iOS app — a workout timer — on Jan 20, 2026, sure the hard part was behind me. It wasn’t.
Getting a good thing in front of the people who’d want it is a separate, harder craft than making it. I’d built plenty before, but never my own — and never had to make a stranger care.
Wrapped after four and a half years. Turns out the retrospective finally needed a retrospective.
↳ Co-hosted “No es solo código,” a weekly podcast on life in web programming — a running retrospective with a colleague, 2019 to 2024. · alive 53 months
Co-hosted “No es solo código,” a weekly podcast on life in web programming — a running retrospective with a colleague, 2019 to 2024.
AI coding isn't about generating code. It's that effort can compound — each pass should inherit the last one's context, not rebuild it from scratch.
The leverage was never “the AI writes code.” It’s that effort can stack — each pass inherits the last one’s context instead of starting cold.
Used well, it frees your attention for the interesting part: establishing non-obvious relationships between things, exploring, building — not re-explaining your codebase for the tenth time. Used badly, it goes sideways building from zero, every time.
What hangs here isn't a category of work — it's the evidence of what happens in this room. The same note may also be a Ledger row or a Glossary headword; it's authored once.