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.

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 😂

Still got some of that $62m left, eh? 😏

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.

One of my coworkers blogged about how we’ve been using Claude code at work which you may find interesting. We have ~25 eng using it daily so have been keen to find patterns to improve our usage. incident.io/blog/shippin...