But only because if you're writing imperative code and doing lots of mutation "you should be made constantly aware of the full horror of what you are doing."

Also when applying the mantra "Dont repeat yourself" (DRY) it can have the opposit effect; that when you are optimizing a hot loop, like a game render loop you inline everything and discover there are repetitions that can be vectorized or removed/optimized. Maybe because you applied DRY and abstracted too early or what not.

Yeah... DRY is probably the most over-used principle (likely bc it's so easy to identify). I like "AHA" (Avoid Hasty Abstractions) as a counter-balance.

DAMP (descriptive and meaningful prose) is especially useful for maintaining tests. Which is where they bulk of the time investment comes.

Literally any testing strategy can be forced to work for about 18 months. Anyone working with shorter lifetimes than that is inexperienced.

I love that quote, and that article as a whole!