Discussion

• @edzitron Ed Zitron on x

  On two separate occasions Amazon's Kiro AI assistant caused an AWS outage, one that was 13 hours long. Amazon blames this on “user error not AI error,” which is one of the most embarrassing things you could ever say as a human being [image]

• @techviews @techviews on bluesky

  You cannot let the machine make decisions.  It is *not* intelligent.  [embedded post]

• @jennifercobbe Jennifer Cobbe on bluesky

  A glimpse of a future where everyone needs to use the cloud for everything because AI-driven hardware shortages have made local computing too expensive, but also AI has broken the cloud [embedded post]

• @measuredandslow Alyssa Long on bluesky

  Lol 13 hours is SO LONG in internet outage time.  Mayhap we should not have fired the people who know what they're doing 😬 [embedded post]

• @brunodias Bruno Dias on bluesky

  we're probably not far from the first case of a person being killed by actions taken by an LLM agent [embedded post]

• @parismarx.com Paris Marx on bluesky

  if generative ai takes down the cloud, i might finally have something good to say about it [embedded post]

• @segatape Leger-Felicite Snorlax on bluesky

  a fun experiment for an analyst at amazon would be to calculate the actual cost of these two outages versus the claimed savings of AI shit [embedded post]

• @impemboganecue @impemboganecue on bluesky

  go on.  keep telling me that vibecoding is the here and now.  keep insisting that it is great for anything except automating some simple personal bullshit you could've done in entry level Python [embedded post]

• @edzitron.com Ed Zitron on bluesky

  Hahahaahhaa hell yeah.  The future rules!  THE FUTURE RULES! [embedded post]

• @doubleohkevin Kevin on bluesky

  [embedded post]

• @gregpak.net Greg Pak on bluesky

  so what i'm hearing is that this “a.i.” shit sucks [embedded post]

• @fack @fack on bluesky

  Hilarious.  [embedded post]

• r/programming r on reddit

  Amazon service was taken down by AI coding bot [December outage]

• @malwarejake Jake Williams on bluesky

  My friends, if Amazon, with all its governance and change control, is getting these kinds of outcomes, (respectfully) you have no chance.  [embedded post]

• @derek.space Derek Newsome on bluesky

  Coding errors have managed to take down many a rocket in the past.  —  I am very concerned for when a company decides it's a good idea for ai to write the code for one of these machines.  [embedded post]

• @davidgerard.co.uk @davidgerard.co.uk on bluesky

  lol, AWS vibe coded itself an outage  —  www.ft.com/content/00c2...  [image]

• @runakog @runakog on bluesky

  Would be interesting to see the balance between SLA liability for the outage and money “saved” on engineering compensation.  [embedded post]

• @taryndevere Taryn de Vere on bluesky

  Amazon's AI causing problems for Amazon?  You LOVE to see it.  [embedded post]

• @maxvonthun Max von Thun on bluesky

  Amazon's cloud service suffered outages after engineers let AI assistants make key decisions.  —  The combination of highly concentrated digital infrastructure and a rushed rollout of unreliable AI technologies is going to create many more incidents like this, and worse.  —  www.…

• r/webdev r on reddit

  Amazon service was taken down by AI coding bot

• @joshuafoust.com Joshua Foust on bluesky

  Agentic AI is really going to crash the economy, isn't it [embedded post]

• @robbowley.net Rob Bowley on bluesky

  Surprised not to have heard more stories like this by now [embedded post]

• @theecatservant @theecatservant on bluesky

  AI is going to destroy not just the planet but all industries.  It's not going anywhere but it needs severely regulated and controlled.  That won't happen though because all these companies are run by morons.  [embedded post]

• @joeydantoni.com Joey D'Antoni on bluesky

  I've wondered a lot about the recent increases in the cadence of cloud outages, and I figured it's just the stress of layoffs leading to more mistakes.  Surprise, we vibe coded your cloud service. www.ft.com/content/00c2...

• @crusaderproject @crusaderproject on bluesky

  ‘Best at’ isn't ‘good at’ though.  Anything I have seen from coders is that AI is shit at coding.  —  Can't comment on that but I know it's shit at history or energy market analysis, which I can comment on.  —  Andersen has to force its senior managers to use its proprietary AI t…

• @somewhattolerable.com Rich Burroughs on bluesky

  Who could have seen it coming [embedded post]

• @johnperich.com @johnperich.com on bluesky

  I'm gonna shock the world here by agreeing with the Amazon spokesperson that this was not AI error per se - this was human error.  It's just that the humans who made the error were senior management who gave “agentic” AI the power to push to prod, not the engineer overseeing it.

• @mattocko Matt Ocko on x

  I guess the “AI for DDoS” calls are “coming from inside the house” 👀 Not the first such, nor even the most damaging, just one of the more visible ones

• @shakoistslog Shako on x

  tfw you get terrible returns and your company starts to suck [image]

• @jamiecooperatl Jamie Cooper on x

  Laughing because it really will delete files w/o asking if given access

• @boppinwtboyz @boppinwtboyz on x

  Vibe coding bby

• @the_ceo_guy @the_ceo_guy on x

  “Layoff the experienced teams and give the AI total control to make changes.” *explosions* “Well, who could have seen that coming?”

• @heymynameisrob Rob on x

  ~5 months away from completely wiping all software jobs apparently

• @mikeisaac Rat King on x

  amazon's internal A.I. coding assistant decided the engineers' existing code was inadequate so the bot deleted it to start from scratch that resulted in taking down a part of AWS for 13 hours and was not the first time it had happened incredible https://www.ft.com/... [image]

• @samlambert Sam Lambert on x

  During the outage we all heard rumors that this is what happened. I am so glad it's finally leaked. This is a serious lie of omission from AWS that demonstrates their hostility toward their users.

• @granitegeeknh @granitegeeknh on bluesky

  This is how A.I. could break civilization: Not killer robots but being integrated into everything and then making decisions for reasons we don't understand.  One screwy act feeds into another and then another and suddenly things don't work and we don't know why.  —  www.reuters.c…

• @gergelyorosz Gergely Orosz on x

  Full article: https://www.ft.com/... My two cents is: well, this proves AWS engineers are giving a Kiro an honest shot. My biggest surprise is that despite it being used for prod work, Kiro remains virtually unknown / unused outside AWS...

• @gergelyorosz Gergely Orosz on x

  This headline today reads shocking, but will soon enough be a nothingburger: When AI generates most code and more config files as well, most outages caused will be *technically* done by AI. In reality they happen thanks to inadequate verification/monitoring/rollback systems [imag…

• @leomschwartz Leo Schwartz on x

  I know this is said a lot but this is actually a Silicon Valley plotline

• @vikhyatk Vik on x

  can't believe i'm defending kiro but this is like me blaming neovim for the bug i pushed last week