Put your pride aside and comment your code for good
itty.bitty.site
itty.bitty.site
If I'm going to make a comment, it better be worthwhile. A heuristic I find useful is "why, not what". That is, if the code has an unusual but justified feature, place that justification in a comment.
Sounds like the author is waist-deep in a crusty old codebase, but I'm not sure comments on every line are necessarily the solution.