|
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."
|
|
|
|
|
damn? It's not swearing IMHO.
No more Mister Nice Guy... >: |
|
|
|
|
|
Because it can happen to me to be sarcastic about some legacy code or an API :P
modified 6-Apr-21 21:01pm.
|
|
|
|
|
Made the status/heartbeat LED pulse a pointed nasty message in morse at high speed. xored content so didn't show in code review. Was nice to know it was there on country wide terminals.
|
|
|
|
|
Having fixed a very complex bit of SQL report code for the 2nd time after a new dev rafactored it to broken I left a particularly pithy offer to dismember any stupid bastard who ever touched the code again. It already had about 100 lines of comment scattered throughout the stored proc.
And yes it got into production and is still there AFAIK.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Not explicitly, Sometimes PG versions like dang or darn in internal test only code.
Save the good stuff for the review where their impact can be directed at the guilty party or parties.
It was broke, so I fixed it.
|
|
|
|
|
|
Dan McKinley wrote:</div>He [Richard] had recently been fired for repeatedly showing up in the early to mid-afternoon drunk and coked out of his mind (I guess nobody told him that we real programmers show up on time and drink at our desks).
Panic, Chaos, Destruction. My work here is done.
Drink. Get drunk. Fall over - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre
I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer
Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
|
|
|
|
|
Consolas font so it is much more soft...
|
|
|
|