These tasty fuckers better be served at 898 degrees Fahrenheit so that every Millennial and Gen Z person burns their lips, tongue, and mouth roof so bad they can understand what the 70s and 80s were like.
UPS: “Your package is in your city, on a truck driven by Mike. It will arrive on your doorstep at 6:27 p.m. today.”
FedEx: “Your package is coming. You’ll get it when we get there.”
USPS: “What package?”
Amazon: “We are already inside your apartment. Check the bathroom.”
Facebook: “We know you were thinking about getting a toaster yesterday. Here are 20 ads for toaster ovens.”
Welcome home Reid, Victor, Christina, and Jeremy! 🫶
The Artemis II astronauts have splashed down at 8:07pm ET (0007 UTC April 11), bringing their historic 10-day mission around the Moon to an end.
The Artemis II crew named a lunar crater after Commander Reid Wiseman's late wife, Carroll. What a beautiful and touching moment.
I'm not crying, you're crying 🤧
This is the most important signal in AI right now, and most people are reading it wrong.
The story isn't "AI broke Amazon."
The story is that the largest cloud infrastructure company on Earth, spending $200 billion on AI this year, still hasn't solved the governance layer between AI-generated code and production systems.
The timeline tells you everything:
→ Amazon mandated 80% weekly AI coding tool adoption
→ Their own Kiro agent was given operator-level permissions with no peer review
→ It autonomously deleted and rebuilt a live AWS environment. 13 hours of downtime.
→ A second AI tool incident followed months later
→ Last Thursday, the retail site went down for 6 hours. 21,000+ users locked out of checkout.
→ Today, a mandatory all-hands to address "a trend of incidents" they can no longer downplay
Amazon's fix: junior and mid-level engineers can no longer push AI-assisted code without senior approval. They're calling it "controlled friction."
That phrase alone should be on every engineering team's wall.
The companies winning with AI coding tools aren't the ones moving fastest.
They're the ones who built review gates, permission boundaries, and deterministic checks before handing agents the keys to production.
Speed without governance isn't velocity. It's liability.
Every team deploying AI in their dev workflow should be asking three questions right now:
What permissions does our AI tooling actually have?
Is there a mandatory human checkpoint before any destructive operation?
Are we tracking AI-assisted changes separately in our deployment pipeline?
Amazon learned this in production. You don't have to.
@DIRECTVhelp leased devices are involved but i think the root issue is i had an account, canceled years ago, now trying to reestablish service, not going very well. not a browser problem. :)
How is it in the modern era when streaming companies are fighting for customers, @DIRECTVhelp@DIRECTV is like impossible to sign up for? Web Screen order processing errors that don't point to actual issue, credit pulls for streaming? Support agent couldn't even do it. WTF