Read your location before running commands
See this course’s project requirements
A repeatable Bash workflow with checked registration counts, a controlled rerun and clear handoff instructions.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Location and path log.
- Raw-row count with header handling.
- Confirmed counts by session.
- Reviewed script and dedicated output path.
- Baseline/variation results and handoff.
Review and revise
Use these criteria to check your work and choose what to improve.
- Paths and quoting are accurate.
- Counts reconcile with the fixture.
- Raw data is preserved.
- Rerun and limitations are explained.
Want more background?
The idea in everyday life
Summarize fictional workshop registrations using Bash and a small tab-separated file.
A terminal runs a named program with arguments from a current location.
Read your location before running commands — guided practice
Identify the current directory and distinguish a command from its output.
Create an empty shell-lab folder. Inside it create input and output folders. Put registrations.tsv in input with these tab-separated rows and a final newline: session<TAB>status; art<TAB>confirmed; code<TAB>confirmed; art<TAB>waiting; code<TAB>confirmed; music<TAB>confirmed. Start the terminal in shell-lab. Bash required; no sudo, remote systems or deletion commands.
1. Inspect location
Run pwd and note only the final folder name.
pwdYou should see: The final component is shell-lab.
The same relative path means different things from different folders.
2. List names
Run ls and compare the two names.
lsYou should see: input and output are listed.
Listing is a read-only way to inspect before acting.
3. Inspect one folder
Run ls input.
ls inputYou should see: registrations.tsv is listed.
An argument tells ls which folder to inspect.
4. Record syntax
Write command=ls and argument=input in a note.
You should see: The note separates the tool name from its target.
This helps read unfamiliar command examples.
What to finish
A three-command location log.
Watch for this
Copying a displayed prompt such as $ as part of the command.
How can I tell I understand it?
Complete the changed case, explain your result, and pass the three application checks.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video
Lecture 1: Course Overview + The Shell (2020)
From Missing Semester. Watch here or open it on YouTube .
Optional course overview. Follow the written steps below at your own pace.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: Arguments, paths and input/output.
Access: Free public web page; no paid enrollment required.
Reuse: CC BY-NC-SA; link only.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: Working directory and relative paths.
Access: Free public web page; no paid enrollment required.
Reuse: CC BY 4.0 instruction; MIT examples. Independent fixture used.
Source & access notes · checked 2026-09-12
Metadata retrieved and inspected on 2026-09-12: exact title and channel confirmed through YouTube oEmbed. Playback and full video content were not tested. Optional overview; the written lesson and supplied practice stand alone.
Access: Free public web page; no paid enrollment required.
Reuse: Link or provider embed only; do not copy video, audio or transcript.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.