Post

At this point, we don't have successful case studies in safety engineering protocols necessary to ensure long-term quality and reliability of LLM-generated software, much less a more holistic assessment of impact on community and organizational knowledge, mentoring, etc.

Loris Cro ⚡@kristoff.it

Contributor Poker and Zig's AI Ban https://kristoff.it/blog/contributor-poker-and-ai/

This was a knee-jerk manager reaction. It surely didn't assess the long-term impact of reassigning senior engineers to reviewing sloppy PRs instead of cross-cutting design work and active mentorship. More recently, these managers are questioning tokenmaxxing and return on investment 🤡.

Christine Lemmer-Webber@dustyweb.bsky.social

It turns out GenAI code changes are causing serious incidents and outages at Amazon with "high blast radius" www.ft.com/content/7cab... Junior / middle engineers no longer allowed to push GenAI code to production without senior engineer review

It is sometimes true that these products shorten the time necessary to meet certain KPIs. Management does not want to critically examine how bogus their KPIs have been. Meanwhile, they need investor confidence more than they need a product, and participating in the Potemkin performance is rewarded.

Jed Brown@jedbrown.org

Also note that many developers are subject to coercive measures to maximize "AI" use and self-report success (performance eval), quality be damned. And contrast the rosy claims of the Potemkin performance for investors to what developers say when able to speak freely.

3 reposts12 likes

Agents are malware. Bugs, infrastructure failures, and security issues are expensive. Management flailing in ways that plenty of engineers instantly recognize as harmful to the company, but can't be heard and still consider themselves too special to unionize. Must keep up appearances for investors.