pborenstein.dev

How I code with Claude


I start by telling Claude what I want and ask it to make a plan. We iterate over the plan, refine it, and rework it into a new plan. We do this two or three times before we start code.

Once coding starts, we look at the results, reëvaluate the plan, iterate on that, and continue coding. This is the spirit of agile: small loops, real feedback, plans that bend.

We do this three or four times till we get an MVP.

I use the MVP for a few days, iterating with Claude as real-world use exposes what I missed.

After a week or so of that, I chat with Claude about the implementation vs the plan. Early assumptions that weren’t borne out, new needs the MVP exposed, ideas for improvement.

During this reassessment, Claude creates tools to analyze logs, test ideas, and to search for similar projects.

We make a plan. We bend the plan. We make a new plan.

I wondered How Claude works with Philip. There’s a version of this post annotated by Claude.