This article is true for it's message: It's not clean and require documentation.

Jokes aside, even human language requires documentation. It depends on the problem domain. Even "hello" - "hi" can be misunderstood if spoken in some foreign language.

Clean code requires a context. New developers starting to work seriously on some codebase will still prefer clean and repeatable structure over documented spaghetti. The more the code reminds spaghetti, the more code is needed to write the new code, and more documentation needed.

Ideally developers should be able to read the code, not only write it. Sounds trivial. Especially in higher level languages. Familiar patterns, naming conventions can eliminate a lot of comments.

Of course, advanced algorithms and techniques may need comments. But this is not against clean code principles.