↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

The Parable of Painting an Office

The author presents a non‑technical parable about estimating work using the example of painting a small office. At first, the reader is asked to estimate painting time based only on room size and desired color. The story then reveals overlooked tasks one by one: buying supplies, moving furniture, taping and covering surfaces, painting the ceiling, and applying and waiting for a second coat. Each missed step forces a revision of the original estimate.

The moral is that people usually estimate work at too coarse a level, ignoring many required steps. Even with careful effort, estimates for individual tasks can be wrong, and omitting entire activities has a much bigger impact on delivery time. If a simple painting job hides so many steps, a large, interconnected software system can hide many more. Breaking work into smaller pieces reduces the chance of missing steps, but “small enough” is far smaller than most assume, and estimation still fails in many ways. For software projects, the author concludes that estimation is such a hazardous game that the safest approach is to avoid playing it at all.

Reading notes
#

  • The author shifts from technical topics to a non‑technical theme: estimation, which many stakeholders want but rarely receive accurately.
  • A parable is introduced where the reader is asked to imagine being hired to paint the author’s small office.
  • Initial information given for the estimate is room size and desired paint color, prompting the reader to guess total hours needed.
  • After the first estimate, the author points out that time to buy supplies like paint, brushes, tape, and covers is usually omitted and must be added.
  • Next, the parable highlights the need to move furniture away from the walls, another task likely missing from the original estimate.
  • Additional preparation work such as taping baseboards and covering the floor with plastic is raised as another commonly forgotten time cost.
  • The author asks whether the ceiling was included, noting that leaving it unpainted would look strange, so its painting time also needs to be added.
  • The story then introduces the need for two coats of paint, including drying time and repainting all walls and the ceiling, further extending the estimate.
  • Through these added steps, the office ends up beautifully painted, but only after repeated corrections to the initial time estimate.
  • The author argues that estimation efforts usually lack enough detail to achieve accuracy, even when people try very hard.
  • A distinction is made between wrong time guesses for known tasks and the more serious issue of missing entire steps in the process.
  • The example of painting is used to suggest that if such a simple task hides many steps, complex, interconnected web applications hide far more unknowns.
  • Common advice says breaking work into smaller pieces reduces missed steps, and the author agrees this approach helps.
  • However, the author notes that the size considered “small enough” is usually much smaller than people assume, and even then estimates can still fail.
  • The author concludes that while breaking work down improves estimation, it does not make it reliably accurate.
  • Drawing on the film War Games, the author likens software estimation to a dangerous game where the best strategy is to avoid playing.