Could you please stop posting unsubstantive, shallow criticisms? So far all 3 of your comments have been of this sort, and we're trying for more thoughtful conversation here.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

Note this one: "Don't be snarky."

Unreliable software is also expensive. Rather, building reliable software is incompatible with a management policy that rewards and punishes people based on KPIs (basically leading indicators). The concept of KPIs is fine, but they should (a) be actual indicators of progress, and (b) be kept secret from employees (so that we can avoid or mitigate Goodhart's Law). Both of those things are difficult, because you need a rigorous statistical model of what correlates, and you need to keep that model a secret, while also changing the KPIs periodically, to prevent employees from intuitively overfitting. That whole process would be very expensive (and if it would not, why is nobody doing it).

Furthermore, software that is reliable, is also software that is done (in the sense that AVL Trees, and ZFS, and DTrace, and ZSTD, and slab allocators are done -- they are very close to perfect, and require minimal changes, related to compilers and kernels and computer architectures). A team that builds reliable software, is a team that cannot be "managed". What exactly is there to manage?