I think we needed an Option 3 for those who simply don't comment.
Really, can you say you've really invested due diligence in programming if you don't contribute some profane discourse for future encounters? I believe this is indeed a needed form of warning not to f!*$ with code that took unknown hours of blood, sweat and unlicensed narcotics to completed.
No single raindrop believes it is to blame for the flood.
We almost called a project MOF... Our company name starts with an M Office Framework. Quite amusing seeing how the Dutch called the Germans 'moffen' (single, mof) during WWII. At least LAME and SCAM are politically correct
I had a project for a regional police force called LOLOLO and my ex-PM nearly got Computerized Line Integrated Test Or Repair Information System through - his boss was just about to sign the order for project ties when he spotted the acronym, apparently.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
I think it's an important information for the maintainer in which modd the code was written. Otherwise, there could be misunderstandings about the structure and naming convention used, e.g. a variable like f***YOu could be misinterpreted as float unsigned complex key to a Y combinator Orphanage, measured in microns, and this misunderstanding could lead to bugs.
My initials make it into a screen / display somewhere in most of my projects (Easter Egg)... In one system, if three different error conditions occured at the same time, the error screen would display my initials (eash letter indicating an error condition). On the last project, the command to test LED segments in an onboard display was my initials
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
I usually berate the coder (Me!) in the comments or a popup in a code branch that should never be reached.
I'm the sole developer on my team and write tools and automation utilities, so I'm the only one who ever sees the source code. We're a bunch of jokers so if the impossible happens and one of those messages does manage to pop up (it's only ever happened once!) noone gets pissed off. In fact, it shows a weakness that the wolves I work with can use to give me about a years worth of ribbing.
Early in my career, I've been burned by test data that should never have been seen by others but as been made public -inside the company, thank God- through a chain of random events and an until then undiscovered bug in our software.
Lesson learned, never again.
I was HollyHooo but got tired of it and Sebastien was taken.
I understand the comments about sounding professional, but each profession decides what is considered professional and what is not. IT people are known to be a little more funny than the other departments, and I think that's ok.