Well… uh… yeah, it's a weird title but I found it interesting and actually, it worked for me.
It happens that developers get stuck in the head a lot, sometimes we don't hit the nail on the head and we are, as you would say colloquially, in my country stripping the shot all the time without reaching any solution. This is sure not only happens to developers, I can bet it happens to anyone who needs to solve problems in their work, whether they are artists without their muse, or KZKG ^ Gaara trying to invent some way to do something that someone else has already done, but in bash (xD).
Anyway, my solution for this was precisely to get up from the PC for a while, make a coffee, go to the patio and go around and around talking to myself while I finish my coffee and smoke a cigarette. It has worked for me, I have a lot of chalk-scratched walls and ugly algorithms in the work we have at home (and my mother wants to kill me), but reading this article en Geek World I realized that there is a more productive way of doing things and less destructive for my little lungs and for the walls of the work, and surely that will preserve my skull from flying objects propelled by maternal force (xD).
It turns out that psychologists have documented that vocalizing (talking) about the problems and ideas that we have helps, for some reason, to clarify and organize them; which explains why doing what I do has been giving me results (although when someone sees me, they think I'm crazy). Anyway, rubber ducky debugging is based on something simple: you buy a rubber duck, you put it on your desk next to your PC / Laptop and when you have to vocalize, well, you talk to the duckSimple isn't it?
Sure, in my case I don't have a duckling, but I have an old stuffed pikachu that they gave me a few years ago and, nothing, it's yellow, so it should work.
I hope the advice serves you, yes, the only disadvantage is that if they already have a reputation for being weird, this is not going to help them; well they say in the original article.