Liked a bunch of these recent ones. The tips on deep point of view are well-taken; I try to do this but don't always succeed.
I really liked the "Why you need to stop rewriting" one. It reminds me of a saying in software development: "Write one to throw away." Why? Because the first one you write, you started it without knowing the details of what you were trying to accomplish. It was an exploratory work, an "understanding by doing" effort.
By the time you finish writing the first version of something, you know what you're trying to do. But the words, or program/function/subroutine, that you have still contains a lot of what you wrote before you wholly understood the task.
So, "throw it away." (Don't really trash it, of course — just don't refer to it while writing it again). If necessary, write down everything that you learned, but if the piece is short, you don't even have to do that.
Doesn't work for everyone, and doesn't work for every situation, but if you have a case where a piece of your work technically works — it accomplishes what it should — but isn't quite "right" it might be just the cure you needed.
I think I may expand this to a blog posting of my own, in fact.
edited 19th Jun '12 7:28:21 PM by Morven
A brighter future for a darker age.