# Demonstration: The Same Word, Two Different Destinations

## OBSERVE

Starting from `/home/student`, run `cd project` — you land at `/home/student/project`.

## HYPOTHESIS

Now, from `/home/student/project`, what do you predict `cd project` will do this time?

## INSPECT

```
$ pwd
/home/student/project
$ cd project
bash: cd: project: No such file or directory
```

It fails — there's no `project` directory INSIDE `project` (unless you happened to create one).
The exact same relative path meant something completely different depending on where you stood.

## CHANGE

From `/home/student/project`, run `cd ../project` instead — this correctly goes back up one
level, then into `project` again, landing you right back where you started.

## VERIFY

`pwd` after each `cd` to confirm exactly where you ended up — this habit (verify your location
before assuming it) prevents a huge share of "why did my command run somewhere unexpected"
confusion later.

## Instructor Notes

**Demo goal:** Make "relative paths depend on where you are" concrete and slightly surprising,
rather than an abstract rule to memorize.

**Approximate timing:** 8 minutes live.

**Common mistake to watch for:** students assume a relative path always means the SAME thing
once they've used it once — reinforce that it's re-evaluated fresh every time, from wherever
they currently are.