Last week, the developer community was busy discussing about a single tweet:
I'm not joking and this isn't funny. We have been trying to build distributed agent orchestrators at Google since last year. There are various options, not everyone is aligned... I gave Claude Code a description of the problem, it generated what we built last year in an hour. — Jaana Dogan ヤナ ドガン (@rakyll) January 2, 2026
The author is Jaana Dogan (known as Rakyll), a highly respected figure in the Google ecosystem, in the open-source world, and in my heart (thank you Rakyll for your great Go blog posts).
At first glance, the tweet suggests an enormous shift in the software industry: the ability to build in just one hour what previously required weeks or months for a team of sofware engineers, using just the description of the problem. The tweet was too-much dramatic in my own opinion, but actually impressive!
The post triggered an immediate wave of “doom-posting,” with many fearing for the future of software engineering (as each week since a year now). However, as the conversation reached a high number of replies and citations on social networks, Rakyll released a follow-up thread to provide context:
To cut through the noise on this topic, it’s helpful to provide more more context:
- We have built several versions of this system last year. - There are tradeoffs and there hasn't been a clear winner.
- When prompted with the best ideas that survived, coding agents are able to… https://t.co/k5FvAah7yc — Jaana Dogan ヤナ ドガン (@rakyll) January 4, 2026
This response thread revealed a story far less miraculous than the original tweet suggested. Let’s analyze it.
... continue reading