A creative project often contains several plausible directions. If each change overwrites the last, it can become difficult to remember why one version worked differently from another.
Save a version at a meaningful decision and give it a descriptive note. State the question being tested, such as a shorter opening or a quieter composition. A sequence of unexplained numbers preserves files without preserving the reasoning.
Compare versions around the same purpose rather than judging each by a new standard. Keep the alternatives that carry useful learning and release redundant copies when appropriate. Versioning helps the work when it makes a revision easier to understand.
Try the idea in context.
A new draft could include a note that the opening now answers the reader’s first question. The explanation makes the revision easier to review.
A thought for the next read.
Keep a trace of the choice that changed the work. A later collaborator should be able to see the reason for a revision, not only the final arrangement.
- Save at a meaningful decision.
- Name the question the version tests.
- Compare alternatives against the same purpose.
Follow a related question
Notice what is complete or waiting.
A review that stays lightweightCheck the actual interactive area.
Touch targets with room to moveKeep learning
Related background to continue exploring this subject.
Git: version control fundamentals W3C: accessibility, usability, and inclusion
