When I write computer programs I use a free system (git with vscode) that with a click lets me save and recover versions. I can create branches - the diagram on the left shows how, from the bottom, a file evolved, splitting into branches then mostly merging. I can compare versions side-by-side, the differences colour-coded.
It's possible (I haven't done it, but I've seen it done) to analyse the development of a text, colour-coding the lines according to age or number-of-changes.
With a click I can back-up to the cloud (free - github). In my will I can leave the instructions to make the back-up visible to all. Nothing's lost - even my mistakes.
I could use the same system for poems/stories too. Already I have long/short versions of a few poems. Because of the various word limits for prose, I have 3 versions of a few texts. One recent short piece had so many UK/US issues (gear-sticks, supermarket trolleys) that I keep 2 versions of it. But I'd be most interested in watching how a story develops - which paragraphs changed the most? which paragraphs never changed? when were the growth spurts? (I think there's often an initial one, then I fiddle around, then I realise what the story's about and quickly add many more words).
My story collection "By All Means" (ISBN 978-0-9570984-9-7), published by Nine Arches Press, is on sale from 
My poetry pamphlet "Moving Parts" (ISBN 978-1-905939-59-6) is out now, on sale at the 
No comments:
Post a Comment