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

Same concept as rubber duck debugging.



This is a big reason why asynchronous communication works better for me. I can't begin to count the number of problems I've solved in the process of writing an email asking for help. And many more times where the question I was intended to ask changed to a completely different, and more useful question. The process of collecting the information I have, ended up pointing to holes in my thought processes and led to the solution.

If I had gone straight to Slack I would have wasted other people's time, and cheated myself out of thinking through the problem myself.


Very true. Email forces you to compose rather than emit streams of consciousness.

And composing often leads to solutions even before you press Send.

https://mobile.twitter.com/b0rk/status/1546875361002135554?r...


I think the key here is that by putting it to paper (so to speak), you linearize and structure the problem and all it angles in a way that are conducive to methodically advancing your understanding.


My employees don't seem to understand why I prefer they email questions to me instead of calling. The clarity writing often brings aids the conversation. I frequently call once I have the email.


Kind of but writing has the added benefit of being easily inspectable after fact. Speaking out loud will identify some weak logical points, but writing will catch even more.




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

Search: