A folder full of files called “final” tells a familiar story: the work changed, but the names did not keep up. Finding the right item now requires opening several candidates and reconstructing their history.
Choose a few details that distinguish the files in your actual work. A project name, a subject, or a consistent date may help. A complicated naming rule can create its own friction if it requires information no one has at the moment of saving.
Test the pattern on a small collection and imagine returning a month later. Can you identify the purpose and the current version? A name should help the next person begin, including the next version of yourself.
- Choose the details that distinguish your files.
- Use a pattern you can maintain.
- Try finding an item without opening every candidate.
Try the idea in context.
Consider naming a document with its subject and revision rather than final-final. The filename can explain why two nearby copies both exist.
A thought for the next read.
Try the method on one real task before making it universal. The exception you discover may be the most useful part of the experiment.
Follow a related question
Save at a meaningful decision.
Versions that explain the revisionCheck the actual interactive area.
Touch targets with room to moveKeep learning
Related background to continue exploring this subject.
Git: version control fundamentals Mozilla: backing up and restoring browser data
