Oh lol, it strips out comments.
There is a load of code that goes like this....
<!-- WOO YAY -->

If you read my comments on my code, I write like I'm writing to myself.

// Right, now we're going to grab the user
[code to grab the user]
// Now we're going grab the _POST data and strip it
[code to do blah blah]
// Let's update it now
[code to update
// Did it work? Let's plonk up the All Done message
[All done message]
// Refresh the user vars
[code to refresh user vars]
// Right, sorted, continue on as usual.
[code to continue
( G/PP &#128169;&#128169;&#128169;&#128169;&#128169;&#128, Sat 30 Oct 2010, 11:43, 1 reply, 15 years ago)

I'm glad to say that this looks impressive, but I don't understand a single bit of it.
I think I see what you are doing though, in very general terms.

Please don't bother to educate me, I'm happy to remain ignorant in this case.
( Bartleby A dead man on vacation, Sat 30 Oct 2010, 11:48, Reply)

Heh, cool, it's just that I write bits in the code that read like a short paragraph story so when I look back it's ovbouse.

( G/PP &#128169;&#128169;&#128169;&#128169;&#128169;&#128, Sat 30 Oct 2010, 12:03, Reply)

Those are the bits I understood.
Where I work, the engineers delight in putting no comments or even decent titles in the software. This ensures they get called out when something goes wrong and no one can understand the programme.
( Bartleby A dead man on vacation, Sat 30 Oct 2010, 12:05, Reply)

I used to do that, but now I try not too because I look at it like this....
"[Company] are paying for the code, they own it. Although it's nice that they would have to come to me and I can charge what I want 'cus they'd be desporate... it's a bit like getting a builder in to paint your living room and he choosing a colour that only he can supply, even though you're the one paying for the paint".

Sometimes I can't help it, like I made a short function to do something (won't bore you with the details), and I called it the SQLCodeSelectStringCreator, which makes sense to people who know what code is, but I had to type that out 30 odd times so I just called it "SSC" (the 'SQL Code' bit being ignored), which means that nobody outside of my head would know what that does without looking at that function.

The trouble is, when Developer 2 comes along, they'd ask me what on earth that does, which means it takes more time explaining it.
( G/PP &#128169;&#128169;&#128169;&#128169;&#128169;&#128, Sat 30 Oct 2010, 12:11, Reply)

Good analogy.
The other month I refused to pay a contractor who finished a job, left it working, and sent me the code. It had no words on it at all. I had written in the specification that a description of the code was required. His reposte that "it works, doesn't it?" cut no ice with me.
( Bartleby A dead man on vacation, Sat 30 Oct 2010, 12:17, Reply)