Fifteen minutes now saves an hour in January, and it saves it on the
worst possible day β the one where the project is due and the file is
called final2 copy (1).py.
The shape to build today
ICS3U/
βββ Unit 1 β Foundations/
β βββ temperature.py
β βββ ticket_price.py
βββ Unit 2 β Data/
β βββ readings.txt
β βββ averages.py
βββ Tasks/
β βββ The Toolbox/
β βββ toolbox.py
β βββ demo.py
β βββ usage note.md
βββ Journal/
Three rules keep it working:
- The folder says where you are; the file says what it is. Inside
Unit 2 β Data, a file calledaverages.pyis clear.unit2.pyis not, anywhere. - Data sits with the program that reads it. A program that opens
readings.txtwill only find it if they are in the same place β which is the single most common reason a program that worked yesterday does not today. - No spaces at the start, no dates in the name. Let the computer track dates; it is better at it than you are.
Doing it on your machine
Use the operating systemβs file manager β Finder on macOS, File Explorer on Windows, Files on most Linux desktops. Make the folders first, then move things in. Editors will happily save into whatever folder they used last, so tell yours where your work lives once, and check the first time you save.
If you work on a shared or network drive at school, the same shape applies, with one addition: know which folder is yours and which is shared. Anything you can edit, somebody else may be able to edit too β and a shared folder is not a backup, because a file deleted there is deleted for everyone.
The test that this worked
Close everything, take a two-minute break, then find the program you wrote last Thursday in under ten seconds without searching. If you had to search, the names are wrong, not your memory.
Then read Backing Up Your Work β organised and backed up are different problems, and only one of them survives a lost laptop.
Curriculum connection
C2.1
use an operating system to organize computer programs and files logically on local and shared drives;
Link to original