> but harmful to late-stage developers who adopt it as dogma.

Even Robert Martin, very often in his videos and blogs, espouses "engineering judgment" and is quite fine abandoning advice in his book when the situation calls for it.

If performance is important and clean code is impacting it, he won't object to your breaking the rules.

It's mostly with his TDD evangelism that he goes (a little) crazy.