Do you leave jokes in your code? If so, please share!

Oftentimes, my code is the joke 🤷‍♂️

I tend to shorten button to butt, which seems clear enough, isn't overly offensive, but makes me chuckle just because I'm writing butt.

And even still I kind of regret not just writing button for clarity. 🙃

At one client, they were using a home-grown issue tracking system called Bob, after Bob the Builder. It even had an image of Bob the Builder in the application itself.

As a little joke, I built in a timer that at random times replaced the image of Bob with one where one eye was closed, wich made it look like he was blinking every now and then. It took a week and a half before someone noticed. I had a hard time not to laugh and to keep my face straight, while asking: "what do you mean, Bob is blinking? Are you serious?"

I also love the little gems hidden in the Android codebase

• Log.wtf()
• isUserAMonkey()
• isUserAGoat()

Our software which we use in the office, I leave a code like this:

const err = {
    count: 0
}

const btn = document.querySelector(".js-btn-remove")

btn.addEventListener("click", () => {
    if(err.count == 5) {
                // omg, you can't be serious. you're still trying...
        myFancyMessage({
                   title: 'Leave me alone...',
                   text: [
                      'unhappy',
                      `Don't do this again. You almost kill me. This hurts me.`,
                   ]
                })
        return false;
    }

         myFancyMessage('Warning', 'You are not authorized to remove sales.')        

    // some important codes
    err.count++

})

I never did in products that I've worked, but where I work currently there are internal systems that when it's blocked for maintenance shows the Travolta confused :D And it makes me LOL...

In the test case:

class OpportunityConnectionMessagesTestCase(APITestCase):

    def setUp(self):
        ...
        self.message_text = 'Last time I cried was when I was cutting Onion. Onion was a good dog.'

I once copied code of my colleague Mark, including the Created by Mark comment. To fix this, I git-pushed:

I tried to frame Mark for a crime he didn't... commit.

I got fed up with badly written assignments in my last semester of college and left some comments criticizing the requirements 😛

I recently used this code comment.

//////////////
// Nonsense //
//////////////
//
//   <reason why I had to do nonsense>

To clarify, I leave this in the code. The code had to be written to dull a weird edge of a library. It was odd in comparison to the rest, so I needed to explain. It is hoped that one day the weird edge will go away and I can remove the code.

I quite often use movie, and other pop culture, references. For example, in development and test mode pages include a Pi symbol in the lower left corner which shows some debug information when you click on it.

There have been cases where the final error message was PC Load Letter, if no better error message was available.

Or when resizing an array the comment // We're going to need a bigger boat is very suitable.

For an internal CA I used the department name Setec Astronomy.

Our CTO once put a client into maintenance mode accidentally. When that happens, the client can't log into their account or anything. He panicked and started blowing up Slack asking about how to reverse it. Since then we have a confirm dialog on that button that says

Are you sure you want to enable maintenance mode for this client, Ed?

That was added over a year ago. What is better is that a newer dev recently saw it and assumed we had incorrectly identified the user. He was quite amused when we told him, nope, that was on purpose. 😂

One of our developers, Scott, was well-known at MousePaw Media for possessing a lethally dry wit. I made the mistake of asking once for a "yay or nay" on something, and from then ever afterwards, he'd respond to yes/no questions with "yay" or "nay". It caught on at the company, even prompting a pair of yay-nay T-shirts to be made for our holiday gift exchange.

When we wrote IOChannel, a featureful wrapper around C++'s std::iostream, we offered a few formatting flags for printing boolean variables. Among those is the undocumented bool_scott...

bool foo = true;
ioc << bool_scott << foo << io_end;

...which would output...

Yay

Meanwhile, the official (still unpublished) specification for our upcoming language contains these little gems...

ERROR 22: Paradox. Something impossible happened.
ERROR 22: Paradox. Computer will now self-destruct.

Error 22 is actually useful for "can't happen" scenarios. There will be some way get it to print out the second message instead, though.

ERROR 42: Unknown question.

If a user hadn't used the new feature the UI needed to display a "new" icon next to it's menu link. so...

  let thaySeentIt;

  function init() {
    thaySeentIt = checkNewFeatureFlag();