Every wondered which model is best for Laravel and how much does Boost actually help?
We had the same question - here's what we found out. 👀
https://t.co/516OzFtkCF
Amazon had four Sev-1 outages (their highest severity level) in a single week. Internal memos say AI-assisted code changes were a contributing factor.
The timeline here is wild. In October 2025, Amazon laid off 14,000 corporate employees. In January 2026, another 16,000. That’s about 30,000 people in five months, roughly 10% of the corporate workforce. CEO Andy Jassy said the cuts were about culture, not AI.
During those same months, Amazon set a target: 80% of developers using AI coding tools at least once a week. They tracked adoption closely and blocked rival tools like OpenAI’s Codex. Even so, 30% of developers still hadn’t touched Amazon’s in-house tool Kiro by January.
In December 2025, Kiro caused a 13-hour AWS outage. The AI tool had production-level permissions and decided the best fix for a bug was to delete and recreate an entire live environment. A second incident involved Amazon Q Developer, another AI tool. Amazon blamed both on “user error, not AI.” But quietly added mandatory peer review for all production access afterward.
Then March 5: Amazon’s retail site went down for about six hours. Over 22,000 users reported checkout failures, missing prices, and app crashes. Amazon called it a “software code deployment” error.
Five days later, SVP Dave Treadwell made the normally optional weekly engineering meeting mandatory. His memo acknowledged “GenAI tools supplementing or accelerating production change instructions, leading to unsafe practices.” These problems trace back to Q3 2025. Amazon’s own assessment: their GenAI safeguards “are not yet fully established.”
The new rule: junior and mid-level engineers now need senior sign-off on any AI-assisted production changes. Treadwell also announced “controlled friction” for the most critical parts of the retail experience.
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh.
They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service templates, the whole shebang.
The whole senior engineering leadership came from Amazon, where they were used to each team owning a distinct service. They tried to apply that model directly. But our issues were with code ownership and poor domain modeling.
The entire application could have run on just a handful of EC2 instances.
What was the result?
Five years later, 70% of the application is still running on the Ruby on Rails monolith. Never completed the migration. But now they have to maintain two systems.
None of the original leadership works there anymore.
Sad to share @weaverryan passed away peacefully this week surrounded by loved ones.
Celebration of life will be held Sunday, Sept 7th, 1–4pm at WildWood Family Farms, 7970 Snow Ave SE, Alto, MI 49302.
If you’re able, please donate to his son’s fund: https://t.co/dZfbhN2TpG
Here is my favorite picture of Ryan for your viewing pleasure!
All product engineers I've worked treated some jobs beneath them.
Until Laravel.
- They jump on support tickets.
- They volunteer for double shifts at conference booths.
- They give feedback without the snark.
- They want roadmap requests from sales & marketing (they care about the business).
- They talk to people (on Twitter, Reddit, LinkedIn, & IRL), not just for feedback, but to build a welcoming Community.
- And the CEO leads by example.
Hard to quantify, but the impact is definitely massive.
The best startups already do this:
- Linear: has a zero bug policy and a "goalie" role (dev who fixes all reported bugs, fulltime, on rotation).
- Figma: zero bug policy for new features + "quality weeks"
Did deepdives on both in @Pragmatic_Eng , check them here: (cont'd)
It'd be nice to see more library authors take advantage of `currentScript` like this. It'd prevent a few headaches for users who install them incorrectly (assuming loading strategy matters).
We shipped a cache memoization feature to Laravel today. 🚀
Cache::memo let's you decorate any cache store with a memoized wrapper, allowing you to temporarily store resolved cache values in memory during a single request or job execution. This prevents repeated cache hits within the same execution
This week's banger is courtesy of @timacdonald87.
https://t.co/WvsIXSesBh
Yesterday I helped a friend with their startup's single server going down after an update. Turned out the contractor's AI generated code loads over 12k records from the database and presents them in JSON responses (on every request).
The pool of bad software contractors is already huge. With AI, I'm afraid it's getting even larger. I think it'll be very difficult for experienced coders to compete in contracting gigs.
To be honest, most recent generative AI announcements left me kinda unimpressed.
But Genesis - announced today - is absolutely mind blowing.
AI generated videos with correct physics?! 🤯