Seems painfully obvious that, whatever you think about #genai code, anyone using it is heading for a code-review logjam.

[timbray@cosocial.ca]

Seems painfully obvious that, whatever you think about #genai code, anyone using it is heading for a code-review logjam. Assuming that the org requires code review; if yours doesn’t, nothing I can say will help you. Anyhow, Rishi Baldawa writes smart stuff about the problem and possible ways forward, in ˚The Reviewer Isn't the Bottleneck”: https://rishi.baldawa.com/posts/review-isnt-the-bottleneck/

[My prediction: A lot of orgs will *not* do smart things about this and will suffer disastrous consequences in the near future.]

[petrillic@hachyderm.io]

@timbray I am hearing peers in other companies being pushed by executives to abandon code review completely.

If you’re wondering how deep the psychosis goes.

[tim_lavoie@cosocial.ca]

@petrillic @timbray That's certainly my concern. I'm in security, so mostly watching this from the sidelines, as I listen to execs essentially pushing for "vibe-code to prod".

It can only become worse when making changes to programs, since it won't be incremental change. Instead, it'll be, "no, do the thing, but not like that." The old fluff will be thrown away, and so the new version will be whatever it is, possibly completely different from last time. How do you review that?