: Fiction writing: is using Git overkill? Hope this question isn't off-topic because it involves programming software (for some reason I think many people in this site has used Git, though). Git

Vote Up Vote Down

I start my documents as "NameOfDocument 000.doc" (or similar, depends on software being used.) Every time I start a writing/editing session on the document, I do a "Save As" and increment the number, before doing anything else. I find the Undo/Redo commands to be sufficient within a session. Exception: If I'm about to perform major surgery, e.g., delete/move large sections, I'll save, then SaveAs with an incremented number. Then I'll make the major changes.

This method works with any software (and any computer task). Storage is MUCH cheaper than your time.

Also, don't forget to copy all those backups to another physical location, or a fire/flood could destroy your magnum opus.

(0)

Vote Up Vote Down

I think git is a bit overkill, because you have to remember to commit it all the time it does not just happen like after a save.

Options that I can think of

Google Docs it has a Revision History view
Microsoft word has Track Changes (I don't know much but one site I found www.techrepublic.com/article/microsoft-office-word-101-use-track-changes-more-efficiently/)

(0)

Vote Up Vote Down

I use git for fiction. Sometimes I'll save versions at various milestones, such as when I finish a chapter). But more often I forget, and save a version only when I finish a draft.

Some other times that I save versions:

Before and after I apply my editor's edits.
When I finish creating a book cover, book interior file, or epub file.
Whenever I want to try experiment with the cover or interior. For this, I not only save a version, but create a "branch" that I can use to try lots of ideas.
Whenever I create a copy of the manuscript in a different format, such as when a magazine wants a .doc file, or .rtf file, or text file.

It might be overkill. Git shines with text-based files, on projects where you're collaborating with others. I use only a tiny fraction of git's features for fiction. Other version control systems (e.g. subversion) are potentially simpler.

But I'm comfortable with git from my software development work, and I really like being able to create new branches to experiment on.

I don't think I've ever reverted to an earlier draft. If I don't like a scene or a chapter, I'll just drag it into my "deleted scenes" folder and start again.

But I often revert when I'm experimenting with covers and interiors.

(0)