![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhn3Z5RN3K0DLKAuHrcNas6-fLyJay3nbSMrRlgGA0qWN9PKJjXopfrwdx1pyzzAZ_LGmmECEIe8oZvpoK_N5iJDR6insumLe9mf2STYnj0tRdlo6XPGpZrYHP7rYI7J9uF6xwbaPqbzzw/s400/RubberDuckDebugging2.jpg) |
Rubber duck debugging at home |
Recently, I shared with you my
best practices for working from home. Today, I want to add an angle specific to technical jobs, especially for developers. When you work in co-located teams, you benefit from the direct conversations and exchange. In (software) development and technical writing, it is important to rethink ongoing processes or ideas, to reassess a situation, to explain what you do.
Rubber duck debugging is one such method - debugging code by explaining it to a rubber duck.