← All posts

Command Line Basics Every CS Student Should Know (But Nobody Teaches)

You avoid the terminal and click through folders instead. That works until it suddenly does not. Here is your survival kit.

🚀 The Simple Version

The terminal is just a text-based way to do what you already do by clicking — open folders, move files, run programs. It's faster once you know maybe 10 commands, and a lot of real developer tools (Git, Docker, deployment) simply don't have a "click here" button.

The Survival Kit

  • pwd — where am I right now?
  • ls (or dir on Windows) — what's in this folder?
  • cd folder-name — go into a folder; cd .. — go back up one level
  • mkdir name — create a new folder
  • touch file.txt — create an empty file (Mac/Linux)
  • rm file.txt — delete a file (careful — there's no recycle bin)
  • clear — wipe the clutter off your screen

Reading an Error Instead of Fearing It

"command not found" almost always means one of two things: you typed it wrong, or the tool isn't installed / isn't on your system PATH. That's it. It's not mysterious — it's the terminal telling you exactly what's missing.

One Habit That Saves You Constantly

Press the Up arrow to reuse your last command instead of retyping it, and use Tab to auto-complete file and folder names. Together these cut your typing in half and eliminate typo-based errors.

Why This Actually Matters

Every Git command, every npm install, every deployment script you'll ever run lives in the terminal. Getting comfortable here isn't optional flavor — it's the same keyboard you'll be using for the rest of your career.