Pathmaker
Command Line Fundamentals
A hands-on class teaching students to navigate, manage files, and run programs using the terminal—building the foundation for development, scripting, and system administration.
About This Course
The command line is the interface that professionals use to control computers directly—without menus or mouse clicks. This class teaches students to navigate the file system, manage files and directories, run programs, pipe commands together, and write simple scripts.
No prior experience required. By the end, students can use the terminal confidently for everyday tasks and have the foundation to go much further.
What You'll Learn
- 1Navigate the file system using the command line
- 2Create, move, copy, and delete files and directories
- 3Read and edit files directly from the terminal
- 4Pipe commands together to process data
- 5Write a simple shell script to automate a repetitive task
- 6Understand how the PATH works and how to install command-line tools
Week by Week
Orientation: The Terminal Environment
The terminal is not difficult—it is just unfamiliar. This week removes the intimidation by giving students a clear mental model: the terminal is a text-based way to give instructions to your computer.
Every command follows a pattern, and the file system is the same one you already use with a GUI.
Explore this week's curriculum
Key concepts
Terminal / Shell: A program that takes text commands and passes them to the operating system. Bash and Zsh are the most common shells.
Command: An instruction typed at the prompt. Usually a program name followed by options and arguments.
Working Directory: The directory you are currently 'in' when using the terminal. Commands run relative to this location.
Prompt: The text the shell displays to indicate it is ready for input. Often shows your username, machine name, and current directory.
Studio activities
First Commands
Open a terminal and complete a structured series of first commands. Document every command you ran and what it produced.
- Open Terminal (Mac/Linux) or Git Bash / WSL (Windows)
- Type 'pwd' and note where you are
- Type 'ls' and read the output
- Type 'cd Desktop' (or another folder you know exists) and then 'ls' again
- Type 'echo Hello, terminal' and observe the output
- Type 'date' and see the current date and time
- Document all 6 commands with the output each produced
Success criteria
A documented log of all 6 commands with their output and a sentence explaining what each command does
Reflection
- What was more intuitive than you expected? What was confusing?
- How is the terminal's view of your file system different from a GUI file browser?
Study guidance
- The tab key autocompletes filenames and commands—use it constantly to avoid typos
- The up arrow scrolls through previous commands—you rarely need to retype
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
Why would you want to use the terminal when a GUI does the same thing?
What is the working directory, and why does it matter for commands?
What does the shell actually do with a command you type?
What was more intuitive than you expected? What was confusing?
How is the terminal's view of your file system different from a GUI file browser?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Navigating and Managing Files
The core of terminal use is navigating the file system and managing files. This week covers the essential commands for moving around directories, creating and deleting files, and understanding paths—both absolute and relative.
Explore this week's curriculum
Key concepts
Absolute Path: A file path starting from the root of the file system. Always works regardless of where you are. Example: /Users/alex/Documents/notes.txt
Relative Path: A file path relative to the current directory. Shorter but context-dependent. Example: ../Documents/notes.txt
Hidden Files: Files beginning with a dot (.) that are hidden by default. Viewable with 'ls -a'. Often used for configuration.
Wildcard: Characters used to match multiple files. * matches anything. Example: '*.txt' matches all text files.
Studio activities
File System Challenge
Complete a structured series of file management tasks using only the terminal. No GUI allowed.
- Create a directory called 'practice' in your home directory
- Inside it, create three subdirectories: 'notes', 'scripts', 'archive'
- Create a file called 'readme.txt' in 'practice' using the touch command
- Write a line of text to it using echo and redirection (echo 'hello' > readme.txt)
- Copy readme.txt into the 'notes' folder
- Move the copy to 'archive'
- Delete the original from 'practice'
- Verify the result using ls in each directory
Success criteria
All tasks completed with a documented log of every command used and the final state of the directory structure
Reflection
- When would using wildcards save significant time?
- Why is 'rm' more dangerous in the terminal than deleting in a GUI?
Study guidance
- Use 'ls -la' to see all files including hidden ones with detailed permissions
- When in doubt about where you are, type 'pwd'—it always tells you
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What is the difference between an absolute path and a relative path, and when would you use each?
What happens when you run 'rm' on a file? Is there an undo?
How would you move all .txt files in a directory to a subdirectory using wildcards?
When would using wildcards save significant time?
Why is 'rm' more dangerous in the terminal than deleting in a GUI?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Reading, Editing, and Searching Files
Much of what you do in the terminal involves reading and searching through file content. This week covers commands for reading files, searching their contents, and making basic edits—without leaving the terminal.
Explore this week's curriculum
Key concepts
cat / less / head / tail: Commands for reading file contents: cat prints all, less lets you scroll, head shows the beginning, tail shows the end.
grep: A powerful search command that finds lines in a file matching a pattern. One of the most used terminal tools.
stdin / stdout / stderr: Standard streams: stdin is input, stdout is normal output, stderr is error output. All can be redirected.
Redirection: Sending output to a file instead of the screen using > (overwrite) or >> (append).
Studio activities
grep and Redirection Drills
Use grep, cat, head, tail, and redirection to complete a series of file reading and searching tasks. Document every command and result.
- Create a text file with 20 lines of mixed content using echo and >>
- Use cat to print the whole file
- Use head -5 and tail -5 to show the first and last 5 lines
- Use grep to find a specific word you included in the file
- Use grep -c to count how many lines contain the word
- Redirect grep output to a new file
- Use cat on the new file to confirm it worked
Success criteria
All tasks completed with a documented command log and output for each step
Reflection
- How would grep change the way you approach searching through large text files?
- What is a situation where redirecting output to a file would be more useful than printing to the screen?
Study guidance
- grep -r 'searchterm' . searches recursively in all files in the current directory—extremely useful
- Pipe grep with other commands: 'cat file.txt | grep 'error'' filters output in place
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
When would you use 'tail -f' on a log file and why?
How would you find all lines containing the word 'error' across 50 log files?
What is the difference between redirecting stdout to a file and appending to it?
How would grep change the way you approach searching through large text files?
What is a situation where redirecting output to a file would be more useful than printing to the screen?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Pipes, Filters, and Combining Commands
The terminal's real power comes from combining commands. Pipes let you pass the output of one command directly to another—chaining tools into workflows.
This week teaches students to think in pipelines and combine small commands into powerful operations.
Explore this week's curriculum
Key concepts
Pipe ( | ): Passes the output of one command as the input to the next. The core mechanism for combining tools.
sort: Sorts lines of text alphabetically or numerically.
uniq: Removes duplicate adjacent lines. Often used after sort to deduplicate.
wc: Counts words, lines, or characters in a file or stream. 'wc -l' counts lines.
Studio activities
Pipeline Challenges
Complete a series of pipeline challenges that combine multiple commands to produce a specific output. Document each pipeline and explain what each stage does.
- Challenge 1: Count the total number of lines in three text files combined
- Challenge 2: Find all unique words in a file, sorted alphabetically
- Challenge 3: Find the 5 most common words in a text file
- Challenge 4: List all .txt files in a directory, sort them by name, and count how many there are
- For each challenge, document the full pipeline command and explain each stage with a pipe
Success criteria
All four pipeline challenges completed with full command documented and each stage of each pipeline explained
Reflection
- How does thinking in pipelines change the way you approach a data task?
- What is a real task you could now automate with a pipeline that you couldn't before?
Study guidance
- Build pipelines incrementally: run the first command, check output, then add the pipe and next command
- Most terminal tools are designed to work in pipelines—small, single-purpose, composable
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
How would you count the number of unique words in a large text file using only terminal commands?
What is the Unix philosophy of 'do one thing well,' and how does it relate to pipes?
What is the advantage of using a pipeline over writing a custom script for a simple task?
How does thinking in pipelines change the way you approach a data task?
What is a real task you could now automate with a pipeline that you couldn't before?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Shell Scripts and Automation
Any sequence of terminal commands you run more than twice should probably be a script. This week teaches students to write their first shell scripts—saving commands to a file and running them automatically—so the terminal becomes a tool for automation, not just manual execution.
Explore this week's curriculum
Key concepts
Shell Script: A file containing a sequence of terminal commands that can be run as a program.
Shebang ( #!/bin/bash ): The first line of a shell script that tells the OS which interpreter to use to run it.
Variables: Named storage in a script. Defined as NAME='value' and accessed as $NAME.
chmod +x: Makes a script file executable so the OS will run it as a program.
Studio activities
Your First Shell Script
Write a shell script that automates a real task. It must accept at least one input, perform at least three operations, and produce meaningful output.
- Choose a real task: backup a folder, organize files by extension, generate a report from log files, etc.
- Write each command you'd run manually in sequence
- Create a new file called task.sh and add #!/bin/bash as the first line
- Add your commands, using at least one variable
- Run chmod +x task.sh to make it executable
- Run ./task.sh and test that it works
- Write a README.txt explaining what the script does and how to use it
Success criteria
A working shell script with at least one variable, three operations, and a README explaining its purpose and usage
Reflection
- What changed in how you think about computers after learning to script?
- What would you build or automate next if you kept going with shell scripting?
Study guidance
- Start every script with #!/bin/bash and set -e (which exits on error)—it saves debugging time
- Write scripts incrementally: test each command before adding the next
Discuss with Professor Reed
Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.
What repetitive task in your life could you automate with a shell script?
What does 'making a file executable' actually do at the OS level?
How would you pass an argument to a shell script so it can work on different inputs?
What changed in how you think about computers after learning to script?
What would you build or automate next if you kept going with shell scripting?
Ask me one question at a time to check my understanding, then explain any gaps.
Help me plan this assignment without doing the work for me.
Topics Covered
More in This Track
Designing for Delegated Experiences
Design how people entrust decisions and actions to people, services, and agents.
Algorithms and the Online Experience
Investigate how ranking, recommendation, advertising, and moderation mediate everyday online life.
Design, Technology, and AI Systems
How designers can understand AI products, software ecosystems, automation, interfaces, and workflow tools — without becoming purely technical.
Ready to begin?
Start your personalized curriculum today — free to try, no credit card needed.