[mateo-]

To play devil's advocate, I frequently see people throw software and automation at problems that could've been solved with a system/design change. "We make 20 of these widgets a day, they take too long to make, let's automate it!" Unfortunately the first questions aren't always "why do we make these widgets?" or "do we have to?"

Lots of out of touch leadership types automate away system design flaws IME. Rather than automating for speed or consistency.

[rektide]

Sure, no code is great when it works. Usually though I think there is a real calling for forward motion, for getting better, not unwinding & disassembling.

Reagrdless of whether we agree here, the question stands of what we do when action is required.