[bradlenox]

I agree. Someone's "darling" code might be a truly innovative or unique way of solving a problem, and providing enough commentary should help avoid the problems the author warns about.

[mhurron]

It's amazing, their whole complaint is solved by proper software development practices - Comment your code.

[prodigal_erik]

Code that's clear enough not to need a comment is better than code that has a comment. Comments can be outdated or mistaken and they consume screen real estate.

[mhurron]

You still need to document intent. No code is self documenting.

[dllthomas]

In some cases, naming may be sufficient to communicate intent.

[CaptSpify]

To be fair: What is proper practice, is far from what is common practice

[TTPrograms]

Not to mention it may be a performance optimization.

[sgt101]

Which is a good reason, if that optimization is needed.