|
|
It is safe to use profanity in a variable name, as long as it won’t ever be seen by someone who would find it objectionable. However, it is never safe to put any questionable content into a display string. Even though you have every intention of deleting the bad words, they can still make it into production.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
I use WTF functions all the time in debugging...
WTF = WriteToFile(...)
I get a kick out of it when someone sees it
but it is a valid acronym
|
|
|
|
|
I'm a bit found of naming my double's d.
|
|
|
|
|
The worst I have ever done is when coming across the following comment.
I added the following after it:
Unfortunately they asked me to remove both comments during the code review
He who asks a question is a fool for five minutes. He who does not ask a question remains a fool forever. [Chineese Proverb]
Jonathan C Dickinson (C# Software Engineer)
|
|
|
|
|
Probably it had to deal with legacy undocumented code...
|
|
|
|
|
Although I have mentioned it before in another posting, I have seen the word "FUKU" used as a protocol identifier.
|
|
|
|
|
Well, maybe not profane, but likely hilarious.
After the third or fourth time fighting the build system, I submitted this labeling comment: "This is as much fun as eating a poopy flavored lollipop."
I need a 32 bit unsigned value just to hold the number of coding WTF I see in a day …
|
|
|
|
|
I have to keep that in mind :
poopy flavored lollipop...
you made my day
edit: thinking about other possible results of fighting the build system:
monitor-bashing
keyboard-torment (flying keys in the room)
forehead-torment (head wallbashing)
...

|
|
|
|
|
Damn IDE auto-correcting spell checker! Get one letter wrong and a word and you never know what you'll end up with! 
|
|
|
|
|
May be it's a symbolic representation of how his manager treated him for skipping the deadline. 
|
|
|
|
|
Not quite profanity but ...
Many, many years ago in a far off galaxy ... I had the displeasure of having to work with a code pre-processor that had some irritating "features".
As an expedient solution to some of those features, I inserted a blank line at the top of a key header file to prevent all sorts of errors. Certain colleagues insisted on "tidying up" this blank line, meaning that errors kept coming back ...
My solution: I inserted a comment below that blank line "If you delete the blank line above I will find you, where ever you are, and break your fingers one by one".
It clearly worked. I even got a phone call several years later (having moved on) asking if it was one of my comments ... and did it still stand!
|
|
|
|
|
I have on occaision used a variable called "Count", but as I was typing - missed out the e "o". Oops.
Usually managed to correct it before commiting the change.
____-=< |>@\/ø!c| >=-____
`````````_`````_`````````
```````o/ \^w^/ \o```````
``````````(o o)``````````
------ooO--(_)--Ooo------
I'm not a complete idiot;
bits of me are missing.
-><-
|
|
|
|
|
Years ago, maybe in the 1980s, at a previous company, we had a problem that manifest itself when the user got impatient and rebooted their computer during a long "Pack" operation (it was kind of an ISAM file). While waiting for the next release to fix the problem, I put out an emergency patch that displayed a distinctive cursor during the pack, so that users could be informed their computer wasn't hung (no pun intended). The cursor looked something like:
PA I CK
really a bit more like an hourglass with PACK written around it. As it happened, most packing operations were very quick and took only 1/10th of a second or so. So this insurance company client of ours had all these sweet little old ladies working there who would get these subliminal flashes of what they took to be a really dirty word - mistaking the "A" rendered in a boxy way with very few pixels for an "R". A defect was submitted saying that our product flashed dirty words at our users and that they were very very upset. The patch was pulled immediately.
|
|
|
|
|
I wonder what downtimes refers to in this context ...
|
|
|
|
|
I once made the misstake of spelling "Sauce" instead of "Source".
I did this in a company library and our entire software was littered with "Sauce", until a bright colleague finally pointed out the spelling mistake.
We had a good laugh about it
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}
|
|
|
|
|
I see a lot of silly spelling mistakes in a number of libraries, including several DevExpress libraries (Most of those mistakes have been fixed, however).
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image.
Stephen Hawking
|
|
|
|
|
As recently as yesterday, a colleague sent me an email that was supposed to include the word "assign". However, she transposed the last two letters 
|
|
|
|
|
In a MySQL table, the start and en time of using a service are recorded. I tried to get the sum of usage per user and day:
SELECT OriginationName, Date(StartTime), count(*), sum(timediff(endtime,starttime)) as duration
FROM ippbxcdr
Group by OriginationName, Date(StartTime)
order by OriginationName, Date(StartTime)
With a start time of '2012-08-21 15:02:29' and an end time of '2012-08-21 15:03:59' , that duration of 1 minute 30 seconds was shown as 130.0000 .
No, no, no: thou shalt not use sum with timediff !
The Lord of MySQL giveth no error message, he punisheth with a wrong result.
|
|
|
|
|
|
Ooouch!!! 
|
|
|
|
|
|
¿ Are you sure you haven't multiple records with the same values ?
When you have 100 records with these values......you'll have this result.
|
|
|
|
|
Your punishment is accord to your sins, long live to our migthy and fair MySQL Lord!
|
|
|
|
|
I have renamed your thread appropriately!
|
|
|
|