50+ Basic Linux Commands Every Developer Should Know

Why bother with the terminal at all?

Every developer eventually ends up staring at a blinking cursor in a black window, whether it's to install a package, check why a server won't start, or SSH into a machine that doesn't have a GUI at all. You can avoid the terminal for a while, but not forever. Deploying an app, setting up a dev environment, debugging a process that's hogging memory, none of that happens through a nice interface, it happens through commands.

The good news is that you don't need to memorize hundreds of flags to be productive. A working set of maybe 15 commands covers most of what you'll do day to day, and everything past that is stuff you look up when you actually need it, the same way you'd look up a library's API. This blog is split into two parts: the essentials you should genuinely know by heart, and a broader reference you can come back to whenever you need something specific.

Part 1: The Essentials Every Developer Should Know

These are the commands you'll type without thinking about it once they're second nature. If you only learn 15 things from this blog, make it these.

1. pwd - print working directory

Tells you exactly where you are in the file system right now. Useful the moment you feel lost after a few cd commands.

bash

2. ls - list files

Shows you what's inside the current folder. Add -l for a detailed list with permissions and sizes, and -a to also show hidden files (the ones starting with a dot).

bash

3. cd - change directory

Moves you into a different folder. cd .. goes up one level, cd ~ takes you home, and cd - jumps back to wherever you just were.

bash

4. mkdir - make directory

Creates a new folder. Add -p if you want to create nested folders in one go, even if the parent folders don't exist yet.

bash

5. touch - create an empty file

Creates a new, empty file instantly. Developers use this constantly to scaffold files before writing anything into them.

bash

6. rm - remove

Deletes a file. Add -r to delete a folder and everything inside it, and be careful, there's no trash bin here, it's gone.

bash

7. cp - copy

Copies a file or folder from one place to another. Add -r when copying folders.

bash

8. mv - move (and rename)

Moves a file, or renames it if the destination is in the same folder. There's no separate "rename" command in Linux, mv does both jobs.

bash

9. cat - print file contents

Dumps the entire contents of a file straight into your terminal. Great for short files, not great for anything hundreds of lines long.

bash

10. nano - a simple text editor

Opens a file for editing directly in the terminal. nano is the friendliest option for beginners, Ctrl + O saves, Ctrl + X exits.

bash

11. clear

Wipes your terminal screen so you're not scrolling through a wall of old output. Doesn't undo anything, it's purely visual.

bash

12. history

Shows you a list of every command you've typed recently in this shell. Genuinely useful when you know you ran the right command five minutes ago and can't remember what it was.

bash

13. man - manual pages

The built-in documentation for almost every command. If you're not sure what a flag does, this is where you check before guessing.

bash

14. sudo - run as administrator

Runs a command with elevated permissions. You'll need this for anything that touches system-level files or installs software system-wide. Use it deliberately, not by habit, since it can genuinely break things if misused.

bash

15. chmod - change permissions

Changes what a file is allowed to do, read, write, or execute, and for whom. You'll run into this the first time you try to run a shell script and get a "permission denied" error.

bash

[IMAGE: A simple cheatsheet-style graphic showing the 15 essential commands grouped visually, placed right after this essentials section, before the broader reference begins]

Part 2: The Broader Reference

Once the essentials feel automatic, these are the commands you'll reach for depending on what you're actually doing. You don't need to memorize this section, just know it exists so you know what to search for later.

Viewing and reading files

Searching and processing text

File permissions and ownership

[IMAGE: A visual breakdown of a "ls -l" output line, showing what each character in the permission string means (owner, group, others, read/write/execute), placed right after the permissions table above]

Process management

Networking

Disk and system info

Archiving and compression

Package management (Debian/Ubuntu based systems)

Shell operators worth knowing

These aren't standalone commands, but you'll use them constantly alongside everything above.

A quick example putting a few of these together

Say you want to find every error in a log file, count how many there are, and save the result to a new file. You don't need a script for this, one line does it:

bash

This pipes grep's output into wc -l to count the lines, then redirects that count into a new file. That's the actual power of the terminal, small commands that do one thing well, chained together to do something more specific. If you've set up a Node.js and Express server before, you'll recognize this exact workflow from tailing logs while debugging a route that keeps failing, something covered in more depth in Node.js and Express.js explained.

What to actually take away from this

You don't need to know all 50-plus of these by heart. Learn the first 15 properly, they'll cover almost everything you do on a normal day. Everything after that is a reference you come back to, the same way you'd look up a specific method in a library's docs instead of memorizing the whole thing upfront. The terminal stops being intimidating pretty fast once you realize it's just a small set of tools, used together, over and over again.