re: Good comments explain WHY, not WHAT, and 3 more rules on writing good comments VIEW POST

FULL DISCUSSION
 

Great article. I don’t fully agree with developers leaving their name, since the code and comments would go through a peer review under most processes. It’s essentially the team’s code, and the developer’s name would just be clutter once the team accepts the code and comments in a peer review.

Lots of good points in here though.

 

in general agree
but most knowledge work has fragments of informations that you don't represent in the artifacts you create
or differently put: need to know more -> that person will know more

git blame never really worked for this imo

code of conduct - report abuse