Post

Sam Rose
@samwho.dev

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.

Sam Rose
@samwho.dev

Vibe coding pros: - I was able to get a lot of chores done around the house while working on this. - Quite nice to give high level tasks and feedback then come back a few minutes later to see how it’s doing. - I don’t think I’d have been able to make the time to do this otherwise.

0 reposts1 like

Sam Rose
@samwho.dev

Cons: - If you let it do what it wants without reading the code it will produce a nightmare of cthulean proportions. - Very much not an interactive process. Everything takes minutes. Not long enough to focus on anything else but not short enough to feel good watching it happen.

Sam Rose
@samwho.dev

Many times it got stuck on a specific bug and I tried half a dozen times to explain the problem and desired behaviour before having to go and look at the code. Invariably the code was turbo-ass and I spent an hour or so prompting it to be better. Tests and static analysis help a lot.

Sam Rose
@samwho.dev

Ultimately I don’t think this is a good way to work. I think the optimum is somewhere in the middle. Delegation of tasks these systems are good at while I spend my time digging into the stuff it isn’t. I’m enjoying learning how to use them, though, and suspect they’re here to stay.