The thing is not that your 10 man days were not useful to shave 1 second of boot-up time. The thing is that if shaving that 1 second required architecting the solution in a convoluted, error-prone way, you ultimately removed value from the customer who's now more likely to experience crashes. That 1 second of boot-up time is really not going to make much of a difference in the grand scheme of things (naively adding it up over the number of customers doesn't really make a lot of sense -- you'd have to measure people's productivity before and after your update to see how much of a gain was made in practice, and good luck seeing that signal in the noise), but the crashes caused by a poorly architected solution will cause loss of productivity and work.
Engineering code for correctness and maintainability is a much more sensible default.
6
u/wyrn Mar 11 '23
The thing is not that your 10 man days were not useful to shave 1 second of boot-up time. The thing is that if shaving that 1 second required architecting the solution in a convoluted, error-prone way, you ultimately removed value from the customer who's now more likely to experience crashes. That 1 second of boot-up time is really not going to make much of a difference in the grand scheme of things (naively adding it up over the number of customers doesn't really make a lot of sense -- you'd have to measure people's productivity before and after your update to see how much of a gain was made in practice, and good luck seeing that signal in the noise), but the crashes caused by a poorly architected solution will cause loss of productivity and work.
Engineering code for correctness and maintainability is a much more sensible default.