Kent Beck on TDD origins, XP's birth, and AI's trust gap
Get the Tech newsletter
Daily tech — startups, AI labs, chips, the launches that shape the next decade. Free.
- Kent Beck created Extreme Programming, pioneered test-driven development (TDD), co-created JUnit, and is one of the authors of the Agile Manifesto — contributions that shaped modern software engineering practice.
- Kent Beck was fired from Apple in the late 1980s after joining for the Smalltalk project; Apple customers wanted C and Pascal compilers instead, and Beck says he was let go for being in "punk mode" and refusing to be a team player.
- TDD was, in Beck's telling, "rediscovered" rather than invented: he recalled an old tape-to-tape programming book trick about manually typing the expected output before writing the program, then mapped it onto his SUnit framework.
- The Agile Manifesto was drafted in 2001 at Snowbird, Utah, where Martin Fowler and Jim Highsmith wrote the values on a whiteboard during a break from a contentious group session; Beck's contribution was the word "daily."
- At Facebook, where Beck arrived at age 50, his TDD class at a company hackathon got zero signups while adjacent classes filled up — prompting him to abandon his preconceptions, relearn engineering from scratch, and stay seven years.
- Kent Beck developed the "3X" framework — explore, expand, extract — to help engineers navigate major technology shifts, and describes his career pattern as "a tree shaker, not a jelly maker" who starts things, pushes them to takeoff, then moves on.
- Kent Beck argues that current AI-driven development is failing to accumulate trust at the same rate as new code, and contends that software engineering is about far more than writing code — building confidence, connections, and domain understanding.
Why it matters: Beck's framing recasts the AI-coding debate as a verification crisis rather than a productivity story: teams are generating code faster than they can build confidence in it, and his insistence that the human side — communication, judgment, trust — is the load-bearing part of the craft gives engineering leaders a vocabulary for pushing back on raw output-volume metrics.
