Post

I got an itch to play with some ideas I’ve had around code review. Also decided to completely vibe code it with Claude Code to become more familiar with the strengths and weaknesses of working like this. Idea is you can sort files topologically, and symbols modified in this PR are highlighted.

Are you familiar with plan mode? You activate it by shift+tab’ing in your Claude code session. I’d advise doing this always. You give instructions, then you carefully review the plan and make changes there, which means you fix half the issues before it even writes any code.

The plan can be made way quicker than the changes so feedback loop is much more fun, you don’t have to wait minutes to find out it’s done something stupid. Also were you on Sonnet 4 or Opus? Opus is noticeably better, though it is 10x as expensive.

0 reposts0 likes

I’m aware of plan mode but haven’t tried it yet. It’s on my list! I’m also mostly using Sonnet 4. I’ve heard folks say “Opus for planning, Sonnet for execution.”

Yeah, that advice reflects how impactful the initial plan can be. Same reason helping it build a plan that exactly matches what you want can make a big difference to output. Confess I’m just running Opus now, but that’s less ok if you’re employer isn’t paying the bill 😂

Hahaha, it turns out it’s much cheaper to make your engineers 20% more effective than it is to hire 20% more eng! I mean, we’re doing both and would triple the team tomorrow if hiring could support it, but for now giving everyone unlimited AI spend is just one of the ways we can try going faster.

Hey @lawrencejones.dev are there a videos of this system being actively used? I'm curious about bringing AI features into my dev workflow but at the moment the only tool I use is Copilot. There's access to Claude, but copilot (at least my config?) requires constant monitoring of the AI stuffs.