Yes, it does sound like a sex thing, doesn’t it? And if that’s why you came (ahem), maybe stick around anyway because it won’t be long (goodness) or hard (oh dear me) and over quickly (swoon).
So in coding, there’s a concept called rubber ducking. Some coder, in the distant past, discovered that if they had a tricky problem, and brought in another coder to help them, the very act of explaining the situation to the other coder would often let them work out what was causing the issue.
“So it’s the weirdest thing. Look, I go here to this part of the code, and this data comes in, and I add it to the list, but then it just … oh. Hang on. I’m not actually adding it to the list, am I? I’m just adding it to a temporary list, which then gets deleted. Right! Thanks for the help!”
In fact, it was soon discovered that another coder wasn’t even required for this to work. You could get the same effect from explaining your problem to any person or object, such as a rubber duck on your desk. Hence the phrase rubber ducking.
And by the now, the humble rubber duck has probably helped to debug more code than anything else in the world. In fact, this concept extends to life in general. It’s basically how problem pages work (“Dear Margie, I want to know if I should leave my husband.”), and also tarot cards (“Dear Margie, will I meet a tall dark stranger when I leave my husband?”). Because if you, as the person with the issue, can sit down and explain to someone (or a rubbery something) exactly what the problem is that you want help with, then you’re almost all the way there.
You see? Not hard at all. Also totally covered in rubber. Which I know you like.
/ Paddy