The writer commented on how some of his best code was written away from the computer and how all of this fast reloading causes poor code to be written. I'm not

The writer commented on how some of his best code was written away from the computer and how all of this fast reloading causes poor code to be written. I'm not sure if he would disagree with me, but I think a lot of it depends on the kind of person you are and the kind of problem you are solving. Some problems can't really be solved well iteratively (voice-recognition and DSP for example), while others can. Similarly some people work better iteratively while others do not. I think it's similar to writing an essay in some ways. Some people sit down and think for a while, then write the essay in one sitting. They then make some minor grammar corrections and otherwise polish the essay before submitting it. Others (like me), sit down and write whatever comes to mind. Then they rewrite everything, and then they rewrite everything again, etc. Finally they have an essay that they are happy with, make some small polishing changes and submit it. In the end, both approaches work fine for writing an essay, just like both approaches work fine for writing code. The key, when talking about speed and iterative development, is that the code isn't finished when you have something that appears to work. You have to go back through and rewrite things, refactor, add additional tests and clean the code up.