Clean code is specifically a book about how to write code well. This isn't criticizing writing clean code, but specifically what that book recommends programmers do.
I wouldn't say the mission of trying to create "clean" code is a bad one. Certainly there is terrible code to read and maintain, which implies there are good ways to write code.
I completely understand that it's about a specific book. My beef is with the fluffy, imprecise language that gets used when discussing quality standards.
I wouldn't say the mission of trying to create "clean" code is a bad one. Certainly there is terrible code to read and maintain, which implies there are good ways to write code.