@droidboy @peter @fishidwardrobe In my experience, the people who vibe code PRs also use AI to generate the descriptions, the Jira tickets, and everything else that used to contain useful information.

Nothing but a direct human to human conversation with the person in question enables me to figure out what it is they’re actually attempting to do. 😅

@droidboy @peter @fishidwardrobe Social disrespect aside, I would say it’s nigh impossible to actually review the PR. It’s difficult to know if a change is doing what it is intended to do if the intention isn’t clear.

FWIW this is not hypothetical. I occasionally need to review vibe-coded PRs, and close to 100% of the time I need to pause the review and have a conversation or Slack chat with the author to figure out what problem they’re actually trying to solve.

@peter The single most important structural thing any software organization can do is to figure out how to hire and retain talented people.

If you can do that (and it’s not easy!) then whatever methodologies and ways of working those folks come up with will work fine.

@peter Like many things in software development, a talented and diligent software developer will produce great software without necessarily needing to write a ton of tests, and a bad developer will not have the ability to write useful tests.

I’ve found that hard and fast rules like “you need x% coverage” or “you need to use agile” or whatever are complete BS. The bottom line is that talented people will do good work and talentless people will fuck everything up.