, ScanIAm wrote

Gotcha.  You write clean and correct code so those of us who might have to follow up after you can just suck it.


That is what code reviews are for.

It's called 'context'. 

Expecting the next developer to have to read pages of code just to figure out WTF you where thinking is unethical.  Doing so on a large project is counterproductive.

I know you'll want to continue to argue this, so how about we split the difference.  I won't make you comment if you won't ever work on any code I'll eventually have to fix.

Deal?


This "comments are for crappy code" idea isn't magical crap I make up the other day, it's fairly accepted idea these days in software engineering circles that comments are a crutch for poorly written code.

Here is a quote you can ponder if you like:

“The proper use of comments is to compensate for our failure to express yourself in code. Note that I used the word failure. I meant it. Comments are always failures.” --Robert Martin