Confining codebase 'gardening' to one person creates failure cases
vboykis · x · 2026-08-22
Responding to the idea that every team needs a dedicated "gardener" to manage PR streams and code smells, Jamie Duke argues against assigning this role to a specific person. He highlights a specific failure case: the work becomes illegible (invisible), and the gardener gets passed up for promotion because their contributions are hard to measure. His stance is that if the codebase is a garden, then everyone working on it should be a gardener.
More from Companies & People
- MLHacks Co-founder: AI Could Enable a Billion New Software Creators — Arindam_1729 · 2026-08-22
- Prediction: Next week to be major release week for OpenAI and SSI — rand_longevity · 2026-08-22
- Indie dev pivots business model, aims for $100k MRR — djcows · 2026-08-22
- Gary Marcus Questions Anthropic's ARR Metrics — GaryMarcus · 2026-08-22
- Workplace 'AI-blindness': Low-quality AI docs causing reading fatigue — bibryam · 2026-08-22
- Tracking AI coding tool spend for 60 days revealed hidden costs — FlyLess9643 · 2026-08-22