Witty humor, jokes, memes, and punchlines sorted by emotional damage level from Chaotic Meh — organized so the algorithm can pretend this place has adult supervision.
A friend from West Virginia was shopping at the Wal-Mart in Blacksburg, VA. At the cash register, my friend wrote a check.
The clerk asked for her driver’s license.
She presented her West Virginia driver’s license and the clerk grabbed it away from her and scoffed, “If you’re going to use a fake ID, you could at least use a real state!”
A manager was required to verify West Virginia’s statehood.
A fellow had just been hired as the new CEO of a large high-tech corporation. The CEO who was stepping down met with him privately and presented him with three numbered envelopes. “Open these if you run up against a problem you don’t think you can solve,” he said.
Well, things went along pretty smoothly, but six months later, sales took a downturn and he was really catching a lot of heat. About at his wit’s end, he remembered the envelopes. He went to his drawer and took out the first envelope. The message read, “Blame your predecessor.”
The new CEO called a press conference and tactfully laid the blame at the feet of the previous CEO. Satisfied with his comments, the press and Wall Street responded positively, sales began to pick up and the problem was soon behind him. About a year later, the company was again experiencing a slight dip in sales, combined with serious product problems. Having learned from his previous experience, the CEO quickly opened the second envelope.
The message read, “Reorganize.” This he did, and the company quickly rebounded. After several consecutive profitable quarters, the company once again fell on difficult times.
The CEO went to his office, closed the door and opened the third envelope. The message said, “Prepare three envelopes.”
The San Francisco Zoo has an elephant named Calle who has a chronic illness, requiring medication. The zoo people couldn’t get Calle to take her dose orally, so a California pharmacologist developed a suppository. The ten-inch-long, four-pound, cocoa-butter bullets are crafted by the good folks at Guittard Chocolates in Burlingame.
Administering the daily medication takes five zoo workers, including one person to distract Calle with treats and one person who wears a full-arm glove.
Why am I telling you this? Just think — five people have jobs worse than yours!
This is an actual job application someone submitted for a fast-food establishment:
NAME: Greg Bulmash
DESIRED POSITION: Reclining. Ha ha. But seriously, whatever’s available. If I was in a position to be picky, I wouldn’t be applying here in the first place.
DESIRED SALARY: $185,000 a year plus stock options and a Michael Ovitz-style severance package. If that’s not possible, make an offer and we can haggle.
EDUCATION: Yes.
LAST POSITION HELD: Target for middle-management hostility.
SALARY: Less than I’m worth.
MOST NOTABLE ACHIEVEMENT: My incredible collection of stolen pens and Post-it notes.
REASON FOR LEAVING: It sucked.
HOURS AVAILABLE TO WORK: Any.
PREFERRED HOURS: 1:30–3:30 p.m., Monday, Tuesday, and Thursday.
DO YOU HAVE ANY SPECIAL SKILLS?: Yes, but they’re better suited to a more intimate environment.
MAY WE CONTACT YOUR CURRENT EMPLOYER?: If I had one, would I be here?
DO YOU HAVE ANY PHYSICAL CONDITIONS THAT WOULD PROHIBIT YOU FROM LIFTING UP TO 50 LBS?: Of what?
DO YOU HAVE A CAR?: I think the more appropriate question here would be “Do you have a car that runs?”
HAVE YOU RECEIVED ANY SPECIAL AWARDS OR RECOGNITION?: I may already be a winner of the Publishers Clearing House Sweepstakes.
DO YOU SMOKE?: Only when set on fire.
WHAT WOULD YOU LIKE TO BE DOING IN FIVE YEARS?: Living in Bimini with a fabulously wealthy supermodel who thinks I’m the greatest thing since sliced bread. Actually, I’d like to be doing that now.
DO YOU CERTIFY THAT THE ABOVE IS TRUE AND COMPLETE TO THE BEST OF YOUR KNOWLEDGE?: No, but I dare you to prove otherwise.
SIGN HERE: Scorpio with Libra rising.
During the “rush hour” at Houston’s Hobby Airport, my flight was delayed due to a mechanical problem. Since they needed the gate for another flight, the aircraft was backed away from the gate while the maintenance crew worked on it. We were then told the new gate number, which was some distance away.
Everyone moved to the new gate, only to find that a third gate had been designated for us. After some further shuffling, everyone got on board, and as we were settling in, the flight attendant made the standard announcement: “We apologize for the inconvenience of this last-minute gate change. This flight is going to Washington, D.C. If your destination is not Washington, D.C., then you should ‘deplane’ at this time.”
A very confused-looking and red-faced pilot emerged from the cockpit, carrying his bags. “Sorry,” he said. “Wrong plane.”
A true story.
This is a bricklayer’s accident report that was printed in the newsletter of the English equivalent of the Workers’ Compensation Board. So here, thanks to John Sedgwick, is this bricklayer’s report.
Dear Sir,
I am writing in response to your request for additional information in Block #3 of the accident reporting form. I put “Poor Planning” as the cause of my accident. You asked for a fuller explanation and I trust the following details will be sufficient.
I am a bricklayer by trade. On the day of the accident, I was working alone on the roof of a new six-story building. When I completed my work, I found I had some bricks left over which when weighed later were found to weigh 240 lbs. Rather than carry the bricks down by hand, I decided to lower them in a barrel by using a pulley which was attached to the side of the building at the sixth floor.
Securing the rope at ground level, I went up to the roof, swung the barrel out and loaded the bricks into it. Then I went down and untied the rope, holding it tightly to ensure a slow descent of the 240 lbs of bricks. You will note on the accident reporting form that my weight is 135 lbs.
Due to my surprise at being jerked off the ground so suddenly, I lost my presence of mind and forgot to let go of the rope. Needless to say, I proceeded at a rapid rate up the side of the building. In the vicinity of the third floor, I met the barrel which was now proceeding downward at an equally impressive speed. This explains the fractured skull, minor abrasions and the broken collarbone, as listed in Section 3, accident reporting form.
Slowed only slightly, I continued my rapid ascent, not stopping until the fingers of my right hand were two knuckles deep into the pulley which I mentioned in Paragraph 2 of this correspondence. Fortunately by this time I had regained my presence of mind and was able to hold tightly to the rope, in spite of the excruciating pain I was now beginning to experience.
At approximately the same time, however, the barrel of bricks hit the ground — and the bottom fell out of the barrel. Now devoid of the weight of the bricks, the barrel weighed approximately 50 lbs. I refer you again to my weight.
As you might imagine, I began a rapid descent down the side of the building. In the vicinity of the third floor, I met the barrel coming up. This accounts for the two fractured ankles, broken tooth and severe lacerations of my legs and lower body.
Here my luck began to change slightly. The encounter with the barrel seemed to slow me enough to lessen my injuries when I fell into the pile of bricks and fortunately only three vertebrae were cracked.
I am sorry to report, however, as I lay there on the pile of bricks, in pain, unable to move and watching the empty barrel six stories above me, I again lost my composure and presence of mind and let go of the rope.
1. Rome did not create a great empire by having meetings… they did it by killing all those who opposed them.
2. If you can stay calm while all around you is chaos… then you probably haven’t completely understood the seriousness of the situation.
3. Doing a job RIGHT the first time gets the job done. Doing the job WRONG fourteen times gives you job security.
4. Eagles may soar, but weasels don’t get sucked into jet engines.
5. Artificial Intelligence is no match for Natural Stupidity.
6. A person who smiles in the face of adversity… probably has a scapegoat.
7. Plagiarism saves time.
8. If at first you don’t succeed, try management.
9. Never put off until tomorrow what you can avoid altogether.
10. TEAMWORK… means never having to take all the blame yourself.
11. The beatings will continue until morale improves.
12. Never underestimate the power of very stupid people in large groups.
13. We waste time, so you don’t have to.
14. Hang in there, retirement is only thirty years away!
15. Go the extra mile. It makes your boss look like an incompetent slacker.
16. A snooze button is a poor substitute for no alarm clock at all.
17. When the going gets tough, the tough take a coffee break.
18. INDECISION is the key to FLEXIBILITY.
19. Succeed in spite of management.
20. Aim Low, Reach Your Goals, Avoid Disappointment.
A helicopter was flying around above Seattle yesterday when an electrical malfunction disabled all of the aircraft’s electronic navigation and communications equipment. Due to the clouds and haze, the pilot could not determine the helicopter’s position and course to steer to the airport.
The pilot saw a tall building, flew toward it, circled, drew a hand-written sign, and held it in the helicopter’s window. The pilot’s sign read “WHERE AM I?” in large letters.
People in the tall building quickly responded to the aircraft, drew a large sign, and held it in a building window. Their sign read “YOU ARE IN A HELICOPTER.”
The pilot smiled, waved, looked at his map, determined the course to steer to SEATAC airport, and landed safely.
After they were on the ground, the copilot asked the pilot how the “YOU ARE IN A HELICOPTER” sign helped determine their position.
The pilot responded, “I knew that had to be the Microsoft building because, similar to their help lines, they gave me a technically correct but completely useless answer.”
Tech: “I think I know from where your problems stem. Would you, could you, RTFM?”
User: “I would not, could not RTFM. I want you to solve my problem.”
Tech: “Could you read the docs online? Would you read them any time?”
User: “I would not read the docs online. Without them I can do just fine.”
Tech: “Would you read a FAQ or HOWTO? Is this something you could do?”
User: “I could not read a FAQ or HOWTO. Even the thought makes me spew.”
Tech: “What could I suggest next? Would you read it in hypertext?”
User: “I would not read help in hypertext, for the problem with which I am vexed.”
Tech: “How about if you could read it through a conveniently placed system menu?”
User: “I will not access help from a menu. That stuff is a bunch of ballyhoo!”
Tech: “How much simpler could this be? Did you try the help hotkey?”
User: “I’ll try not a help hotkey, to that I will never agree!”
User: “I would not, could not RTFM. I want you to solve my problem!”
Tech: “Since you will not RTFM, you I must now condemn”
Tech: “To a life without working software, and a constant feeling of despair.”
Tech: “You should read a book by Dr. Seuss, or maybe something by Mother Goose.”
Q: How many Windows programmers does it take to change a light bulb?
A: Four hundred and seventy-two: One to write WinGetLightBulbHandle, one to write WinQueryStatusLightBulb, one to write WinGetLightSwitchHandle…
Q: How many technical support personnel does it take to change a light bulb?
A: We have an exact copy of the light bulb here, and it seems to be working fine. Can you tell me what kind of system you have? OK. Now, exactly how dark is it? OK. There could be four or five things wrong… Have you tried the light switch?
Q: How many managers does it take to change a light bulb?
A: We’ve formed a task force to study the problem of why light bulbs burn out, and to figure out what, exactly, we as supervisors can do to make the bulbs work smarter, not harder.
Q: How many beta testers does it take to change a light bulb?
A: We just notice that the room is dark; we don’t actually fix the problem.
Q: How many Microsoft technicians does it take to change a light bulb?
A: Three. Two to hold the ladder and one to screw the bulb into the faucet.
Q: How many MIS guys does it take to change a light bulb?
A: MIS has received your request concerning your hardware problem and has assigned you request service number 39,712. Please use this number for any future reference to this light bulb issue.
Q: How many C++ programmers does it take to change a light bulb?
A: You’re still thinking procedurally. A properly designed light bulb object would inherit a change method from a generic light bulb class, so all you’d have to do is send a light-bulb-change message.
Q: How many developers does it take to change a light bulb?
A: The light bulb works fine in my office.
Q: How many shipping department guys does it take to change a light bulb?
A: We can change the light bulb in seven to ten working days, but if you call before 2 p.m. and pay an extra $15, we can get the light bulb changed overnight.
Q: How many Microsoft engineers does it take to change a light bulb?
A: None. Bill Gates will just redefine Darkness™ as the new industry standard.
Q: How many service technicians does it take to change a light bulb?
A: Just one, and he does it very well, but there is that $85.00 non-refundable on-site service fee to consider…
Q: How many quality assurance techs does it take to change a light bulb?
A: Two, and you’ll need a forty-eight-hour burn-in, two hours of cool down, and a very thorough bench analysis of the new bulb, so don’t expect to see either bulb for a week or so.
Q: How many receptionists does it take to change a light bulb?
A: Zero — well, actually one: the one who told the office manager about the light bulb problem in the first place.
Q: How many software engineers does it take to change a light bulb?
A: None. That’s a hardware problem.
