I was on Youtube watching an endless stream of videos (basically constantly going on a screen as background noise) and I came across a video that reminded me of something I learned about a while ago and still do today - rubber deck programming.

What is Rubber Duck Programming?

Rubber duck programming is a method used by programmers to debug and solve complex coding issues. The process involves explaining the code, line by line, to an inanimate object, typically a rubber duck. This technique is based on the idea that explaining the code out loud helps the programmer to slow down and examine the logic and flow of the code more thoroughly. This often leads to a better understanding of the problem and can help in identifying errors or better solutions.

The term originates from a story in the book "The Pragmatic Programmer" by Andrew Hunt and David Thomas, where a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck.

The act of verbalizing thoughts and explaining the purpose and logic of the code often clarifies the solution to the problem, even if the rubber duck does not contribute to the conversation.