How to take notes

02Keep enough context

Start with the task: what you wanted to do. The environment describes where you tried it, such as the lesson page, program and device. Record the relevant version if you know it. A version identifies a particular release of a program; unknown is more useful than an invented number.

Next write the action and the result. Keep an error's exact words, because a summary such as it broke can hide the distinction between different failures. Later, when you learn commands, record what you typed beside what the computer returned.

A source is where your evidence came from, such as the worksheet card. A timestamp records when something happened and helps order repeated attempts. If the source supplies no time, write unknown. Notes should preserve missing information rather than silently fill it in.

03Mark the guess

In the example, File unavailable is the observation. A wrong filename is only one possible explanation. Comparing the two filenames could show whether that explanation fits. If they match, you need other evidence before deciding the cause.

Use separate lines for observation and inference. Write a next check that could support or weaken the inference. If a later check changes your mind, add the new evidence and explanation while keeping the original result.

select the worksheet link once

the page displays File unavailable

the link may use the wrong filename

compare the linked filename with the lesson's filename

04Fill a note from evidence

Now use a different invented attempt: a learner tries to open a text file. A filename identifies a file; here it is practice-notes.txt. A folder is a place for grouping files. The ending .txt commonly indicates plain text. You are describing this attempt from the record, not opening a file on your own device.

Encrypted means transformed so that reading the content requires the appropriate key. You will study it later. An error message alone does not establish that content is encrypted. You need evidence that supports the particular cause you propose. Credentials means information used to sign in, such as a password.

FICTIONAL ATTEMPT
Task: read the supplied file practice-notes.txt
Environment: personal laptop; text-viewing program
Program version: not recorded
Action: select Open, then choose practice-notes.txt
Result displayed: File not found
Learner's guess: the file might have moved to another folder
Credentials supplied: none
Time: not recorded

Task:
Source of this record:
Environment and known versions:
Time (or unknown):
Action:
Exact observation:
Inference (not yet tested):
Next check:
Permission and limits:
Sensitive information removed before sharing:

1. Copy the template into your notes. Fill the task, source, environment and action from the fictional attempt. Use unknown for the missing version and time.
2. Copy File not found into Exact observation. Put the moved-file idea under Inference, and keep its uncertainty visible.
3. Write a next check that gathers relevant evidence without changing access. For this case, ask the lab author which folder should contain the supplied file.
4. Review your note against the record. Another learner should be able to identify the attempted action and exact result. The note should not claim to know the cause or invent missing facts. Stop with the note; no searching or moving real files is needed.

05Protect the note

Before sharing a copy, remove passwords, private information and puzzle answers. A session token is a value a service can use to recognize a signed-in browser. Someone who obtains it may be able to misuse that access, so treat it as sensitive too.

Redaction means removing sensitive information or replacing it with a marker such as [password removed]. Keep the surrounding explanation so the note still makes sense. A screenshot, which is a picture of your screen, can include account names, other tabs and sensitive text in a web address. Review the whole picture before sharing it.

06Optional challenge

Allow about 5 extra minutes. Propose one piece of evidence that could weaken the moved-file guess without searching someone else's files. Explain how that evidence differs from repeating File not found. You can use a reply from the fictional lab author as the proposed source.

07Fresh cases for the checks

Use these fictional cases for the checks below. They have different inputs from the worked examples. Read them here or make notes; no installation or external service is needed.

Task: read lantern.txt from the supplied worksheet.
Environment: browser on a tablet; browser version unknown.
Action: select the lantern.txt link once.
Displayed result: Resource missing
Learner guess: the server is broken.
Worksheet names the file lanterns.txt.
No timestamp is supplied.
Private note also contains Password: [fictional-secret].

08Build the note

Optional written self-check: Write task, environment, action, exact observation, uncertain explanation and next check from case A. Keep the original record privately; remove sensitive values in a shareable copy. Your rubric is honest unknowns, a preserved exact result and a check that could change your explanation.