logoalt Hacker News

whstlyesterday at 2:04 PM1 replyview on HN

Not advocating that people should follow this but:

As someone that loves cleaning up code, I'm actually asking the vibe coders in the team (designer, PM and SEO guy) to just give me small PRs and then I clean up instead of reviewing. I know they will just put the text back in code anyway, so it's less work for me to refactor it.

With a caveat: if they give me >1000 lines or too many features in the same PR, I ask them to reduce the scope, sometimes to start from scratch.

And I also started doing this with another engineer: no review cycle, we just clean up each other's code and merge.

I'm honestly surprised at how much I prefer this to the traditional structure of code reviews.

Additionally, I don't have to follow Jira tickets with lengthy SEO specs or "please change this according to Figma". They just the changes themselves and we go on with our lives.


Replies

grvdrmyesterday at 4:49 PM

Favorited. I was talking to someone (non-dev) yesterday who prototypes with Claude and then goes back/forth with the lead engineer to clean it up and make it production worthy (or at least more robust). I like that model.