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.
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.
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...).
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.