re: #270 Simply Sarah

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.

It’s not just fixing it that matters. Sooner or later there will be upgrades. There will be other software competing for resources, some of which are at least supposed to integrate.

The problem is, as you said, it can take longer to document than it takes to do the code itself especially given some standards.

I’ve often wondered if things might not work better with a voice recorder that tied sound to keystrokes, then having another specialist who did nothing but enter comments using those two items (and an occasional persuasive visit to recalcitrant programmers.)