|
LOL It had been some time since I checked this forum and when I saw the title of this post I thought there would be tons of Rebbeca Black references (I'm writing this as of FRIDAY, September 7th)
|
|
|
|
|
Definitely WTF worthy.
You have my sympathies.
|
|
|
|
|
So I think the guy before me wanted to spell the word 'Assigned' in his C# method name but ended up saying
public int UpdateReasonNotAssgiggedFlag(IEnumerable<DownTime> downtimes)
{
}
Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours,
Brian Hart
|
|
|
|
|
Sounds like a reporting method for use in a prison web service.
If (DropSoap && !A##Gi##ed){
Update....
}
(please accept my appologies too - Just couldn't resist).
|
|
|
|
|
So that's why they call it the "soapbox"...
|
|
|
|
|
Quote: A##Gi##ed
Is that a valid identifier?
|
|
|
|
|
In C#: if you put an @ in front of it, MAYBE.
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)
|
|
|
|
|
No. Its not an identifier in C#. # is used as a directive.
There is no great genius without some touch of madness - Seneca, Epistles
|
|
|
|
|
I didn't even see it the first time. If you hadn't metioned I might not have noticed.
However, now that I do, it is quite funny!
|
|
|
|
|
Its amazing how the human brain fills in what we think it should be when reading - I missed it the first time also.
|
|
|
|
|
I've never cursed in my executable code, but I have in comments a number of times.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: I've never cursed in my executable code, but I have in comments a number of times. Which is another good reason not to write comments.
|
|
|
|
|
In the cases I recall, my cursing was an accurate technical description of the situation I was addressing. The point of a comment is to describe what your code cannot. If my code has to do something that looks unnecessary or stupid because someone else is an idiot, you bet damn Skippy I'm going to document it. If my language in the comment is a little 'colorful', it's because the circumstances were so outrageous it was warranted.
Software Zen: delete this;
|
|
|
|
|
A few years ago I was so upset because of a problem that my variable declaration was
string fick = "dich";
which is german for
string f*** = "you";
unfortunately I forgot to change that back before checking in... o_O
thank goodness my department chief had a lot of humor; there were no further consequencies...
Lessons learned:
Curse loud, not in source!
|
|
|
|
|
When I first started working with WPF and C# a few years back. I was trying to get some piece of code to work and I ended up writing something along the lines of just f*****g work already. I also ended up checking it into the repo. When my supervisor saw it, he laughed and said that he's done that a few times when he can't get something to work. Of course, by the time he saw the comments, I already had the code working.
|
|
|
|
|
Gary Wheeler wrote: The point of a comment is to describe what your code cannot. Agree, that's IMO the only justifiable cause for a comment.
However, IME, such situations are rare, and can almost always be avoided by rephrasing your code.
|
|
|
|
|
Hmm. My environment is process control (we make commercial ink-jet printing systems), where we manage a lot of diverse hardware. The API's we use often bear little resemblance to the actions taken by the machine. Hence, we document. We document a lot.
Software Zen: delete this;
|
|
|
|
|
The trailblazing operating system MCP was approx 250k lines of Espol, a high-level language based on Algol with extra instructions like Halt and Heyu. Multi-processor, virtual memory, open source - this was around 40 years ago! Anyway, it had a process creation function called motherforker(); when executives realised the meaning of open source it was renamed to anabolism().
--
Richard Ross-Langley
|
|
|
|
|
Software Zen: delete this;
|
|
|
|
|
|
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...
|
|
|
|