Seen in some source code...

"If we reach here then the ladies bits are pointing skyward"

I guess we all have done this and that I am not an outlier? Please? Or maybe at least 90% of commentards?

Not in any project that others would see, thank the maker. I do have some expletives in my source code, but milder forms. Plus some court has actually declared that swearing in dialect is not deemed (too) offensive.

Never did it - I got past finding offensive words "funny" before ten, I guess. Probably because I was exposed to good humor that doesn't need them.

Writing software for me was and is also a show of skills and elegance - not a show of how much childish I could be. But maybe I'm the outlier.

Tosser

I was going to suggest "twat", but I bow to your lead-off opinion.

I outgrew potty humor as well.

Given the amount of downvotes you already have, yeah, we're outliers.

Obviously never worked in a high-pressure job that used hospital humo(u)r as a pressure relief valve.

Lucky you.

It does not mean that the stress relief becomes part of the code base (or anything else that will outlive the current state of affairs),

Sorry, can't think of anything funny to say :-(.

"It does not mean that the stress relief becomes part of the code base"

Except it does. Or rather, from my perspective it sure seems to. I've seen it in every single large coding project I've ever worked on.

"(or anything else that will outlive the current state of affairs),"

And again, but it does. A single word or phrase uttered at the (in)appropriate moment will often send the aware listener(s) into gales of (sometimes stifled) laughter. The more solemn the moment, the more pronounced the effect. I once watched two members of a C-suite almost lose it completely as the Boss was reading carefully worded excerpts from the annual report ...

If Brad is still writing code, and now understands logical operations, I bet he's implemented base36 just to give himself some more options and/or a better possible vocabulary..

I run source code through something that checks for swearwords, licence keys etc before it's published...basically if I or a team member have made that mistake before, it's trapped here. The added benefit is that it keeps you up to date with current foul language:-)

Hint: Do not tell the junior team members about Roger's Profanisaurus, unless you like playing sweary whack-a-mole!

"I run source code through something that checks for swearwords"

I can assure you that the English language is quite flexible enough to get objectionable phrases past any rules that they choose to implement. That kind of filtering is worse than useless in that it takes time to implement, doesn't work, provides a false sense of security, and opens the company up to lawsuit should an employee accidentally see something that they think was missed by the filters.

Student: "You wont find a single word in my paper that one couldn't say on Radio 4!"

Master: "Yeah, but not in that particular order ..."

A slight aside...

Colleague at a job a long time ago received a mistakenly addressed email from one brother to another, expressing in colourful terms the older brother's dismay at finding out his sibling had come out as gay.

When he replied, to let the sender know the missive hadn't reached its intended recipient, their firm's email filter rejected it due to the level of profanity contained, none of which my colleague had added to...

Looping through ***** is standard operating procedure for most companies. Glad to hear of someone clearly labelling it

From what I remember of the 9-5 grind, it was more loping through *****.

Yeah, just take a look at [1]https://thedailywtf.com/ for inspiration.

The appropriate words will pop into your mind. It is just that most never reach the vocal chord system or other's auditory system.

[1] https://thedailywtf.com/

Some very-many years ago, when IBM used to release the source code of their various operating systems on microfiche, a customer hailing from the mid-West of the US (yes, yee-haw...) had complained to "IBM Management" that one comment in a 360-Assembler comms code module read:

"Retry 10000 times, for the hell of it".

The hapless originating IBM programmer was required to change the comment, so that next time round the source code line bore the revised text:

"Retry 10000 times" ...

It should have read : "Retry 10000 times and let us not irritate the poor little Mid-West yokels by saying why"

One wonders what the mid-west yokel thought of the word EBCDIC ...

something like this?

for (f@ck = 1; f@ck < 11; ++f@ck)

{

printf("%d ", f@ck);

}

return 0;

I pity the poor sod who have to fix such code... especially if the end result of f@ck is used somewhere else too...

So does ++f@ck count as an in-built f@ck-up all by itself?

A common window title in our department was "X blows goats" or similar. There were also conditionals or loop endings of the style "fat_lady = has_sung".

I don't see how a reference to the opera is a bad thing.

We all know that it ain't over 'til the fat lady has sung. It's tradition.

You obviously haven't met the head of Personnel HR ...

And i'm not the only one ...

There is some sense of relief when trying to debug someone else's code and come across a comment of

// FFS

or code that has been written by team A, then handed over to team B and has comments along the lines of

// who in their right mind thought this was a good idea

#ifdef BURN_IT_WITH_FIRE

[.. lots of code ]

#endif

And I've seen similar comments around my own code, that was coded up ever so clever and making use of arcane template knowledge that meant my code was awesome, extremely succint, nicely formatted and impossible to modify without basically having to rewrite it from scratch

And I've seen similar comments around my own code, that was coded up ever so clever and making use of arcane template knowledge that meant my code was awesome, extremely succint, nicely formatted and impossible to modify without basically having to rewrite it from scratch

You wrote it in Perl?

A long time ago while at university writing a program in a functional programming language with an interpreter that was slightly less robust then a tissue paper ocean liner I had to insert a comment line with the text (translated) "If this comment line is removed the fing interpreter throws a fit and crashes!"...

I worked on a development whose customer was UK MoD. It was embedded code, so was never expected see the light of day. The contract allowed the customer the option of a code review as part of sign off. The MoD QA bloke, let's call him "Mike", was a pain in the arse* and, naturally, insisted on doing the code eview. There were many comments in the code along the lines of "..another error trap for a condition that can only happen in Mike's head...". No four-letter words or direct insults but he was very (and quite rightly, in hindsight) miffed by them and we missed delivery and incurred extra costs because of the work to take the comments out and repeat testing and, of course, code review.

*He also insisted on a formal test to prove that the keyboard worked - every individual key, every allowable key combination plus hours' worth of random multiple key-presses all tested, witnessed and recorded. It took two days, plus the time to write the test procedure and report.