4 ms·
lol. that's me; only I start by writing out the problem as an email to ask someone for help. 90% of the time, I find that I didn't have a complete understanding
by Pokepokalypse 4y ago
lol. that's me; only I start by writing out the problem as an email to ask someone for help. 90% of the time, I find that I didn't have a complete understanding of the problem to begin with, and I usually end up solving it before hitting "send".
Then I'll have this odd memory of - "I discussed this with you, I told you all abo- oh wait, I didn't send it."
- jrochkind1 4y agoWhich is so common it's basically what's called https://en.wikipedia.org/wiki/Rubber_duck_debugging https://en.wikipedia.org/wiki/Rubber_duck_debugging
- heisenbit 4y agoI found that sometimes sending it is required for me when I‘m absolutely stuck and have explained it a few times. It sort of commits it to memory and frees up mental resources then able to come from a different direction.
- sedawk 4y agoI thought I was the weird one... Many a times have I debugged an issue and was convinced of where is the bug and what the fix is. Only to discover that I was off in both the regards when I sat down to write a detailed email to the team! I felt I was wasting too much time. But I've realized that for me the time spent writing something in details has always helped me fill in the gaps and also discover the unknowns.