Why Forest and Desert People Cannot Understand Each Other
Kent Beck’s daughter Beth, a staff engineer, pitched a project approach to her manager. The manager said it would work “if we were living in a forest, but we live in a desert.” Beck saw in that phrase something he had been missing for decades: the breakdown in XP conversations was not miscommunication. The same words, “metrics,” “compliance,” “accountability,” carry completely opposite meanings depending on which world you inhabit. Not a spectrum, not a disagreement. Parallel universes.
The Philosophical Roots of Two Development Cultures
Two old debates explain the split. Rousseau thought people are basically good and want to do good work. Hobbes thought people need central authority to force pro-social behavior. In the early 20th century, Frederick Winslow Taylor built management theory on Hobbes: smart people design work, cheap people execute it. Mary Parker Follett pushed the opposite, “power with” rather than “power over.” Forest teams assume change, pull on purpose, build community. Desert teams assume scarcity, apply pressure, enforce control. Both are internally consistent.
Metrics: Self-Awareness Tool or Pressure Weapon
Forest teams collect metrics for self-awareness: how many minutes debugging, how much time on tooling, did this experiment improve things? The team sees the data and it stays with the team. The Coinbase CEO declared 60% of code was AI-generated and demanded 70%, with consequences for anyone who fell short. Beck pointed out he would simply stop writing code by hand until 100% was AI-generated. Goodhart’s law made flesh. Metrics as a hammer produce reports, not behavior, and desert organizations cannot tell the difference.
Dependencies and Compliance: Collaboration or Cover
Dependencies between teams are invitations to collaborate in the forest. When your system needs something from another team, you go build it together. In the desert, they are excuses for failure: the security team’s queue grows so more people can blame it for slipping dates. Compliance follows the same split. Square Life, a Swiss insurance company Beck has worked with for nearly 30 years, asked its auditors how to make their job easier. Simplified terms and conditions fit one page. Result: an insurance product conceived on Friday morning, first contract sold Monday night, regulatory approval included.
Accountability, Status Reporting, and the Cost of Crumbs
Accountability’s dictionary definition is “required to render account.” In the forest that means transparency: here is how we spent the six weeks, every mistake and rabbit hole included.
“an invitation to trust.” — Kent Beck
In the desert it becomes blame. You miss the sales number, you’re fired. At one large software company, every team knew never to report green status. Green projects lost engineers to red ones. So every team reported yellow, every estimate inflated, every VP discounted it, and everyone played along. That performance takes value out of software development and leaves crumbs.
Notable Quotes
The desert is content with the crumbs. Kent Beck · ▶ 13:47
Nobody’s happy. Kent Beck · ▶ 14:13
because it grants your wishes but is not what you wanted. Kent Beck · ▶ 26:13
an invitation to trust. Kent Beck · ▶ 28:45
Key Takeaways
- Forest and desert teams use the same words — metrics, accountability, compliance — to mean opposite things, making cross-culture dialogue nearly impossible.
- Desert practices are not failures of discipline; they are rational responses to a belief in scarcity and distrust of people.
- Teams that operate in the forest consistently deliver more value, yet external pressure from desert organizations pulls oases back toward scarcity thinking.