Kent Beck, creator of Extreme Programming and Test-Driven Development, joins Gergely Orosz to discuss how AI is changing software development and what it means for practices like TDD.
Kent Beck’s AI Journey
Kent has been actively experimenting with AI coding tools:
- Started skeptical, became increasingly impressed
- Uses AI daily for coding tasks
- Sees both opportunities and challenges
TDD in the AI Era
Does TDD Still Matter?
Kent’s perspective on TDD with AI tools:
- Tests as specification: Tests describe what you want, AI generates implementation
- Red-Green-Refactor evolves: The cycle changes but principles remain
- AI can write tests too: But human judgment on test quality matters
New Workflows
How TDD adapts to AI:
- Write test (human)
- AI generates implementation
- Human reviews and refines
- Iterate
AI Coding Agents
Kent’s thoughts on autonomous coding agents:
Current State
- Agents can handle simple, well-defined tasks
- Struggle with ambiguity and context
- Best for repetitive, mechanical work
Future Potential
- Will improve at understanding intent
- May handle larger chunks of work
- Human oversight remains essential
The “Taste” Problem
- AI lacks aesthetic judgment
- Can’t distinguish elegant from merely functional
- Humans provide the “taste” layer
Programming as Thinking
A key insight from Kent:
“Programming is thinking. AI can help with the typing, but the thinking is still ours.”
What AI Can’t Replace
- Understanding the problem domain
- Making architectural decisions
- Knowing what to build vs. how to build it
What AI Does Well
- Boilerplate generation
- Syntax and API lookup
- Pattern application
Practical Advice
For Individual Developers
- Experiment actively - Try AI tools on real work
- Maintain skills - Don’t let fundamentals atrophy
- Focus on judgment - That’s your value-add
For Teams
- Share learnings - What works, what doesn’t
- Update practices - Adapt workflows to include AI
- Keep testing - AI-generated code needs verification
On Software Craftsmanship
Kent reflects on craft in the AI age:
- Craft isn’t about typing speed
- Understanding and judgment define expertise
- AI raises the floor, humans raise the ceiling
The Economics of AI Coding
Interesting discussion on costs:
- AI tools have real costs (API calls, subscriptions)
- ROI varies by task type
- Not always cheaper than human coding
Looking Forward
Kent’s predictions:
- Short term: AI as sophisticated autocomplete
- Medium term: AI handling larger code chunks
- Long term: Fundamental shift in what “programming” means
But throughout: human judgment remains central.
Notable Quotes
“The best code is code you don’t have to write. AI helps with that.”
“Tests are a conversation with the future. AI doesn’t change that.”
“I’m more optimistic about AI than I expected to be, but also more cautious.”
Kent Beck,极限编程和测试驱动开发的创始人,与Gergely Orosz讨论AI如何改变软件开发以及这对TDD等实践意味着什么。
Kent Beck的AI之旅
Kent一直在积极尝试AI编码工具:
- 开始时持怀疑态度,后来越来越印象深刻
- 每天使用AI进行编码任务
- 看到机遇和挑战并存
AI时代的TDD
TDD还重要吗?
Kent对AI工具下TDD的看法:
- 测试作为规范:测试描述你想要什么,AI生成实现
- 红-绿-重构演变:循环改变但原则不变
- AI也能写测试:但对测试质量的人类判断很重要
新工作流程
TDD如何适应AI:
- 编写测试(人类)
- AI生成实现
- 人类审查和完善
- 迭代
AI编码代理
Kent对自主编码代理的看法:
当前状态
- 代理可以处理简单、定义明确的任务
- 在模糊性和上下文方面有困难
- 最适合重复性、机械性工作
未来潜力
- 将改进对意图的理解
- 可能处理更大块的工作
- 人类监督仍然必不可少
”品味”问题
- AI缺乏审美判断
- 无法区分优雅和仅仅功能性的
- 人类提供”品味”层
编程即思考
Kent的关键洞察:
“编程是思考。AI可以帮助打字,但思考仍然是我们的。“
AI无法替代的
- 理解问题领域
- 做出架构决策
- 知道要构建什么vs如何构建
AI做得好的
- 样板代码生成
- 语法和API查找
- 模式应用
实用建议
对个人开发者
- 积极实验 - 在实际工作中尝试AI工具
- 保持技能 - 不要让基础技能退化
- 专注于判断 - 那是你的附加值
对团队
- 分享学习 - 什么有效,什么无效
- 更新实践 - 调整工作流程以包含AI
- 继续测试 - AI生成的代码需要验证
关于软件工艺
Kent反思AI时代的工艺:
- 工艺不是关于打字速度
- 理解和判断定义专业知识
- AI提高下限,人类提高上限
AI编码的经济学
关于成本的有趣讨论:
- AI工具有实际成本(API调用、订阅)
- ROI因任务类型而异
- 并不总是比人类编码便宜
展望未来
Kent的预测:
- 短期:AI作为复杂的自动补全
- 中期:AI处理更大的代码块
- 长期:“编程”含义的根本转变
但始终:人类判断仍然是核心。
值得注意的引言
“最好的代码是你不必写的代码。AI在这方面有帮助。”
“测试是与未来的对话。AI不会改变这一点。”
“我对AI比预期更乐观,但也更谨慎。”