Conversation

Notices

1. Embed this notice
   Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 10-Mar-2026 23:31:41 JST Christine Lemmer-Webber

   • Kim Perales

   It turns out GenAI code changes are causing serious incidents and outages at Amazon with "high blast radius" https://www.ft.com/content/7cab4ec7-4712-4137-b602-119a44f771de

   Junior / middle engineers no longer allowed to push GenAI code to production without senior engineer review

   (HT @KimPerales )

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Wednesday, 11-Mar-2026 00:34:22 JST Christine Lemmer-Webber

     in reply to

     Here's a different article about the same topic https://www.tomshardware.com/tech-industry/artificial-intelligence/amazon-calls-engineers-to-address-issues-caused-by-use-of-ai-tools-report-claims-company-says-recent-incidents-had-high-blast-radius-and-were-allegedly-related-to-gen-ai-assisted-changes

     Steve's Place repeated this.
   • Embed this notice
     deech (deech@mastodon.social)'s status on Wednesday, 11-Mar-2026 01:10:13 JST deech

     in reply to

     • Kim Perales

     @cwebber @KimPerales I'll bet $100 the incidents would have happened even with sign off. No one wants to review slop.

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Wednesday, 11-Mar-2026 02:25:54 JST Christine Lemmer-Webber

     in reply to

     And even another link https://arstechnica.com/ai/2026/03/after-outages-amazon-to-make-senior-engineers-sign-off-on-ai-assisted-changes/

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Wednesday, 11-Mar-2026 02:41:33 JST Christine Lemmer-Webber

     in reply to

     • Z̈oé
     • mcc
     • Kim Perales

     @uint8_t @mcc @KimPerales The current trajectory is: don't hire any new junior engineers. Instead, management generates the slop PRs themselves and sends them to senior engineers. "Hey, what do you think?" and you have to figure out how to tell your boss "I'm sorry but this is really bad" and they won't understand why

   • Embed this notice
     Z̈oé (uint8_t@chaos.social)'s status on Wednesday, 11-Mar-2026 02:41:35 JST Z̈oé

     in reply to

     • mcc
     • Kim Perales

     @mcc @cwebber @KimPerales also the vibe coder junior will hardly mature into senior

     Christine Lemmer-Webber repeated this.
   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Wednesday, 11-Mar-2026 02:41:36 JST mcc

     in reply to

     • Kim Perales

     @cwebber @KimPerales "without senior engineer review"

     okay so this hits on an issue i've been thinking a *lot* about

     i won't use LLM code generators. i believe i can find a job where i don't have to use LLM code generators. but i would probably still be forced to *work with people who do*. and if someone on your team vibecodes, you vibecode. the work of a vibecoder is code-review and checking. but everyone checks everyone's code. so they're pushing their work onto me. i'm vibecoding for them.

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Wednesday, 11-Mar-2026 02:41:36 JST mcc

     in reply to

     • Kim Perales

     @cwebber @KimPerales amazon just formalized this. my criticism. "they tweeted it out". if what the junior vibecoder does is review the generated code, but amazon must mandated the senior engineer does the actual review, then why do you have junior engineers at all? the senior engineer in this case now does the junior engineer's entire job as amazon defines it.

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Wednesday, 11-Mar-2026 02:42:13 JST Christine Lemmer-Webber

     in reply to

     • Z̈oé
     • mcc
     • Kim Perales

     @uint8_t @mcc @KimPerales It won't last that way forever but I think that could be the sad interim state we are heading towards for a while