3 ms·
I saw somewhere that you guys had All Hands where juniors were prohibited from pushing AI-assisted code due to some reliability thing going on? Was that just a
by jgilias 7mo ago
I saw somewhere that you guys had All Hands where juniors were prohibited from pushing AI-assisted code due to some reliability thing going on? Was that just a hoax?
- etoxin 7mo agoNot a hoax, saw it in the news. I'm not at Amazon but can confirm massive productivity gains. The issue is reviewing code. With output similar to a firehose of PR's we need to be more careful and mindful with PR's. Don't vibe code a massive PR and slap it on your coworkers and expect a review. The same PR etiquette exist today as it did years ago.
- erklik 7mo agohttps://www.aboutamazon.com/news/company-news/amazon-outage-ai-financial-times-correction https://www.aboutamazon.com/news/company-news/amazon-outage-... About All Hands : > Much of the coverage of the service incidents has focused on a weekly Amazon Stores operations meeting and a planned discussion of recent outages. Reviewing operational incidents is a routine part of these meetings, during which teams discuss root causes with the goal of continuing to improve reliability for customers. This is something that's a part of every FAANG afaik. I know for a fact that there's no prohibition on pushing AI-assisted code. How would that even technically work? It'd basically mean banning Kiro/CC from the company. > Only one of the incidents involved AI-assisted tooling, which related to an engineer following inaccurate advice that an AI tool inferred from an outdated internal wiki, and none involved AI-written code. and this doesn't seem as "AI caused outage" as it was portrayed.
- senderista 7mo ago“outdated internal wiki” has to be responsible for so many AMZN outages…
- erklik 7mo agoShows how although AI is great, good ol' issues that we had in human-coding times are still persistent and problematic even during the AI-age.