File Management

• File formats — how data is saved so applications can read it back, and why "compatible" formats matter.
• File & folder structures — how folders nest to organise data hierarchically, so it can be found quickly.
• Saving work & version control — saving regularly, and keeping numbered versions so you can go back in time.
• Naming files — meaningful names vs vague names, and why it actually matters.
• Locating stored files — using search tools (like Windows Search) to find files fast without digging through folders manually.

Think of a file format as the "language" a piece of software writes in when it saves your work. Microsoft Word doesn't just dump your essay onto the disk as plain text — it wraps it up with all the formatting, fonts, images, and structure info, using a specific set of rules. That set of rules is the file format, and it's what lets Word open the file again later and reconstruct exactly what you had.

The problem is: different programs speak different "languages." A spreadsheet program doesn't know how to read a database file, the same way a Spanish speaker can't just understand Japanese by looking at it. That's why it's good practice to save your work in a format that's compatible with the application you're using — and with whoever needs to open it next.

This is exactly why, when you install an old copy of Microsoft Office and try to open a document made in the newest version, you sometimes get an error — the older software was never taught the "new words" the newer format uses.

Sometimes you finish creating something in one application, but you need to share it in a completely different, more universal format. The classic example from the chapter:

This is a two-way street to understand: you save in the native format while you're still editing (so you keep all your editable layers, fonts, and tools), then you export to a generic format like PDF only once you're done and want to share or print it.