> until someone runs the numbers and finds something more efficient would improve performance or save money by a significant enough amount This argument must b

> until someone runs the numbers and finds something more efficient would improve performance or save money by a significant enough amount This argument must be the ultimate defense in code review. The thing is, we have the field of theoretical computer science and things like big O so that we can reason about code without having to do benchmarks about every little thing, because that's impossible in practice. Regarding protocols, I'd argue that the most important thing for them is to be efficient, at least when IO is still the biggest bottleneck of computing. The other comment already points out debug being a tooling problem.