Semantic overload is a weird but effective attack on human thought. Whenever I voice criticism of 'Clean Code', a lengthy, awkward and difficult conversation f

Semantic overload is a weird but effective attack on human thought. Whenever I voice criticism of 'Clean Code', a lengthy, awkward and difficult conversation follow, where I must clarify that I don't dislike writing code that is 'clean', I dislike writing code according to the whims of some dude who wrote a bunch of random practices down in a book he titled 'Clean Code'. It never goes over well, and my chances of success are inversely proportional to how technical the conversation partner is, and how much of an agenda has. When a non-technical manager 'helpfully' suggest I adopt best practices from this book to improve code quality, a special kind of pain arises in my soul. I know I'm not alone in this struggle, the ways of defeating this menace has escaped a generation of programmers. Same goes for Agile.