It went from one extreme to the other. Is not cleanest code or its opposite. You have a gradient of options in how you'd code. Here is another way to present t

It went from one extreme to the other. Is not cleanest code or its opposite. You have a gradient of options in how you'd code. Here is another way to present the issue discussed by the author: Every level of indirection you add will have a cost for the next developer that needs to extend or maintain it. If, for whatever reason (making code "cleaner" for example) you didn't do it gracefully/welcoming/invinting-to-change/self-docummented enough, then you increased costs, which is the same as being aggressive to business margins. So what's a more interesting conclusion? Get over childish reactions of saying "goodbye clean code" but embracing improved discernment on when and how to introduce it.