I learn best by doing the real thing, then writing down what happened.

Sometimes that’s technical. Last month I needed to make sure a money transfer never runs twice, even if the user taps the button twice or the network retries. I could have read about it for a week. Instead I built it, watched it fail in ways I hadn’t expected, and came out understanding it better than any article would have taught me.

A lot of that building happens with AI now. It writes the first draft, explains the code I didn’t write, argues with me about design, and quizzes me on what I think I understand. Used well, it’s the fastest teacher I’ve had. Used badly, it ships things nobody understands. Working out the difference is one of the things I’ll write about here.

And sometimes it’s not technical at all. Running a company with one other person, moving cities, figuring out what I actually want from work. Same method: do it, notice what happened, write it down.

So this site is a mix. Engineering notes, how I work with AI, thoughts on building things, and whatever else I’m figuring out. Short when something clicks, longer when it takes a while.

If you’d rather learn by doing than by waiting until you feel ready, you’re in the right place.