20% on failures, 60% on work that wouldn't be necessary if we didn't have to work around all the inefficiencies, incompatibilities, limitations, poor practices,

20% on failures, 60% on work that wouldn't be necessary if we didn't have to work around all the inefficiencies, incompatibilities, limitations, poor practices, bad design, etc Just one example: all the time you spend building and maintaining a configuration management system to "fix" system state. Versus an immutable system, that when its state is wrong, you just delete it and make a new copy from the old immutable state. 90% toil becomes 10% toil. That's what good design gets you.