Start assessmentBinary TreeUseful learning, one step at a time
Online
Offline-ready notes · progress saves on this device
Project LibraryStudy workspace →
Courses/Digital Literacy/Lesson 3

Lesson 3 of 5

Files & File Management

Read the overview in
English overview

Recognize common image, document, video, archive, text, and table formats, then organize files so they remain findable, compatible, and safe to share.

10:42 lectureBeginner11 video chapters30 flashcards + 30 questions
Official Binary Tree uploadDigital Literacy Week 3Published 2026-08-06 · embedded with chapters, checkpoints, deep notes, and a project

Four clear stages

Learn → Project → Check → Finish

Watch and work through the lecture →
  1. 1LearnWatch and work through the lectureUse the chapter notebook and answer each video checkpoint.Do this now
  2. 2ProjectCreate a clean file-system handoffPlan it, create it, then prove it meets the definition of done.Next
  3. 3CheckAnswer all 30 questionsCorrect weak spots using the explanation after each answer.Next
  4. 4FinishMark the lesson completeThen move to Programming Fundamentals.Next
Course outlineDigital Literacy

Interactive lecture

Watch, pause, think, apply.

Choose and manage file formats deliberately, then express a small digital process with pseudocode, conditions, loops, and reproducible environment files.

0:003 thinking points marked10:42

Numbered markers show where the video will pause. Seeking past one opens the first unanswered check.

Connecting to the lecture…Open on YouTube ↗

Chapter-by-chapter lecture notebook

Everything in the video, organized for learning

The lecture connects file literacy with programming logic because reliable software depends on understandable inputs, environments, and steps.

Source reviewed10:42 lectureReviewed against the public lecture with timestamped slide sampling across the full runtime and cross-checked against the source lesson context.
11

video chapters mapped into notes, examples, and a concrete action.

This is a detailed learning companion reconstructed from the reviewed lecture—not a verbatim transcript.
01
0:00 in the lectureFiles and file handling
What the video is teaching

JPEG suits compressed photographs, PDF preserves document presentation, GIF supports limited-color animation, and ZIP bundles files. Format affects quality, editability, compatibility, size, and safety.

Check the actual file type, expected software, recipient needs, and whether an editable source must be preserved.

What to noticeWorked example

A poster team keeps an editable source file, exports an accessible PDF for distribution, and shares all approved assets in a named ZIP archive.

Do this before continuing

For five artifacts, choose a format and justify quality, compatibility, and editability.

Replay this chapter on YouTube ↗
02
0:50 in the lectureJPEG and PDF
What the video is teaching

JPEG suits compressed photographs, PDF preserves document presentation, GIF supports limited-color animation, and ZIP bundles files. Format affects quality, editability, compatibility, size, and safety.

Check the actual file type, expected software, recipient needs, and whether an editable source must be preserved.

What to noticeWorked example

A poster team keeps an editable source file, exports an accessible PDF for distribution, and shares all approved assets in a named ZIP archive.

Do this before continuing

For five artifacts, choose a format and justify quality, compatibility, and editability.

Replay this chapter on YouTube ↗
03
2:00 in the lectureGIF and ZIP
What the video is teaching

JPEG suits compressed photographs, PDF preserves document presentation, GIF supports limited-color animation, and ZIP bundles files. Format affects quality, editability, compatibility, size, and safety.

Check the actual file type, expected software, recipient needs, and whether an editable source must be preserved.

What to noticeWorked example

A poster team keeps an editable source file, exports an accessible PDF for distribution, and shares all approved assets in a named ZIP archive.

Do this before continuing

For five artifacts, choose a format and justify quality, compatibility, and editability.

Replay this chapter on YouTube ↗
04
3:00 in the lectureWhy file standards matter
What the video is teaching

Clear names, stable folders, backups, secure permissions, and version rules keep information usable across devices and people. Cloud storage is not automatically a backup or permission strategy.

Define one naming convention, one owner, one active location, and one tested recovery copy for important work.

What to noticeWorked example

workshop_budget_2026-08-09_v03.xlsx is stored in the finance folder; the approved export is read-only; recovery is tested monthly.

Do this before continuing

Reorganize a sample project and ask another person to find three files without help.

Replay this chapter on YouTube ↗
05
3:55 in the lectureNaming, folders, backups, and secure sharing
What the video is teaching

Clear names, stable folders, backups, secure permissions, and version rules keep information usable across devices and people. Cloud storage is not automatically a backup or permission strategy.

Define one naming convention, one owner, one active location, and one tested recovery copy for important work.

What to noticeWorked example

workshop_budget_2026-08-09_v03.xlsx is stored in the finance folder; the approved export is read-only; recovery is tested monthly.

Do this before continuing

Reorganize a sample project and ask another person to find three files without help.

Replay this chapter on YouTube ↗
06
5:10 in the lectureProgramming logic and pseudocode
What the video is teaching

Programming logic describes the ordered steps and branches a computer follows. Pseudocode and flowcharts reveal missing inputs, unclear conditions, and loops without syntax noise.

Break a large task into small named steps, state the input and output of each, and test the path for normal, boundary, and invalid cases.

What to noticeWorked example

A file sorter reads a filename, checks its extension, chooses a destination folder, moves the file, and records success or failure.

Do this before continuing

Write pseudocode for sorting five incoming files and include an unknown-extension branch.

Replay this chapter on YouTube ↗
07
6:05 in the lectureFlowcharts and problem decomposition
What the video is teaching

Programming logic describes the ordered steps and branches a computer follows. Pseudocode and flowcharts reveal missing inputs, unclear conditions, and loops without syntax noise.

Break a large task into small named steps, state the input and output of each, and test the path for normal, boundary, and invalid cases.

What to noticeWorked example

A file sorter reads a filename, checks its extension, chooses a destination folder, moves the file, and records success or failure.

Do this before continuing

Write pseudocode for sorting five incoming files and include an unknown-extension branch.

Replay this chapter on YouTube ↗
08
6:55 in the lectureConditionals, match, and loops
What the video is teaching

Conditionals choose among paths and loops repeat bounded work. requirements.txt, configuration files, and environment definitions help another machine recreate the software context.

Keep secrets out of shared configuration, pin important dependencies, document setup commands, and test from a clean environment.

What to noticeWorked example

A teammate creates a virtual environment, installs from requirements.txt, runs the same tests, and reports a missing system dependency.

Do this before continuing

Draft a minimal project handoff containing files, pseudocode, dependency list, setup step, and failure note.

Replay this chapter on YouTube ↗
09
8:05 in the lectureCode examples
What the video is teaching

Conditionals choose among paths and loops repeat bounded work. requirements.txt, configuration files, and environment definitions help another machine recreate the software context.

Keep secrets out of shared configuration, pin important dependencies, document setup commands, and test from a clean environment.

What to noticeWorked example

A teammate creates a virtual environment, installs from requirements.txt, runs the same tests, and reports a missing system dependency.

Do this before continuing

Draft a minimal project handoff containing files, pseudocode, dependency list, setup step, and failure note.

Replay this chapter on YouTube ↗
10
9:05 in the lectureVirtual environments and dependency files
What the video is teaching

Conditionals choose among paths and loops repeat bounded work. requirements.txt, configuration files, and environment definitions help another machine recreate the software context.

Keep secrets out of shared configuration, pin important dependencies, document setup commands, and test from a clean environment.

What to noticeWorked example

A teammate creates a virtual environment, installs from requirements.txt, runs the same tests, and reports a missing system dependency.

Do this before continuing

Draft a minimal project handoff containing files, pseudocode, dependency list, setup step, and failure note.

Replay this chapter on YouTube ↗
11
10:10 in the lectureAutomation and collaboration reflection
What the video is teaching

Conditionals choose among paths and loops repeat bounded work. requirements.txt, configuration files, and environment definitions help another machine recreate the software context.

Keep secrets out of shared configuration, pin important dependencies, document setup commands, and test from a clean environment.

What to noticeWorked example

A teammate creates a virtual environment, installs from requirements.txt, runs the same tests, and reports a missing system dependency.

Do this before continuing

Draft a minimal project handoff containing files, pseudocode, dependency list, setup step, and failure note.

Replay this chapter on YouTube ↗

Deep explanations

The ideas behind each chapter

Use these sections when the video moves quickly or you need another example.

010:00

Choose formats from purpose and tradeoffs

JPEG suits compressed photographs, PDF preserves document presentation, GIF supports limited-color animation, and ZIP bundles files. Format affects quality, editability, compatibility, size, and safety.

Check the actual file type, expected software, recipient needs, and whether an editable source must be preserved.

Worked example

A poster team keeps an editable source file, exports an accessible PDF for distribution, and shares all approved assets in a named ZIP archive.

Try it now

For five artifacts, choose a format and justify quality, compatibility, and editability.

023:00

Make files findable and recoverable

Clear names, stable folders, backups, secure permissions, and version rules keep information usable across devices and people. Cloud storage is not automatically a backup or permission strategy.

Define one naming convention, one owner, one active location, and one tested recovery copy for important work.

Worked example

workshop_budget_2026-08-09_v03.xlsx is stored in the finance folder; the approved export is read-only; recovery is tested monthly.

Try it now

Reorganize a sample project and ask another person to find three files without help.

035:10

Plan code as a sequence of decisions

Programming logic describes the ordered steps and branches a computer follows. Pseudocode and flowcharts reveal missing inputs, unclear conditions, and loops without syntax noise.

Break a large task into small named steps, state the input and output of each, and test the path for normal, boundary, and invalid cases.

Worked example

A file sorter reads a filename, checks its extension, chooses a destination folder, moves the file, and records success or failure.

Try it now

Write pseudocode for sorting five incoming files and include an unknown-extension branch.

046:55

Use environment files for reproducibility

Conditionals choose among paths and loops repeat bounded work. requirements.txt, configuration files, and environment definitions help another machine recreate the software context.

Keep secrets out of shared configuration, pin important dependencies, document setup commands, and test from a clean environment.

Worked example

A teammate creates a virtual environment, installs from requirements.txt, runs the same tests, and reports a missing system dependency.

Try it now

Draft a minimal project handoff containing files, pseudocode, dependency list, setup step, and failure note.

Language of the lesson

Know these ideas

File format
A defined structure for storing a kind of digital data.
Compression
Reducing data size through a reversible or lossy representation.
Naming convention
A repeatable system for understandable filenames.
Backup
A separate recoverable copy of important information.
Pseudocode
Language-neutral steps describing program logic.
Virtual environment
An isolated set of project dependencies and interpreter context.

Reason like a practitioner

Misconceptions to correct

  • Changing a filename extension converts the file.Real conversion requires software to rewrite the data in the target format.
  • Cloud storage means a file cannot be lost.Deletion, sync, permissions, and account loss still require recovery planning.
  • Pseudocode is wasted work once someone knows syntax.It exposes logic and communication problems before implementation details distract the team.
Transfer challenge

Package a small reproducible project with deliberate formats, a naming convention, secure sharing, recovery copy, pseudocode, dependency file, and an invalid-input path.

Lesson project · File organization

Create a clean file-system handoff

A folder hierarchy, repeatable naming convention, format decisions, compression choice, and recovery explanation.

0%0 of 3 checks
1
Project phase 1

Plan the work

State the goal, audience or user, and the evidence a strong result needs. Explain how File format changes your plan.

2
Project phase 2

Create the deliverable

Sort a mixed sample folder into a clear hierarchy. Rename each file with a useful pattern, identify which can be compressed, and choose the safest format for sharing a final report.

3
Project phase 3

Prove and improve

Use Compression and Folder hierarchy to check the result. Record one piece of evidence, one correction, and one improvement you would make next.

Offline referenceRead the independent walkthrough and practice notes

Why this lesson matters

Recognize common image, document, video, archive, text, and table formats, then organize files so they remain findable, compatible, and safe to share.

The goal is not to memorize vocabulary. By the end of the lesson, you should be able to use the ideas in a realistic situation, explain the reason for your choices, and check whether the result actually works for the intended person or task.

Learning objectives

  • Explain File format in your own words.
  • Apply Compression to a realistic classroom or community example.
  • Connect File format with Folder hierarchy when making a decision.
  • Complete the practice task and reflect on one improvement.

Core ideas

1. File format

The structure used to store information, indicated by an extension such as PNG, PDF, MP4, ZIP, CSV, or TXT.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how File format changes what you choose, create, or check.

2. Compression

Reducing file size or packaging several files together to save storage and make transfer easier, sometimes with a quality tradeoff.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Compression changes what you choose, create, or check.

3. Folder hierarchy

A logical arrangement of parent and child folders that groups related work and prevents files from becoming difficult to find.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Folder hierarchy changes what you choose, create, or check.

How the ideas connect

Start with File format to understand the foundation of the lesson. Use Compression to turn that understanding into an action. Then apply Folder hierarchy to check the quality, safety, or usefulness of the result. The three ideas are strongest when you can explain their relationship rather than treating them as separate definitions.

Guided walkthrough

  1. Name the goal. In one sentence, write what you are trying to understand, create, or improve.
  2. Make a prediction. Before touching a device, use File format and Compression to predict what a strong result should look like.
  3. Complete the task. Sort a mixed sample folder into a clear hierarchy. Rename each file with a useful pattern, identify which can be compressed, and choose the safest format for sharing a final report.
  4. Check the outcome. Use Folder hierarchy to inspect the result. Ask what worked, what did not, and what evidence supports your judgment.
  5. Explain and revise. Tell a partner what you changed and why. Make one small improvement, then compare the new result with the first one.

Worked classroom scenario

Imagine two learners sharing one device. The first learner is the driver and performs the steps; the second is the navigator and reads the goal, predicts the next step, and checks the result. Halfway through the task, switch roles. Both learners should be able to explain how File format, Compression, and Folder hierarchy appeared in the work.

If no device is available, complete the same reasoning on paper: sketch the screen or result, label each decision, and describe what you would test when a device becomes available.

Common mistakes and fixes

  • Rushing into the tool: Write the goal and prediction first so every click or step has a reason.
  • Copying without understanding: After each major step, explain it in your own words to a partner.
  • Accepting the first result: Compare the outcome with the goal and make at least one deliberate improvement.
  • Letting one person control a shared device: Rotate driver and navigator roles so both learners think and practice.

Independent practice

Sort a mixed sample folder into a clear hierarchy. Rename each file with a useful pattern, identify which can be compressed, and choose the safest format for sharing a final report.

For an extra challenge, adapt the task for a different audience or community need. Write two sentences explaining what changed and which lesson idea guided your decision.

Check your understanding

  1. How would you explain File format to someone new to the topic?
  2. What is one realistic example of Compression outside this classroom?
  3. When might Folder hierarchy prevent a weak, unsafe, or confusing result?
  4. How are File format and Compression connected?
  5. What evidence would convince you that your practice result works?
  6. If you repeated the activity tomorrow, what would you improve first and why?

Key takeaway

Recognize common image, document, video, archive, text, and table formats, then organize files so they remain findable, compatible, and safe to share.

You are ready to move on when you can explain the three core ideas, complete the practice without copying, and describe one improvement using evidence from your result.

Open lecture on YouTube ↗Open lecture deck ↗Study in focused mode