Profanity in code
-
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; -
I've never cursed in my executable code, but I have in comments a number of times.
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
-
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
:laugh:
Software Zen:
delete this; -
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
Not even a
wtfvariable?Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
Probably it had to deal with legacy undocumented code... :)
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
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.
-
Gary Wheeler wrote:
I've never cursed in my executable code
Not even a
wtfvariable?Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
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. :sigh:
Just because the code works, it doesn't mean that it is good code.
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
Although I have mentioned it before in another posting, I have seen the word "FUKU" used as a protocol identifier.
-
Gary Wheeler wrote:
I've never cursed in my executable code
Not even a
wtfvariable?Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
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
Sure sure.. thats what you claimed after your file writing abstraction finally was working and went straight to production ;)
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
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 …
-
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 …
:laugh: I have to keep that in mind : poopy flavored lollipop... :java: 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) ... :wtf:
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
-
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! :-D
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:
I've never cursed in my executable code
Not even a
wtfvariable?Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
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)
-
I've never cursed in my executable code, but I have in comments a number of times.
Software Zen:
delete this;The worst I have ever done is when coming across the following comment.
// TODO: Fix this code up. Fred is an **(*!^$, )(!*@# this )(*!#. Fix this up so that it isn't )!*@#! anymore.
I added the following after it:
// TODO: Buy the above developer a beer.
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)
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
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!
-
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 downtimes)
{
// ...
}Excuse the profanity, but I wonder what it feels like to get "ass-gigged." Anyway, I corrected the "misspelling..."
Sincerely Yours, Brian Hart
I have on occaision used a variable called "Count", but as I was typing - missed out the e "o". Oops. :-O 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.
-><-
