Skip to content
CONTACT

20 programmer excuses for when the program doesn't work

20 PROGRAMMER EXCUSES

The programmer doesn't make mistakes: he is misunderstood by the universe. When the program breaks in front of the client, the programmer doesn't panic. He opens his repertoire. Here is the chart of the twenty most used excuses, collected over years of meetings with a projector that won't switch on.

From 20 to 11

  • 20. “Interesting.” Said with the look of someone who has just seen a living fossil.
  • 19. “This error doesn't exist. I searched for it and it's not there.”
  • 18. “It was working before lunch.”
  • 17. “It's the full moon: servers are sensitive.”
  • 16. “The code is correct, it's the data that's touchy.”
  • 15. “My colleague wrote that. The one who left.”
  • 14. “It's a hidden feature. You weren't supposed to find it so soon.”
  • 13. “The client clicked too hard.”
  • 12. “I'll fix it in the next version. The one after the next one.”
  • 11. “Have you tried not doing what you were doing?”

From 10 to 2

  • 10. “It's a cache problem.” Nobody knows what the cache is, so nobody can argue.
  • 9. “I updated a library. Only a small one, the kind that doesn't do anything.”
  • 8. “The program was written for a future that hasn't arrived yet.”
  • 7. “The artificial intelligence assured me it worked.”
  • 6. “The time zones have aligned.” Always said on the day the clocks change.
  • 5. “It only does it when you're watching.”
  • 4. “There was one semicolon too many. They put it there, on the sly.”
  • 3. “It's the Wi-Fi.” Even if the program doesn't use the network.
  • 2. “But I told you in the meeting.” Nobody remembers the meeting. Not even him.

Number one

And the excuse that wins every year, unbeaten, celebrated in the corridors of every technical office in the world:

“It works on my laptop.”

Said with solemn calm, like a revealed truth. And it's true. It works on his laptop. The problem is that the client, unfortunately, can't buy his laptop. We tried, once. He said it wasn't for sale.

Since then, at the agency, we have a simple rule: before every delivery, the program must work on at least one computer that doesn't belong to whoever wrote it. It's our strictest quality procedure. Also the most ignored.


Loosely based on an old piece from the teneraerbetta.it archive