What is Rubber Duck Debugging?

Bugs in programming are frustrating but how to find them? Is it just a typo?

Often it helps to explain the problem to someone else which in turn help you understand the problem better and find a solution. While walking through the code to someone else, you most likely spot the bug in the process.

Introducing the rubber duck. An inanimate object to explain your code to line by line. thus the technique of 'Rubber duck debegging' was introduced.

Content From: FreeCodeCamp.org: Rubber Duck Debugging By Kolade Chris

What is Duck Typing?

“If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.”

In computer programming, duck typing is an application of the duck test—"If it walks like a duck and it quacks like a duck, then it must be a duck"—to determine whether an object can be used for a particular purpose. With nominative typing, an object is of a given type if it is declared as such (or if a type's association with the object is inferred through mechanisms such as object inheritance). With duck typing, an object is of a given type if it has all methods and properties required by that type.[1][2] Duck typing may be viewed as a usage-based structural equivalence between a given object and the requirements of a type.

Content From: Wikipedia: DuckTyping

Other Links:

• Do We Have an Obsession with Ducks in Software Development? By Steve Gordon