Vibeleaderboard
← Course overviewModule 02 · Understand the software underneath · Beta
Lesson 2.1

Module contents

Understand the software underneath

Lesson 1 of 6

Where does the garden note live?

Module 1 treated the garden note as data that you pasted into a chat. On a computer that note is stored as a file, and an application that can search your documents finds it as a file. This lesson explains what a file is, what a folder is, and what the recorded information about a file does and does not tell you.

Numbered links identify sources. Underlined terms offer a definition without leaving the lesson.

A file is stored data with a name and a location

In the first module, software was a set of instructions a computer carries out, and data was the information software works with. Both have to be kept somewhere while no program is using them. A is a named unit of stored data. The garden note from module 1, saved on a computer, is a file: its contents are the sentences about Saturday, and its name is whatever the person who saved it chose, such as saturday-session.txt.

A file's name and its contents are separate things. The name is a label that a person or a program attached. Nothing forces the label to match what is inside. A file named old-notice.txt can contain the newest notice, and a file named photo.jpg can contain text. A program that lists the names in a folder is reading labels, not contents. To know what a file contains, something has to open it and read it. Keep this distinction, because later modules ask you to judge whether a search found what you asked for.

A , also called a directory, is a named container that holds files and other folders. Folders nest, so a location can be described by the chain of folders leading to a file. That description is a . The path Documents/Garden/saturday-session.txt says: inside the folder Documents, inside the folder Garden, the file saturday-session.txt. Paths are how programs are told where to look. A path can also be written relative to a starting point: Garden/saturday-session.txt identifies a file only if you know which folder you are starting from. Programs can keep such a starting folder, called the working directory, and the same relative path names different files from different starting points. 1

The file table this module uses

Here is the authored example the rest of this module returns to. Imagine a folder named Garden on the organizer's computer. On 11 September 2026 it contains five files. The table lists what a file-listing program could show, plus a column the ordinary listing does not supply: the history the author of this example is supplying so that you can check your reasoning against it.

File name
saturday-session.txt
Created
2 Sep 2026
Last modified
9 Sep 2026
History supplied for this example
The note from module 1. Written on 2 September; the meeting time was corrected on 9 September.
File name
volunteer-rota.txt
Created
14 Mar 2026
Last modified
8 Sep 2026
History supplied for this example
A list maintained since March. One name was added on 8 September.
File name
funding-letter-draft.txt
Created
4 Sep 2026
Last modified
4 Sep 2026
History supplied for this example
A new draft, started and last touched on 4 September.
File name
compost-guide.txt
Created
10 Sep 2026
Last modified
10 Sep 2026
History supplied for this example
Copied on 10 September from a neighbor's memory stick. The neighbor wrote it in 2024. On this computer the copy produced a new file, and both recorded dates are the copy date.
File name
plot-map.png
Created
2 Jul 2026
Last modified
2 Jul 2026
History supplied for this example
A picture of the plots. Untouched since July.

Everything in this table is invented. No file-listing program produced it, and the dates were chosen to make the next section's point. The compost guide's copy behavior is stated as part of the example because different systems and copying methods record different dates for a copied file, and this lesson makes no claim about what your own computer would record. 3

Timestamps record events, not intentions

A file usually carries information about itself in addition to its contents. That information is : data about the file rather than the file's own content. The name, the size and the timestamps in the table are metadata. Timestamps are records of particular events that the storage system noticed. Microsoft's documentation for its file systems, for example, distinguishes a creation time, a last-access time and a last-write time, each recording a different event. It also notes that which of these are available and how precisely they are kept depends on the file system, and that software can change a timestamp without changing the file's contents. Other systems keep different sets. The useful point is general: each timestamp is tied to one recorded event, and none is tied to the question you happen to be asking. 3

Now ask the table a question a garden organizer might actually ask: which documents were started this month? Three readings give three different answers. Sort by last modified and take September, and you get the Saturday note, the rota, the funding draft and the compost guide. That list includes the rota, which was started in March and only had a name added. Sort by created and take September, and you get the Saturday note, the funding draft and the compost guide. That list includes the compost guide, whose recorded creation date is the day it was copied, although the writing began two years earlier. Use the supplied history, and only the Saturday note and the funding draft were started this month. Neither timestamp answers the question by itself. Last modified records the most recent write. Created records when this file appeared on this storage, which may have been a copy. When the writing started is a question about a person's activity, and the file system did not record that event.

This is why a request has to be translated into an operation, and why the translation can be wrong while every step of it works. A program asked for files started this month cannot read intentions. Someone, or some software, chooses a timestamp to stand in for started, and that choice decides which files appear. When you review a result, ask which recorded event was used and whether it is the event you meant.

A practitioner's version of the same mismatch

In January 2026, Simon Willison, a software developer who writes about tools he tries, asked Claude Cowork to find recently started drafts and check whether he had published them on his own website. Cowork is Anthropic's application for carrying out computer tasks with a model. Its displayed command selected files by modification time, which does not establish when writing began. 10

The search of his website was explicitly what he requested. He noted that one suggested draft was already published elsewhere. That illustrates a limit of the search's scope, rather than a failure to follow his instruction. It could answer whether the draft was found on that site; it could not establish that the draft was unpublished everywhere.

This is one reported experience from January 2026. Our inference concerns the gap between a question and the operation used to answer it. It is not a measurement of the product's current reliability. The garden table is a separate authored example.

Carry this forward

  • A file is stored data with a name and a path. The name is a label; only reading the contents shows what is inside.
  • Metadata such as timestamps records events the storage system noticed. Which timestamps exist and how precise they are depends on the system, and software can change them.
  • Last modified and created answer different questions, and neither answers when the writing started. Ask which recorded event stood in for your request.
  • Willison's report illustrates two different limits: modification time does not establish when writing started, and a search of one specified site does not cover publication elsewhere.

Lesson check

Using this module's authored table, an application is asked to list the garden documents that were started in September 2026 and answers with every file whose last-modified date is in September. What is the best description of that result?

Choose an answer for each question.

This is a practice check. Answers reset when you leave this page. Results are not saved and do not place you in another module or award a qualification.

The files are found. Now something has to open one. The next lesson explains what is running when that happens, and why closing a window is not the same as stopping the work.

Sources · Reviewed 2026-09-28
  1. 1. Missing Semester (MIT): Course overview and introduction to the shell
  2. 3. Microsoft: File times
  3. 10. Simon Willison (12 January 2026): First impressions of Claude Cowork

Sources support nearby explanations. Product details can change. Scenarios and model results are authored illustrations unless a lesson explicitly identifies a recorded execution. Module 7 identifies its offline code checks.