From what I've seen, most developers either aren't systems thinkers or are too busy to take a step back and spot and eliminate redundancy. The best way I can ex

From what I've seen, most developers either aren't systems thinkers or are too busy to take a step back and spot and eliminate redundancy. The best way I can explain this is that many software processes and pipelines within companies are usually complex Directed Acyclic Graphs and very often Transitive Reduction [1] is not applied to these processes. At the end of transitive reduction, you end up with a graph with all redundant dependencies removed but functionally, it is still the same graph. [1] https://en.wikipedia.org/wiki/Transitive_reduction https://en.wikipedia.org/wiki/Transitive_reduction