[justindz]

I'm not sure I quite expected to see this on HN, though I'm glad it was posted since I happen to be trying to learn novel writing. I thought the before and after example of the basketball article was a concise and clear way to explain over-writing. The second version was clearer, more accessible, less obnoxious and no less informative and narrative. A series of poetry and short fiction teachers in college helped me become self-aware about this bad habit. I still make the mistake consistently, but I have learned to either catch it or agree with the suggestions of my peers who catch it when I don't.

I personally believe that programmers can learn from poets, for example. Write constantly. Read the work of others, both critically and for enjoyment. Writing is the sexy part, but revising is at least as important a task.

[scott_s]

I find your last sentence amusing because I actually prefer editing to writing. It's when I'm editing that I feel like I'm actually applying a craft. I get the same kind of satisfaction from editing my words that I do from refactoring my code. In both cases, it is often only after doing the initial work that I realize how it should be structured, and reworking it into that elegant structure is satisfying.

[rudolf0]

Can't agree with you more, both for refactoring code and editing prose.

I find it also sometimes helps to perform the revisions while in a somewhat altered state of mind (be it mood, setting, music, minor inebriation, or otherwise). It helps you look at the first draft with fresh eyes and see better ways of structuring things and removing excess. Make a version with your prospective changes, then compare the before and after copies a day or two later (this time sober if you weren't before...).

[magic_beans]

I never thought to compare writing words and writing code, but it's true. The writing phase is simply getting all the ideas out, and the editing phase is to make... beauty out of chaos!

[justindz]

I am the same way. I found it surprising. I get so much positive feedback from the editing process that I have actually developed a routine of editing as I draft. Although it improves the quality of my draft, it takes ages. For poetry, it worked well. For novels, I think I'll need to break the habit.

[ricree]

Though for what it's worth, I've seen a lot of professional authors that warn about that as another kind of trap that beginners fall into. That is, paying too much attention to the revision process, at the expense of producing actual finished works.

[GoodIntentions]

>I'm not sure I quite expected to see this on HN

I think it belongs - What he is suggesting carries over to technical endeavours as well.

1. Learning to cut mercilessly improved clarity of my emails and documentation.

2. Learning to put my head down and carry on till a project is first draft complete, warts and all improved my ability to actually _complete_ things.

3. Peer review as a bullshit detector is good.

I'll take Poe or Lovecraft over King any day for entertainment, but I might just crack 'on writing' after reading this article. The man sounds pretty dialed in.