|
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
|
|
|
|
|
As a general rule of thumb I refrain from vulgarity in my written words and limit there usage in my verbal vocabulary as well. However; I do put creative slandering text in comments referencing some quest and the struggle to accomplish what is being looked it. I see it as a way of in the distant future someone may pose the question "Why" so the comment tells why and creatively express that it wasn't easily obtained.
|
|
|
|
|
I see it as very unprofessional. Come to think of it...I have never thought about cussing in my coding
|
|
|
|
|
Henco Eloff wrote: I see it as very unprofessional.
I may have a silly comment depending on my mood but I would never ever cuss anywhere in my code, comments or anything else I write for work. At least I have not done so in my first million lines of C++ code I have written for my job.
John
|
|
|
|
|
I could not agree with you more. I never knew that people actually did that. I haven't been coding as long as you might have as I am only studying at the moment, but I have never even thought about cussing in Coding.
Thanks for the reply John
Henco Eloff
|
|
|
|
|
But you can write some joke. And that one, who will read your code, can laough.
|
|
|
|
|
As part of my studies, I am currently doing an Internship, and we were discussing the same thing. If you examine some websites' HTML Coding, you find various jokes being made. But i personally feel that if your code will be read by someone in a higher position than you, you should stay as professional as possible.
Henco Eloff
|
|
|
|
|
Yes, it's reverse side of medal. It's really bad, when you wrote some code as outsourcer and your customer in other country read youtr jokes
|
|
|
|
|
And more.
To stay as professional as possible you should write good, easy extensible and scalabel code at first. Presence or absence of jokes is not so important.
|
|
|
|
|
Nickos_me wrote: Presence or absence of jokes is not so important.
But can scratch the company's reputation when read by the client (seen that) and is unprofessional, the client is not paying for jokes.
|
|
|
|
|
If you angry because of the code you writing, then go make yourself a brake
No more Mister Nice Guy... >: |
|
|
|
|
|
You do not have to be angry, sometimes you are trying to make a point. I once wrote the following about some of my code: "Warning, the following code isn't just ugly, it's damn ugly."
|
|
|
|