Programmers have it rough sometimes. One instance is when their system or site has a bug, and it is difficult to find just where that bug is. It can get frustrating. It can feel hopeless.

What to do? The Rubber Duckie Test of course! Also known as Rubber Duck Debugging, the Rubber Duckie Test is a method of debugging code used by software engineers. The name comes from a story in “The Pragmatic Programmer” in which a programmer carries around a rubber duck and figures out how to debug a system by explaining the problem line-by-line to the rubber duck.

By describing what the code is supposed to do in simple terms and then also explaining what is actually happening, the programmer is often able to discover the issue. By employing an inanimate object, such as a rubber duck, the programmer doesn’t need to talk out the problem with another person.