Exactly! My husband is a software developer - not just coding but he designs whole systems. And he has often pointed out that writing a novel is a very similar process. You can't get there by "top down design" or even "waterfall" - these methods are linear and suitable only for well understood problems. So when designing a complex system, you have to go round and around.
He also calls editing "debugging" and and as with fixing code, it's important to watch out for "side effects" when making changes.
Thanks Ann! I love that analogy - what is a novel if not a complex problem, for the person trying to write it anyway. the 'side effects' bit as well, that's where the real trouble lies!
Exactly! My husband is a software developer - not just coding but he designs whole systems. And he has often pointed out that writing a novel is a very similar process. You can't get there by "top down design" or even "waterfall" - these methods are linear and suitable only for well understood problems. So when designing a complex system, you have to go round and around.
He also calls editing "debugging" and and as with fixing code, it's important to watch out for "side effects" when making changes.
Good to see you back again!
Thanks Ann! I love that analogy - what is a novel if not a complex problem, for the person trying to write it anyway. the 'side effects' bit as well, that's where the real trouble lies!
Interesting point. Whatever about one’s original intentions, it’s an inherently messy, almost haphazard process.
yep!