3 ms·
when it comes to problem-solving in software development, I tend to regard my subconscious as a black-box object with a fuzzy help me! method I can call. If I h
by RyanMcGreal 12y ago
when it comes to problem-solving in software development, I tend to regard my subconscious as a black-box object with a fuzzy help me! method I can call. If I have a coding problem I'm not sure how to solve, I go for a brisk walk and let my mind wander. By the time I'm done, I've got the answer. If it's a tougher problem, I might need to go home and get a good night's sleep. Then I usually wake up with the answer fully-formed in my head. I give a silent moment of thanks for "the boys downstairs" and go about my day.
- vinceguidry 12y agoI've gone a bit deeper with it. I spend 7-8 hours at my desk every day. I get about the same amount of work done each day, but I don't consciously control how I'm spending those hours. I might be reading / posting on HN, thinking about personal stuff, or even coding. When doing the latter, sessions start when I feel motivated to code and stop the very instant I'm not feeling it anymore. After I stop, my subconscious goes to work. While I'm 'screwing around', insights will bubble up concerning the broader architecture of the platform I'm building and where the thing I'm coding now fits into it. At some point I'll realize why I stopped coding and what I need to do to continue. It's inevitably some deeper consideration that I never would have thought of had I not taken a break. I've also stopped making mistakes more than once. The second I make one, I lose motivation to work until my subconscious has worked out why I made it and how not to make it in the future. I had to 'give myself permission' to operate in this way. Conscious mind just doesn't want to give up control, you need to exercise will in order to give up will. It was a little scary at first. As I built up confidence, I started trusting myself to do it more and more.