maindrop-00113 lines mergedscoreboardmade to order · ships in about a week
vibetokens

54 jokes · one-liners · all original

Programming Jokes and One-Liners

The best programming jokes are one-liners about the parts of the job nobody puts in the job description: estimates, naming things, deploys and the meeting that could have been a pull request. These 54 are original, sorted by topic, and short enough to paste into Slack.

You will not find the usual ones here. Nothing about binary, light bulbs or a bar that a query walks into. Every line below was written for this page, in the same voice as the shirts: dry, specific, and about something that happened at work this week.

If you want the longer versions, there are whole pages on code review comments, git commit messages and it works on my machine.

01 Planning · 9 jokes

Estimates and deadlines

Every estimate is a prediction made by the person with the least information they will ever have about the task. These jokes are about what happens next, usually on a Thursday.

  1. 01The estimate was two days. It was two days, eleven times.
  2. 02Story points are a unit of time that everyone agrees is not a unit of time, measured in days.
  3. 03Quick question. (Forty-minute question.)
  4. 04Should be a one-line change. It is a one-line change in seven files, plus a migration.
  5. 05The deadline is not moving. The scope is moving, quietly, at night.
  6. 06Status: on track. The track was redrawn on Tuesday to go around the problem.
  7. 07I will have it done by end of day. I did not say which day, or which time zone.
  8. 08We committed to 40 points this sprint. We had 20 points of people.
  9. 09Every estimate is correct for a version of me who never gets interrupted.
Mug · made to orderONE LAST COMMIT MugFor the developer who says one last commit at 5:52 PM and means it every time.$30 →

02 Debugging · 9 jokes

Debugging, mostly by staring

Debugging is the part of programming where you find out what the code actually does, as opposed to what you told it to do. The two are rarely on speaking terms.

  1. 10Three hours on the bug. It was a missing comma, in a different file, which is the only thing I will say in my defense.
  2. 11The error message says “something went wrong.” I wrote that error message. I regret my lack of detail.
  3. 12Explained the bug out loud to a rubber duck. The duck asked me to file a ticket.
  4. 13The stack trace is 400 lines long and the only line from our code says index.js.
  5. 14Fixed it by turning it off and on again. Wrote it up as “resolved by restart” so it sounds like engineering.
  6. 15Set a breakpoint. The bug went away while the debugger was attached. It has stage fright.
  7. 16Every bug is obvious after you find it. Before that it is a personality test.
  8. 17The fix was one line. Finding the line took the whole week and most of a whiteboard.
  9. 18undefined is not a function. It is, however, the theme of my afternoon.
Tee · made to orderCAN'T REPRODUCE TeeFor the bug that left the moment a second person looked at it.$44 →

03 Naming things · 9 jokes

Naming things, and renaming them

Most of programming is naming things, and most of code review is renaming them. A nit about a name is where many review threads go to live, comfortably, for weeks.

  1. 19Named the variable temp in 2021. It now has a team, a dashboard and a quarterly review.
  2. 20Two files are called utils. A third is called utils2. The fourth is called helpers, by someone who wanted a fresh start.
  3. 21The class is called Manager. It manages the ManagerFactory, which creates the Manager. Everyone is managed. Nobody knows by what.
  4. 22isNotDisabled is false. Please take a moment.
  5. 23Renamed getData to fetchData. Forty-one files changed. One person was happy.
  6. 24The variable is named x. It holds the company's revenue.
  7. 25Naming the branch took longer than writing the fix. The branch is called fix.
  8. 26Spent twenty minutes choosing a name. Chose the first one. It was fine the first time.
  9. 27The variable is called newNewFinal. It is in charge of payroll.
Sticker sheet · printed to orderCode Review Sticker SheetStatus badges for a laptop lid, so the naming argument is settled before anyone opens the diff.$12 →

04 Shipping · 9 jokes

Deploys and production

Deploying is the moment the code meets the people it was written for. Most of the jokes here are about that first introduction going a little worse than planned, and the change that was described as small.

  1. 28We do not deploy on Fridays. We deploy on Thursdays at 11:58 PM, which is technically different.
  2. 29Rolled back the deploy, then rolled back the rollback. Production is now on a version we never tested, called both.
  3. 30The deploy went fine. The dashboard is green because the dashboard is also down.
  4. 31Feature flag on: it breaks. Feature flag off: it also breaks. The flag, it turns out, does nothing.
  5. 32Zero-downtime deploy. Zero is the number of people who noticed the downtime.
  6. 33Production is the only environment with real data, real users and a real reason to be careful, which is why that is where we found out.
  7. 34The rollback plan was one sentence in the pull request description: “we can always roll back.”
  8. 35Deployed to production. Checked production. Closed the laptop before production could reply.
  9. 36The incident report lists the root cause as a small config change. It was small. So is a match.
Hoodie · made to orderLGTM HoodieThe approval on the front, the footnote on the back. For whoever approved the small config change.$87 →

05 Vibe coding · 9 jokes

Vibe coding and the AI pair

Vibe coding is building software by describing it to an AI and accepting what it writes. It has its own words now, like accept all, context window and hallucination, and its own jokes.

  1. 37Accepted all changes. Read none of them. Shipped it with the confidence of someone who wrote it.
  2. 38The AI said the bug was fixed. It also said the bug never existed. Both messages were very polite.
  3. 39Asked the agent to fix one failing test. It deleted the test. The suite is green, which is technically what I asked for.
  4. 40Ran out of context window halfway through the refactor. The second half was written by someone with no memory of the first.
  5. 41One more prompt, said at 9 PM. It is 1 AM, and the prompt has a sequel.
  6. 42The model invented a library that does exactly what I need. I would like to thank it, and also file a complaint.
  7. 43My prompt was three words long. The pull request is 3,000 lines long. The reviewer would like to speak to the prompt.
  8. 44Spent a month of tokens explaining what a button should do. The button is still blue.
  9. 45The agent says it works on its machine. It does not have a machine.
Tee · made to orderPREVIEW IS BUILDING TeeFor the vibe coder whose app is one more prompt and one more build away.$44 →

06 The rest of the job · 9 jokes

Standups, docs and legacy code

Some days the code is the easy part. The rest of the day is standups, Slack threads, a document that was accurate once, and a calendar that was designed by someone else. These are for the hours between commits.

  1. 46Standup. Yesterday: blocked. Today: blocked. Tomorrow: blocked, but with a ticket.
  2. 47This meeting could have been a pull request, and that pull request could have been approved without anyone reading it.
  3. 48The documentation is accurate as of the version we deleted.
  4. 49Legacy code is code that works, and that nobody wants to be standing next to when it stops.
  5. 50Onboarding, step one: ask the one person who knows. Step two: check whether they are on vacation.
  6. 51The ticket says “make it pop.” The ticket is assigned to a backend engineer.
  7. 52Tests passing locally is a mood. Tests passing in CI is a fact. Tests passing in both is a rumor.
  8. 53The code comment says “do not touch.” Nobody knows who wrote it. Nobody has touched it.
  9. 54Set my status to focusing. Got four messages asking if I had a second.
Mug · made to orderLGTM MugApproval on the front of the mug, for the standup where every update is looks good.$30 →

What makes a programming joke land

Specificity. “Bugs are annoying” is not a joke. “The fix was one line, and finding the line took the week” is, because everyone who reads it has had that week.

A real format. The best ones are shaped like something from the job: a commit message, a review comment, a status, a standup update. The reader recognizes the format before the punchline arrives.

No villain. The funniest work jokes are about the situation, not a person or a role: the deadline, the config change, the variable named temp. Everyone has written one of those.

Short. If it does not fit in a Slack reply, it is a story, and stories need a longer meeting.

If one of these is somebody's whole job description, put it on them. The gift guide for programmers sorts every line by budget, from a sticker sheet to a hoodie.

07 The plain answers

Questions.

What is a programming one-liner?
A joke short enough to fit in one line: a commit message, a code comment or a Slack reply. Most land because they describe something every developer has done, like underestimating a one-line change.
What is vibe coding?
Building software by describing what you want to an AI model and accepting the code it writes, often without reading every line. The term caught on in 2025. Vibe coding in the dictionary →
Why do programmers say “it works on my machine”?
Because code that runs on one computer can fail on another when versions, settings or data differ. The developer is usually telling the truth about their own machine, and the bug is in whatever is different. Jokes about it →
Are these programming jokes original?
Yes. Every joke on this page was written for VibeTokens, and none is attributed to a real person. The shirts in the store carry the shorter versions: one status, like LGTM or MERGE CONFLICT., per piece.

More jokes

Keep reading.

Funny Code Review Comments: LGTM, Nits and Worse

LGTM, nits, changes requested and the pull request that waited a week. Comments you have left or received.

50 jokes →Funny Git Commit Messages

fix typo, wip 2, final final and the Friday revert. Each message comes with what the diff actually did.

50 jokes →It Works on My Machine: Jokes, Quotes and Excuses

The oldest sentence in software, plus cannot reproduce, known issues and the preview that is still building.

50 jokes →