I just learned[1] that there is an actual term for the technique of figuring out the solution of a programming problem by trying to explain it to a rubber ducky.
It’s called “rubber ducky debugging”!
I already heard about this technique before; in an article from somewhare in the web (I cannot remember anymore where).
If I remember it correctly, the writer said that if we have a problem or a bug in our code, and we find it hard to figure out the cause of the problem, we should try to explain it to a co-worker.
But our co-workers are busy of course! We can, instead, provide for ourselves a rubber ducky and then try to explain to the rubber ducky our problem.
If I remember it correctly, the writer said that the process of explaining our problem helps us organize that problem in our brain, and helps us in figuring out the solution to that problem.
It’s good that this is included in the lectures[2] because it seems like I will be needing this technique in the next few weeks of my life! 
Happy rubber ducky debugging! 
… Or happy talking to the wall debugging, as in my case.
[1][2] … from Lecture 7 (with Dr. Ana Bell) of MIT OpenCourseWare’s “6.0001 - Introduction to Computer Science and Programming in Python” (Fall 2016)
