I am somewhat past the middle of a career as an analyst/programmer of various flavors. As I look back on the previous quarter-century, I find that the software I am most proud of is that in which the development effort was punctuated by frequent spells of pushing the chair back from the desk, getting up, and going for a walk about the facility. No destination in particular, just putting one foot in front of the other, probably with a glazed look on my face. Thinking about the project, the current hurdle, and various means of jumping it. Eventually I would surface from these cognitive dives, floors away from my workspace, with a decision on the optimal way to solve the problem. One of these projects is still running a global datacenter, largely unchanged, 20 years post-implementation.
Time to think is the most precious resource an analyst has.
As a 39 year old programmer the most important thing I've learned is that my subconscious brain is way smarter than my conscious brain and the best way for me to solve a difficult problem is to think about it for a little bit and then not think about it for a while.
Later when I'm walking or in the shower or just waking up from sleep, a solution far better than any I came up with using focused thought will suddenly appear nearly fully formed in my head.
Agreed. For me however I push myself to talk to others I respect about my work. This forces me to articulate what it is that I'm doing and why I'm doing it the way I am. I found this technique priceless.
Indeed--I find it works best when the person I'm talking to doesn't know anything about software, so that crucial points don't get hidden beneath a layer of shared abstract understanding.
Time to think is the most precious resource an analyst has.