Neither. I tend to stare down a problem until I can solve it. I want to have the whole solution, or at least the critical parts of it, in my head before typing it out.
One of my bosses described my technique as "do nothing all day and get stuff done."
There were three similar projects assigned to our division, each assigned to a sub group of three people (typically a programmer, a psychologist/researcher, and a designer). My sub group was the only one to successfully create and deploy their application before the three month deadline.
(I also moved them over to Pivotal Tracker since putting stuff into their regular system was abandoned long ago and the white board was becoming an organizational nightmare.)
17 comments
[ 2.8 ms ] story [ 55.6 ms ] threadI'm 45, a "Both" and use Win7 and Linux.
Outside of the occasional burst, my programming style is typically cautious and incremental, but not perfectionist.
Someone should make a politicalcompass.org type test that plots your Steveiness and Chrisiness.
One of my bosses described my technique as "do nothing all day and get stuff done."
There were three similar projects assigned to our division, each assigned to a sub group of three people (typically a programmer, a psychologist/researcher, and a designer). My sub group was the only one to successfully create and deploy their application before the three month deadline.
(I also moved them over to Pivotal Tracker since putting stuff into their regular system was abandoned long ago and the white board was becoming an organizational nightmare.)