|
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.
-irresponsibility@Despair.com
|
|
|
|
|
Actually - those who reply "no" are the ones who do not comment their code
Graham
Librarians rule, Ook!
|
|
|
|
|
I did name a project Legacy Application Monitor Environment (LAME). My manager thought that was amusing.
m.bergman
-- For Bruce Schneier, quanta only have one state : afraid.
|
|
|
|
|
It does happen in professional projects:
LAME[^]
The first rule of CListCtrl is you do not talk about CListCtrl - kornman
|
|
|
|
|
Yes, this is a joke name, too, in the tradition of GNU.
I wrote mine a little less than a year before this came out.
m.bergman
-- For Bruce Schneier, quanta only have one state : afraid.
|
|
|
|
|
We managed to call our system for managing customer contacts SCAM.
Every man can tell how many goats or sheep he possesses, but not how many friends.
|
|
|
|
|
When I worked at a Utah printing company, I left behind a whole language called GayML.
|
|
|
|
|
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 
It's an OO world.
|
|
|
|
|
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.
|
|
|
|
|
Back when I was starting out:
// Holy sh*t! it works!
In someone else's code that I was reviewing:
// Turn off beep because it sh*ts Dave when playing MP3's
I have no blog...
|
|
|
|
|
I do taunt myself for not seeing what fixed it and insult myself too.
Just for fun. But no foul language.
|
|
|
|
|
I do it some of the times,but will remove it when the code review happens
|
|
|
|
|
it can be quite distractive also makes you uncomfortable thinking other people who might be offended are going to read your code!
|
|
|
|
|
|
Hey we all in this group have done it...more than once. Usually the simplest of things that make you cuss at that square screen in front of you!
Henco Eloff
|
|
|
|
|
Tell me about it!
My poor monitors have heard do much...
And not only while coding, but while gaming, and its never their fault
|
|
|
|
|
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  
Steve
_________________
I C(++) therefore I am
|
|
|
|
|
The most profane comment I ever used was
And that was only after extreme provocation.
Anything worse would simply be unprofessional.
Henry Minute
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.
|
|
|
|
|
Yes, but we still have to deal with clients, and they who pay our wages can easily seek someone else who fits in with their view of professional.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
...like, "Refactor, because this sux!"
Another one we had was a stored procedure that's been in use for 5 years. The header comments read:
12/06 this sux
10/09 still sux
5/11 I've just accepted it sux and will stay that way
|
|
|
|
|
I think that is still acceptable, but if your client is going to be looking at your coding, and actually understands what he/she is reading, it is frowned upon. But between Coders it is acceptable.
Henco Eloff
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
