惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

B
Blog RSS Feed
有赞技术团队
有赞技术团队
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
Y
Y Combinator Blog
Jina AI
Jina AI
G
Google Developers Blog
Last Week in AI
Last Week in AI
博客园 - 叶小钗
H
Hackread – Cybersecurity News, Data Breaches, AI and More
L
LangChain Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
V
Visual Studio Blog
aimingoo的专栏
aimingoo的专栏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
J
Java Code Geeks
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
The GitHub Blog
The GitHub Blog
D
Docker
量子位
罗磊的独立博客
腾讯CDC

Software Design: Tidy First?

Formal Methods Pay Off Reject Change, Sometimes Baking a Model Busy is Short Volatility Speculative Short Volatility & Neglectful Short Volatility Canon 3X: Explore/Expand/Extract How Do You Know That? Long Vol: What is Volatility? Long Volatility Development The Beginnings of an Idea: XP is Long Volatility When Complaints Are Good News Air Traffic Control The Cost YAGNI Was Never About Why So Literal? Smalltalk Genie Hey, N00b, We Didn't Hire You to Complete Tasks A Learning System Made of Learning Parts You Don't Get to Create Anything Trust Factory Genie Lessons from Genie Sessions: Prose as a Programming Language Scope Is The Steering Wheel Itchy Brain Thinkies World Congress II: May 20, 2026 Thinkie: Wider Scope Thoughts, Not Thinking? Did We Do This to Ourselves? Adaptive Radix Tree Genie Sessions: Run, Right, and Fast for the Adaptive Radix Tree Unstick Your Stuck Thinking Genie Tarpit
Genie Lessons: Nobody Wants Agents
Kent Beck · 2026-04-23 · via Software Design: Tidy First?

Genie Lessons from the Genie Sessions — every Friday I work on a real problem with an AI tool, live, for paid subscribers. Every Monday the lesson drops here, free.

Nobody wants agents. Nobody wants agent swarms. I have a system and I want it to change. That’s the whole thing.

This session I was using Intent by Augment Code — multi-agent, coordinator plus implementer plus verifier. Working on an adaptive radix tree in Go, optimizing for human readability. The coordinator delegates, the implementer runs off and builds things, the verifier checks. I called it the Freudian architecture: id, superego, ego. The id rushes ahead. The superego folds its arms. The ego negotiates. It kind of works.

But watching the swarm spin up, I noticed something. I was managing it. Watching which agent was doing what. Wondering when to interrupt. Holding state in my head that the system should have been holding for me. I’d said I wanted readable code and instead I had a coordination problem.

The mismatch is this: when I was working on performance last week, what I actually wanted was — how much faster can we make this? How hard would it be? How much would it cost? Outcomes. I don’t want to prompt-engineer my way toward an answer. I want to describe the result I’m after and have the genie tell me if it’s achievable and what it would take. I’ve never been able to get two agents working on the same codebase at the same time without my head exploding. So I’m not convinced the swarm is the answer.

Multi-agent is a feature. Outcome-orientation is the thing the feature is supposed to deliver. We keep getting those confused.

The other frontier nobody’s working on yet: multiplayer. Right now, five agents can work on this codebase simultaneously. Five people can’t. That’s backwards. The person who figures out real-time collaborative augmented development — where multiple humans actually steer together, not just watch — that person is solving the real problem.

Nobody knows what that looks like. But I’m pretty sure it’s not a coordinator with finger guns.

This Genie Session was sponsored by Augment Code.

Intent is the AI coding tool built for the way software actually gets written now. Describe what you want. Intent handles the rest — planning, implementing, verifying — so you stay focused on outcomes, not orchestration.

Try it out →

Available for iOS and Android