Skip to content
loading...

re: Philosophy of a Good Developer VIEW POST

TOP OF THREAD FULL DISCUSSION
re: you make a lot of good points I especially agree with 1) no blame game 2) look at the bigger picture 3) thinking about others 4) write stuff down. ...
 

Totally agree. Good points in the article, but the second one is a big no-no.
Comments make the code harder to read, not to mention obsolete comments.

 

Please Gabor, don't tell me the comment "Represents a Book" in the article didn't immediately make the "function Book(title, author)" code instantly more understandable??? :-)

Comments IMO should be all about the "why" and not the "what" or "how".

+1 to linking to SO solutions where appropriate.

code of conduct - report abuse