Blog

lesson5 min read
supporters

Before the first prompt: purpose, vision, and who this is for

The twenty minutes I spent on paper before opening Claude. Why they mattered more than any individual prompt.

lesson8 min read
supporters

The prompt is the spec: how I learned to talk to Claude

Vague prompts produce vague code. Here's what changed when I started treating every prompt like a specification — and what I do when Claude gets it wrong.

lesson3 min read
supporters

How I set up Claude Code on day zero

Installing the tool, creating the project, giving Claude access to git. The thirty minutes before the first commit.

lesson4 min read
supporters

The dev experience advantage — and how to close the gap

I have a software background. That's why this moved fast. Here's what that actually means and what you can do about it.

experiment3 min read
supporters

What you see after you pay

Most paywalls just remove a block. This one changes what the whole site looks like — and why that matters for any product.

experiment5 min read
supporters

The paywall was fake. Here's how I fixed it.

Day 2: a real paywall without a backend — how HMAC signatures replace a database, and what broke along the way.

experiment3 min read
supporters

I don't write these posts

There's a system. It turns work sessions into published content — and you can set it up in any project.

diary1 min read

Day 1. Starting from zero

I have dev experience. That's why this moved fast. Here's what that means for you.

diary4 min read
supporters

The moment Claude stopped waiting for me

Setting up git push access — and how knowing git made this 20 minutes instead of 2 hours.