[andrewstuart]

Sometimes I think for hours and hours trying to work out how to do something.

More often I’m thinking about how to avoid doing something. A really great days work is thinking until a whole bunch of coding never needs to be done cause I thought of a way to not do it.

Sometimes I attack myself for thinking too long on how to do or not do something instead of rolling my sleeves up and starting to code. But then I ease up the attack because there’s no clear way to know when you’ve done too little, just enough or too much thinking.

Some of my best coding outcomes have been the result of six hours or more staring at the screen, looking at the ceiling, pacing around the room, reading and researching, looking through code, maybe trying out a few theories with little test programs.