Drew

And as a real-world application of this, Amazon held an emergency team meeting to talk about AI breaking its system.

This is a tweet from Lucas Ologenic.

All in ink.

Yeah, European name.

The official framing is part of normal business.

The briefing note described a trend of incidents with high blast radius caused by generative AI-assisted changes, for which best practices and safeguards are not yet fully established.

Translation to human language.

We gave AI to engineers and things keep breaking.

The response from now, junior and mid-level engineers can no longer push AI-assisted code without a senior signing off.

AWS spent 13 hours recovering after its own AI coding tool asked to make some changes, decided instead to delete and recreate the environment.

The software equivalent of fixing a leaky tap by knocking down the wall.

Amazon called that an extremely limited event.

The effective tool served customers in mainland China.

And then inside the email itself, Amazon's e-commerce business has summoned a large group of engineers to a meeting on Tuesday for a deep dive into the spate of allergies, including incidents tied to the use of AI coding tools.

The online retail giant says there has been a trend of incidents in recent months characterized by a high blast radius.

And again, generate AI-assisted changes.

Everybody remembers the AWS outage a couple of weeks ago where all the sites were broken, the website, the internet was basically down for three, four hours.

When we woke up, I can only imagine what it was when we were sleeping.

So this- Do we know that was AI related?

That was the one where they redid their AWS infrastructure.