Category: Engineering

Notes that aren’t tied to a single product — the tooling, process, and engineering decisions that carry across everything I build.
Some of this is workflow: how I run Claude Code sessions, what actually persists between them, which parts of a build belong in version control versus in my head. Some is practice: treating security as a design constraint rather than a pre-launch checklist, and picking up iOS development again after years focused on the web.
These entries tend to be the ones I write after something broke, which makes them more useful than the ones written while everything was working.

Vibe Coding Didn’t Replace the Job. It Just Moved Where the Real Work Is.

I had a demo video with no narration and a stack of AI tools that could hand me a working script in about the time it takes to make coffee. I used them. I’m not going to pretend otherwise, and I’m not going to apologize for it either — that would be its own kind of dishonesty, and I’ve got no patience left for either the “AI wrote my whole app” victory laps or the “real programmers don’t need that” gatekeeping. Both are posturing. Neither describes how the work actually got done.