You cannot reduce software engineering to an algorithm[1], because if you could, you could (duh) write a program to automate it and not have to worry about it.

You cannot reduce software engineering to an algorithm[1], because if you could, you could (duh) write a program to automate it and not have to worry about it. That's why the job is so hard: you have to think about the specific case and decide the best course of action. Sometimes (maybe often), DRY is the right solution; sometimes not. Same for all the other "rules" of software engineering. I think the OP is just reinforcing this: don't go on autopilot--think! [1] Obligatory disclaimer: Eventually AGI will reduce software engineering to an algorithm, but not today.