📎 Webclip
Developers Shouldn’t Measure Twice, Cut Once
The post starts from a fireplace tiling job to show why measuring twice makes sense for physical work. A wrong tile cut wastes material, time, and effort, so checking measurements first avoids rework.
It then shifts to programming and argues that the same approach does not fit software. Code is flexible and can be changed later, so developers should make a rough estimate and start building. The post says long estimation meetings and detailed planning waste time, while developers learn more after they begin coding.
Reading notes#
- Physical work benefits from careful measurement because errors are costly and hard to reverse.
- In software, estimates are often wrong, even when teams spend a lot of time producing them.
- Code can be expanded or reduced later because it is flexible and mutable.
- Planning meetings and requirements sessions can take time away from actual development.
- The post argues that management often relies on estimates that are not very useful.
- It favors rough estimates followed by doing the work, instead of extensive upfront measuring.
