I kind of think the moral of the story here is: "Wanna write a lot? Write crap! That's why I'm so awesome!"
It's true, of course, to an extent. "Writing crap" is absolutely essential in any creative endeavor. Otherwise that crap gets impacted, and the good ideas can't get out.
However, the editing and refinement process is at least as important, I think. If all you do is just write a lot, most of it being bad, it might just all stay bad. You have to be trying not to write crap, knowing that's what you'll often end up doing, and be ok with that.
It's the same in software development. Over-reliance on design can lead to analysis paralysis. Software is best when there's code first, and analysis afterwards.
It's probably worthwhile to have a dev branch and release branch in blogs, for the same reason as it makes sense for code. Friends and regulars can see the just-released content, but the mainstream page doesn't show anything that hasn't been vetted and carefully edited.
I kind of think the moral of the story here is: "Wanna write a lot? Write crap! That's why I'm so awesome!"
It's true, of course, to an extent. "Writing crap" is absolutely essential in any creative endeavor. Otherwise that crap gets impacted, and the good ideas can't get out.
However, the editing and refinement process is at least as important, I think. If all you do is just write a lot, most of it being bad, it might just all stay bad. You have to be trying not to write crap, knowing that's what you'll often end up doing, and be ok with that.
It's the same in software development. Over-reliance on design can lead to analysis paralysis. Software is best when there's code first, and analysis afterwards.
It's probably worthwhile to have a dev branch and release branch in blogs, for the same reason as it makes sense for code. Friends and regulars can see the just-released content, but the mainstream page doesn't show anything that hasn't been vetted and carefully edited.