This is true.

@sjvn Painfully true...! I talk to a Teddy Bear a lot - not a rubber duck and it's surprisingly effective...!

What I hate are the web pages with the exact same problem I'm facing and either no answer at all, or even worse a comment from someone who fixed an issued but doesn't mention what they did!

@EricCarroll @sjvn Perfect; if rubber duck size is proportional to problem size, this should do me.
@sjvn Where's "25 minute nap" on this chart, do you think?
@krans @sjvn nap can’t be charted unless this had a logarithmic y axis
@krans @sjvn not far from “take a walk”. Getting a good nights sleep would also be in that area.
@sjvn I feel as though the “Run the same code, hope it magically works now” point should be a bit higher on the y-axis.

@sjvn running the same code again without changing it is actually very important to make sure it's reproducible. Just because that's the case most of the time, doesn't mean it's not effective at doing showing that.

Otherwise I agree.

@bmaxv @sjvn I'm terrified of doing that before I've got an idea of what's happening, because I've had too mny bad run-ins where a problem occurs very rarely and I don't know when I will get the chance to investigate it again. It is for this reason I tend to add logging in anticipation, instead of AFTER something goes wrong.

@sjvn

print("here")

I feel called out 

@sjvn read docs is way too far to the right
@sjvn First page of googling has dropped sharply in relevance in the last 5ish years.
@raffitz All too, too true. And, it's only going to get worse. :-(
@sjvn Write... a... test?? Apparently to the left of "Take a Walk."
@sjvn I prefer penguins to ducks.
@sjvn I'd rate print("here") higher.
@sjvn
The solution that actually works for you is far more likely to be on the 5th page of Google than the 1st page!
@sjvn undervalues print-debugging though
@sjvn Dammit! "Use breakpoints" LOL guilty
@sjvn A colleague of mine used to find that explaining it to me worked amazingly well, especially when I was asleep.