XP Practices, TDD, and Responsibility

The State of Software Engineering 🔨 — with Kent Beck

Topic 2 of 7

Published Feb 15, 2024 · Clip 12:34–24:25 (11:52)

The discussion turns to XP practices like TDD, pair programming, and continuous integration and why they still provoke resistance. Kent argues that the emotional reactions to TDD stem from programmers being asked to take responsibility for the quality of their own work, which he sees as a healthier relationship with work than letting others pay for your mistakes. He contrasts his father's confrontational 'leave me alone' engineering style with XP's approach of building trust with business through tiny, regularly delivered slices of value. He emphasizes that pressure without feedback produces only reports of progress, not real progress, and that engineers can catch mistakes sooner via short feedback loops.