rubber duck debugging

In software, we do something called ‘rubber duck debugging’. It’s where you tell a little rubber duck about the problem you are trying to solve, and you end up solving it yourself while you’re explaining it.

It’s because to solve a problem, you need to define it. Saying it out loud forces you to organize the problem enough to communicate it - giving it proper definition. The solution becomes obvious.

You don’t really need a rubber duck, and it works for every type of problem - not just engineering. If you’re trying to do something and keep getting stuck, say what you’re doing out loud or write it in email to someone (even if you don’t send it).