Skip to content

Out on a LIMSThe Blog for People Who Risk Life and LIMS on a Daily Basis

Some Levity For the Programmers Out There

Volume IIEntry 86 of 113 in 20161 min read2 comments ↓

Written by Gloria Metrick on . Published as written. It may not reflect how these systems work today.

Now that most projects are rolling along post-summer holidays, people seem slammed with work. Programmers are typing their fingers off and I just thought sharing a bit of fun would help lighten the mood a bit.

Normally, I try to keep things a bit more serious but I think right about now most of us could use a bit of a chuckle so I would like to pass along a list of jokes that I think are totally hysterical!

First, suppose that Chuck Norris is not just martial arts expert but also an expert programmer. Here's one tidbit you might appreciate about him: "Chuck Norris can write infinite recursion functions…and have them return."

If you don't find that as hysterical as I do then don't bother reading the rest at http://codesqueeze.com/the-ultimate-top-25-chuck-norris-the-programmer-jokes/ .  ;-)

Gloria Metrick
GeoMetrick Enterprises
http://www.GeoMetrick.com/

The conversation

2 comments from 1 person on September 21, 2016. Gloria replied once.

  1. Brian

    The Chuck Norris one leaves me cold, I'm afraid, but if you want some humo(u)r I'll dig this one out of the archives in case anybody hasn't seen it before - it's only three months or so until Xmas after all...

    >The 12 "Bugs" of Christmas
    >
    >At the first bug of Christmas, my tech lead said to me: See if they can do
    >it again.
    >
    >At the second bug of Christmas, my tech lead said to me: Ask them how they
    >did it ... and See if they can do it again.
    >
    >At the third bug of Christmas, my tech lead said to me: Try to reproduce
    >it; Ask them how they did it ... and See if they can do it again.
    >
    >At the fourth bug of Christmas, my tech lead said to me: Run with the
    >debugger; Try to reproduce it; Ask them how they did it ... and See if
    >they can do it again.
    >
    >At the fifth bug of Christmas, my tech lead said to me: *** ASK FOR A
    >DUMP ***; Run with the debugger; Try to reproduce it; Ask them how they did
    >it ... and See if they can do it again.
    >
    >At the sixth bug of Christmas, my tech lead said to me: Reinstall the
    >software; *** ASK FOR A DUMP ***; Run with the debugger; Try to reproduce
    >it; Ask them how they did it ... and See if they can do it again.
    >
    >At the seventh bug of Christmas, my tech lead said to me: Say they need an
    >upgrade; Reinstall the software; *** ASK FOR A DUMP ***; Run with the
    >debugger; Try to reproduce it; Ask them how they did it ... and; See if
    >they can do it again.
    >
    >At the eighth bug of Christmas, my tech lead said to me: Find a way
    >around it; Say they need an upgrade; Reinstall the software; *** ASK FOR A
    >DUMP ***; Run with the debugger; Try to reproduce it; Ask them how they did
    >it ... and See if they can do it again.
    >
    >At the ninth bug of Christmas, my tech lead said to me: Blame it on the
    >hardware; Find a way around it; Say they need an upgrade; Reinstall the
    >software; *** ASK FOR A DUMP ***; Run with the debugger; Try to reproduce it;
    >Ask them how they did it ... and See if they can do it again.
    >
    >At the tenth bug of Christmas, my tech lead said to me: Change the
    >documentation; Blame it on the hardware; Find a way around it; Say they
    >need an upgrade; Reinstall the software; *** ASK FOR A DUMP ***; Run with
    >the debugger; Try to reproduce it; Ask them how they did it ... and See if
    >they can do it again.
    >
    >At the eleventh bug of Christmas, my tech lead said to me: Say it's not
    >supported; Change the documentation; Blame it on the hardware; Find a way
    >around it; Say they need an upgrade; Reinstall the software; *** ASK FOR A
    >DUMP ***; Run with the debugger; Try to reproduce it; Ask them how they did
    >it ... and See if they can do it again.
    >
    >At the twelfth bug of Christmas, my tech lead said to me: Tell them it's a
    >feature; Say it's not supported; Change the documentation; Blame it on the
    >hardware; Find a way around it; Say they need an upgrade; Reinstall the
    >software; *** ASK FOR A DUMP ***; Run with the debugger; Try to reproduce
    >it;
    >Ask them how they did it ... and See if they can do it again.

  2. Gloria MetrickAuthor

    Here's one related to Brian's:

    A manager, a programmer, and an engineer were riding in a car down an incline, one day, when the brakes fail. By pulling the car into the grassy side of the road and carefully using the parking brake, they were able to safely stop the car. They all got out.

    The manager said, "Let's put together a committee and study the problem."

    The engineer said, "No, if you've got a paper clip, I'll just fix it, right now."

    The programmer, studies the car some more and finally says, "Hey, let's push the car back up the hill, get back into it, and see if it does the same thing, again."

Comments are closed. This conversation is from 2016. Ask us to remove a comment

Working on the same problem in your lab?

Talk to a laboratory informatics scientist