I've always wanted to write a novel, and I hope to some time before I die (or afterward, I guess.. but who knows what's possible then).
I like the way this article describes architect vs gardener writers. I've always felt this internal conflict of modes when trying to write. I actually think there is a similar spectrum for coders. As a programmer, I definitely architect-first (within whatever scope I'm in) as opposed to feel-it-out-as-I-go. Yet great programmers I know just get started and sort of see where they land. (Iterative refinement is key in both styles, in my experience, and I'm sure the same is true of writing.)
In writing, I always think I should architect the story and setting, so as to validate whether it will be interesting or not at a high-level. But when I try to do this, I seem to end up with uninteresting, low quality results and the process itself feels contrived and burdensome. When I free flow, I seem to do a lot better. But I'm not sure if that's because I just don't have practice in trying to hold all the bits of a story in my head and craft it into a good outline which I can then flow from, and/or if it's because I only write short bits of material (ie the free flow might become unwieldy at length).
Curious what others think about the architect vs gardener coder bit, and also how those who write relate their writing approach to their coding approach.
Do you want to write a novel or do you want to write a good novel? I mean either way it's pretty easy. Just start writing and don't stop. That's kind of the whole NaNoWriMo thing. To write a good novel you just need to write like a dozen shit ones first. Ray Bradbury says ~a million words of bad fiction.
Heh. :-) I'd love to just accomplish writing one, even if it's shitty. But of course would prefer a good one, at some point.
The issue for me at the moment is just carving out the time / paying the opportunity cost to go for it. Not quite ready to dive in yet, but I think about the methods once in a while.
Thanks for the reply and advice! I think it'd be sage to bear in mind if/when I start.
I like the way this article describes architect vs gardener writers. I've always felt this internal conflict of modes when trying to write. I actually think there is a similar spectrum for coders. As a programmer, I definitely architect-first (within whatever scope I'm in) as opposed to feel-it-out-as-I-go. Yet great programmers I know just get started and sort of see where they land. (Iterative refinement is key in both styles, in my experience, and I'm sure the same is true of writing.)
In writing, I always think I should architect the story and setting, so as to validate whether it will be interesting or not at a high-level. But when I try to do this, I seem to end up with uninteresting, low quality results and the process itself feels contrived and burdensome. When I free flow, I seem to do a lot better. But I'm not sure if that's because I just don't have practice in trying to hold all the bits of a story in my head and craft it into a good outline which I can then flow from, and/or if it's because I only write short bits of material (ie the free flow might become unwieldy at length).
Curious what others think about the architect vs gardener coder bit, and also how those who write relate their writing approach to their coding approach.