Forest and desert: matching engineering advice to the ground it grows in

## Spark

Kent Beck's *Forest & Desert* highlights (advice aimed at the desert vs advice aimed at the forest), the Spotify Engineering Culture video, and a finished read of *Tuckman's Development Sequence in Small Groups* all landed in one window.

## Why it could be interesting

The claim: most engineering advice is context-bound — a practice that thrives in a "forest" org rots in a "desert" one, and prescribing across that line backfires. Tuckman (forming/storming/norming/performing) and the Spotify model are two attempts to *name the ground* before prescribing. The angle worth chasing is how this reads for a team-of-one-plus-agents, where the "team" dynamics are with tooling, not people.

## Open questions

- [ ] Is forest/desert the same axis as Tuckman's stages, or orthogonal?
- [ ] What does forest/desert mean when the team is one human plus parallel agents?
- [ ] Does *The Art of Business Value* add a third lens or restate the same idea?

## Source material

- Readwise: Forest & Desert (Kent Beck) — https://read.readwise.io/read/01kxnywcgeg7r0hn1mvjzftds2
- Reader: Spotify Engineering Culture (Kniberg) — https://read.readwise.io/read/01k09mafwy88q02maw6e9bkn2a
- Finished: *Tuckman's Development Sequence in Small Groups*
- Reading (active): *The Art of Business Value*