Be Creative: Put Your Error Patterns Into Famous Quotes

Discussions
,
1

Over the years, I’ve uncovered a lot of errors. Along the way, I’ve noticed certain recurring patterns, like sign errors in formulas. Recently, I had an idea: What if we took famous quotes, proverbs, and sayings and plugged these common error patterns into them?

For example:
That’s one small sign error for a formula – one giant crash for the system.

This can actually be a helpful way to keep these error patterns in mind, reminding ourselves of where things can go wrong.
Now it’s your turn: What error patterns keep popping up for you? Can you fit them into famous quotes or proverbs? Let your creativity flow!

2

Hello, this is customer support. Have you tried updating the app?

3

There are fundamentally only 2 types of -programming error.

  1. Cache inconsistency
  2. Naming the animals
    oh, and Off-by-One errors
4

Objects that live in empty houses should not throw Null Reference Exceptions.

5

We are finished. Aren’t we?

(More common than famous.)

6

A small typo for a dev, a big typo for the customer.

7

I thought you did.
No, I thought you did.

8

We didn’t start the process.

9

What we call criticism in real world is bug in testing world.

10

Timeout will tell __

11

The%20only%20thing%20we%20have%20to%20fear%20is%20fear%20itself.

12

Ask not what your compiler can do for you, ask what you can do for your compiler.

13

Not all those who wander are 404 Not Found.

14

Snug as a bug in a newly developed feature

15

Bugs of a feather flock together

16

Don’t count your finished tickets until they’re tested

17

When the going gets bug-y, the testers get going

18

Delete an object once, it’s erased; delete an object twice, system crash on you

19

The robust code catches the exception

20

These are not the bugs you are looking for.