Hacker News new | past | comments | ask | show | jobs | submit login

I’ve noticed this quite a few times before when working with my systems administrator: He calls me in for a debugging session of a problem he‘s been stuck on for some time and within a few minutes (or less than a minute) he finds the solution. I’ve always seen it as him having to reorganize his thoughts to give me a somewhat structured introduction into the problem. And somewhere along the path he finds the missing piece.



Rubber ducking works better with a live duck.


Attempts have been made to replicate this effect, with limited success, through the use of a rubber duck:

https://rubberduckdebugging.com/

The general idea is to first try explaining your problem to the duck, which is thought to activate the same problem restructuring pathways. However, I've always found that a human makes for a much better rubber duck in practice. Something about the immediacy of the conversation helps my brain to stay on task and not get distracted partway through the explanation.


This happens to me too but I also find taking a walk is all that I need and often try not to drag other people into it


This, absolutely. Can totally relate.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: