Ah yes. It is clear that the root cause of this CVE last month is a lack of spend. Lessons learned: 2.1 trillion tokens is insufficient to detect obvious malware; increase token spend by 10x.
The difference is twofold. First, junior devs who ask for code reviews on massive, 2000+ line diffs get coached, and eventually fired if they persist at it. And second, even the most prolific junior engineer would take years to write what Claude is capable of generating in an afternoon.
When Sundar Pichai announces that 75% of all new code at Google is AI-generated, their stock price goes up. If he were to announce that 75% of all new code at Google is now written by junior engineers, this would trigger a massive sell-off and a lot of employees would resign.
Not only is it a solid premise, but there is an ultrashort story by Franz Kafka that lends itself perfectly to a cinematic promo video:
TINY MOUSE-SIZED HUMAN:
"Alas! The whole world is growing smaller every day.
[Close on the tiny person, panning out ever-so-slowly to reveal, bit by bit, the cavernous enormity of the room.]
At the beginning it was so big that I was afraid, I kept running and running, and I was glad when I saw walls far away to the right and left, but these long walls have narrowed so quickly that I am in the last chamber already, and there in the corner stands the trap that I must run into."
[Corner trap now visible, the camera holds steady and dwells for a moment on this sad, bleak fate. Suddenly, there is another voice from behind -- this is not a monologue after all.]
CAT, SLINKING INTO VIEW:
"You only need to change your direction." [CAT pounces, and promptly gobbles him up.]
Thanks. I was a bit puzzled earlier why AWS was so insistent about enabling object locking, my specific use case doesn't profit from remote versioning at all. But I can see how this would mitigate log integrity concerns. I'll definitely enable it for that.
https://nesbitt.io/2026/06/26/incident-report-cve-2026-lgtm....