Paths that make sense

You're here for Paths that make sense — absolute vs relative paths. I'll teach it the way you'd want a careful friend to teach: exact wording, walked examples, pitfalls named out loud, then checks that match this page.

You've already finished the introductory terminal track. I won't re-teach the absolute first hello. We build upward from habits you already own.

Absolute paths start from a root; relative paths start from the working directory. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

/home/you/notes.txt is absolute on Unix-shaped systems; ./notes.txt is relative to pwd. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Windows Terminal may host PowerShell (C:\ paths) or WSL (/mnt/c/...). Know which world your tab is in. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

./ means from here; .. means parent; . means current directory. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Spaces in paths need quotes or the shell splits arguments. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

When a path "vanishes," check pwd before blaming the filesystem. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Write the absolute form on paper once when a tutorial gets confusing, then shorten carefully. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Running ./prog vs prog can differ because PATH search skips . unless configured. Hold that under Paths that make sense: if you cannot explain it without looking, re-read before the quizzes. Change one misunderstanding at a time — calm corrections beat dramatic rereads of the whole page.

Put Paths that make sense in a sentence you could teach a friend: what changes, what stays the same, and what you expect from the still. Software rewards that sentence more than highlighting. If the sentence needs five caveats, tighten the model.

Open-book does not mean guess. The right answer about Paths that make sense is on this page in plain language. Wrong choices are usually near-misses that sound technical; pick the claim that matches what we actually traced.

If you are skimming, stop and re-read the still for Paths that make sense while pointing at each token. This is not a vocabulary flashcard — it is a behavior (or a verse's claim) you should be able to simulate aloud.

When an exercise asks you to match the still for Paths that make sense, match it honestly: same names, same structure, same intent. Clever shortcuts that skip the concept will leave a hole that the next lesson falls into.

Hold Paths that make sense as a behavior, not a vocabulary flashcard. Ask: what inputs matter, what action runs, what is visible afterward? If you cannot fill those three slots, you are skimming. Write them in a margin before the quizzes.

When something fails around Paths that make sense, change one thing. Read the error or the wrong output. Return to the still. Do not rewrite the whole example when one token is wrong. Calm retries beat dramatic rewrites.

Compare Paths that make sense with the nearest habit you already know — and name the difference out loud. Software's teaching value is often the delta: familiar idea, sharper tool.

Open-book checks for Paths that make sense reward careful reading of this page. The right answer is a claim we actually made. Near-miss choices sound technical; they fail because they invert the lesson.

Before the still, predict. After the still, compare. That predict-compare loop is how Paths that make sense becomes muscle memory. Passive rereading without prediction is how you forget by tomorrow.

Say a one-sentence teaching version of Paths that make sense you could give a friend. If the sentence needs five caveats, your mental model is still foggy — tighten it. Precision in speech precedes precision in practice.

As you continue, Paths that make sense will reappear inside larger workflows. Scripts wrap it. Branches choose it. Habits repeat it. Learning it cold now prevents cargo-cult pasting later.

Keep a scratch note for Paths that make sense: one worked example, one failure you fixed, one sentence of definition. That tiny notebook beats highlighting the same paragraph five times.

If you are tired, stop at the still for Paths that make sense and trace tokens with a finger. Rushing past tokens is how mysteries are born. Slow eyes make fast operators.

Wrong answers on Paths that make sense quizzes are teachers too. Read the explain line. Relate it back to the still. A corrected misconception sticks harder than a lucky first guess.

/home/you/notes.txt
./notes.txt

Walk the still for Paths that make sense top to bottom. Name each token. Predict the visible result. Then match the exercise honestly — same shape, same intent. Clever shortcuts that skip the concept leave a hole the next lesson falls into.

Pitfalls around Paths that make sense: rushing past the still; changing five things at once when one failed; memorizing slogans without the worked example; treating open-book as an excuse not to read. Return to the still. Change one thing. Retry.

That's Paths that make sense. When every quiz and exercise on this page is green, mark it passed. Next lesson when you're ready — not before the still feels obvious.