Praying for well-commented code
Today, I finally get to restart on one of the major projects that I need to finish. For the five weeks, we’ve been putting out one huge fire so I’ve not had a chance to work on it.
Now I realize I have no clue where I left off, and don’t remember how all the code works. That’s one reason it’s good practice to comment the code, so it’s easier to see what the code does and why. (Believe me, this is an absolute necessity when looking at other people’s code.)
This was found at the top of one of the functions:
/// TODO: FINISH IT.
Good times.
wtf? you’re lucky they even put in that line of comment.
Comment by Allen | 20 July 2007
Oh, that’s a comment I left for myself. It should have said
/// TODO: START IT, because the function was completely blank.Fortunately, for the rest of it, I had mostly written pretty decent comments.
Comment by Donnie Briggs | 20 July 2007
try this comment - “mailed warn card (JR)”
even if you worked in my office you’d be like wtf
I’m reading HP now. don’t talk to me.
Comment by annie | 21 July 2007
WTF?
Comment by Donnie Briggs | 22 July 2007