re: #268 kirkspencer

Yeah, positive messaging instead. “Comment your code so we know what the hell you were doing once you leave us for the better job I was supposed to get.”

///

I’ll admit, I generally had commenting code, especially with the documentation standards my company put into place a while back that means making a change to an existing program can mean spending more time documenting everything already there that was never documented than I do actually making my code change. That being said, good documentation can really help in some places, although I suppose that’s often when the code in question is a terrible mess to start with, so maybe fixing the latter is a better idea.