Your Dev Journal needs a home, and this term will pile programs, plans, and half-finished drafts beside it. Where that work lives — and whether future-you can find any of it at the end of the course — comes down to habits that take about a week to build.
Local, cloud, or both
A local file lives on the storage inside your machine: fast, yours, and exactly as safe as the machine it lives on. A cloud file lives on someone else’s server and reaches you through the network: it survives a dropped laptop, follows you to any device, and slips out of reach when the wifi does. Most tools now quietly do both — a local copy that syncs upward — which is the best of the two, as long as you know which version you are looking at.
Version history and sharing
Cloud storage usually remembers old versions of a file, which turns “I ruined it” into “restore Tuesday’s copy” — find that menu before you need it. Sharing is the other superpower: send access, not attachments. One shared file stays one file; an emailed copy becomes five copies, four of them out of date within the hour.
Naming things for future-you
The person who benefits from good file habits is you at the end of the course, hunting for the quiz project at 11 p.m. Give that person a gift:
- One folder per course, one subfolder per project
- Names that say what the file is —
quiz-plan.md, notstuff - No
final-v2-FINAL-real— trust version history instead - Dates written
2026-08-11, so files sort themselves - Anything precious lives in two places before the due date
None of this is glamorous. All of it is the difference between opening The Remix Project with everything at hand and spending the first twenty minutes searching for your own work.
Curriculum connection
B2.1
use file management techniques, including those related to local and cloud storage, to organize, edit, and share files
Link to original