Re:Inefficient Efficiency (2019)
by absolute100 on Saturday May 08, 2021 @11:56AM
(#27088275)
Kent Beck wrote a post that represents exactly how I feel about software development: "By emphasizing latency [of process] we get feedback sooner. Learning and adapting to external changes lead to less waste and therefore greater efficiency. Each piece is inefficient (compared to some theoretical maximum), but the whole is efficient. In my world, latency dominates. Mostly. But it depends." (4 minutes read.)
[ Parent
| on HN ]
Another way to look at emphasizing latency/feedback is to "increase learning". There's a great book, Lean Software Development: An Agile Toolkit, that covers this.
The idea is that there are so many unknowns within a project, that organizations should aim to move quickly enough to uncover them sooner. A lot of these unknowns lead to constraints that have profound effects on designs, so if you delay learning them, you are more likely to have to re-do designs deeper in the process, when it is more costly. The sooner you discover them, the more likely you will have the flexibility to account for them in the design.