Pretty good post. Writing on pure impulse is good for practice and discipline and short-length things, but it won't help you when you need to write a ton of st

Pretty good post. Writing on pure impulse is good for practice and discipline and short-length things, but it won't help you when you need to write a ton of stuff that has flow and needs to be coherent. It is great for a first 'driver' to get you doing something productive, but you need to combine it with additional 'drivers' along the way (planning, coherency, etc.) For instance, I could not imagine GRRM being successful with ASOIAF if it was written without discipline and planning. An interesting contrast is that this author praises unique ideas, but discards its execution as less important (or not important), while most programmers are more concerned with the execution of ideas, since the ideas in that realm are very common (usually). In both cases though, it's ideal to have both a good idea and good execution. In the case of this post, the execution is in the word choice, word play, and other writing elements I don't remember from school because I was too busy writing drunk and editing drunk.