|
|
|
|
|
by moocow01
4934 days ago
|
|
This doesn't address the practical real-world problem... Most developers are under at least moderate pressure to deliver and usually their priority is this... 1) Make thing appear to work 2) Make thing actually work 3) Clean up code to pass a code review or not be yelled at by a coworker 4) Comment where things are necessary In many cases we barely get past step 1 and a half and usually its not even our fault - the business case has been mostly satisfied and according to the mucky mucks its best to move onto the next feature. Yes most of us dream of places where we can craft our code to oblivion but its probably not the average reality unfortunately. I think its great when somebody takes the time to comment - commenting is not fun and has very little upfront reward but can be a lifesaver when traversing complex logic. If you have the ability to leave a profuse amount of comments I can hide them when I dont need them and use them when I have no idea whats going on - comment as much as you like. |
|