The *&%$#!% programmer !

after reading this article , I'm curious to know who here riddles their source code with cuss words? have you ever worked on sofware and documetented it with cuss words for something company who had no idea?

only in school projects.... especially for debug statements

I think it's quite healthy. I mean, it's almost a way to fight back against the code (obviously, it's the code's fault that it chooses not to work).

I don't swear in my comments. I just get incredibly sarcastic.

90% of my user validation error messages are designed to belittle the person

it's not a big habit or anything, but yeah... and I put easter eggs in some of my code as well as some things that show up when you break it down with a hex editor

http://www.durak.org/sean/pubs/kfc/

I use cuss words all the time when debugging, mainly because it would stand out more as opposed to other things. I rarely leave things like that in my comments, however. It's unprofessional and can put a negative spin on you later if someone with a lack of a sense of humor is rummaging through your code.

But I'm with Thantos... sarcastic comments abound throughout my comments.

Swearing in your comments makes you look like a fool IMO. Witty comments and puns make code more fun to read as long as they convey the necessary information. Remember that above all, comments are there to aid the reader in understanding your code and the intentions behind it.

I don't curse in my comments. I don't comment much either, however; it's something I really need to start doing.

>>> Swearing in your comments makes you look like a fool IMO.

Yup.

>>> 90% of my user validation error messages are designed to belittle the person

Nope. If the user enters the wrong information to your prompt, you have failed in your task of preventing such an occurrance. Belittling the user for your failure is poor show. It is your job to make the data entry process work for the "challenged", and make then come away with a sense of acheivment. Running them down will not encourage learning.

Management, different story - We once had a screen which we knew would be seen which said something like...

A position indication record has been attached to a dummy node record. Despite numerous discussions with XYZ, I was assurred this would never happen. His extension number is 3033.

... and if AJC or SJP ever read this, PM me!

Nope. If the user enters the wrong information to your prompt, you have failed in your task of preventing such an occurrance.

Well when you ask for a zip code any they gave you a city name its really not the programmer's fault the user was too dumb to read the prompt. I agree that any professional apps shouldn't belittle anyone but for my personal apps or ones for school its all about having some fun.

i curse a bit in source code when i have to do something the long way (compared to PHP in any case)

>>>
Well when you ask for a zip code any they gave you a city name its really not the programmer's fault the user was too dumb to read the prompt.
<<<

Why? You are an American, you know what a "ZIP" code is. To me, ZIP is a make of barbecue lighting blocks, it is also the thing on the front of my trousers.

I happen to be old enough and worldly wise enough to know that it is also the "post code" in the US, but you assume I know that.

Ask me what my zip code is, and "14 inches" could be a totally accurate answer...

I like to make make allusions to god in my code comments.

Like:
// and on the first day he create int main, and he saw that it was good
int main() { };

etc.
But usualy thats only when I'm coding school programs. When i'm coding stuff thats actauly fun or practical, i tend to comment incredibly sparingly.

Why? You are an American, you know what a "ZIP" code is. To me, ZIP is a make of barbecue lighting blocks, it is also the thing on the front of my trousers.

I happen to be old enough and worldly wise enough to know that it is also the "post code" in the US, but you assume I know that.

Ask me what my zip code is, and "14 inches" could be a totally accurate answer...

Way to go in missing the point. It was an example. My point was that the programmer is not at fault for the user putting in wrong information, only for accepting it as valid.

Since you want to argue the example instead of the point lets try this one:

"Enter an integer between 0 and 10 inclusively (Example: 0, 5, 10): "
and the user enters 13 how is this the programmer's fault?

An example of my response would be something like this:

Since you obviously could not understand my simple instructions let me break it down for you. Type a whole number (a number without a decimal point [.]) and press enter. The number should be between 0 and 10 and may include 0 and 10. Lets see if you can do it right this time: