Linux Command Line Tips Every Developer Should Know

Why the Command Line Is Still Essential for Developers

In an era of polished graphical interfaces and browser-based developer tools, the Linux command line remains one of the most powerful environments a developer can master. It is faster for many tasks, endlessly scriptable, available on virtually every server you will ever deploy code to, and often the only interface available in production environments. Whether you are a web developer, a DevOps engineer, or a data scientist, building fluency with Linux terminal commands will pay dividends every single day.

This guide collects the most valuable Linux command line tips — from navigation fundamentals to power-user tricks — that professional developers rely on to work faster and smarter.

Master Navigation and File Management

Before anything else, move around the filesystem efficiently:

• cd - — Jump back to the previous directory. Invaluable when switching between two locations.
• pushd / popd — Maintain a directory stack. pushd /var/log saves your current location and moves you there; popd returns you.
• ls -lhA — Long listing with human-readable file sizes, including hidden files.
• tree -L 2 — Visualize a directory structure up to 2 levels deep. Install with apt install tree if not present.
• find . -name "*.log" -mtime -1 — Find all .log files modified in the last 24 hours.

Work Faster with History and Shortcuts

The bash shell has built-in productivity features most developers underuse:

• Ctrl+R: Reverse search through command history. Start typing and bash finds the most recent matching command.
• !! — Repeat the last command. Especially useful with sudo !! when you forget to prefix a command.
• !$ — The last argument of the previous command. If you ran mkdir /var/www/myapp, then cd !$ takes you there.
• Ctrl+A / Ctrl+E: Jump to the start or end of the current command line.
• Ctrl+W: Delete the word before the cursor.
• history | grep ssh — Search your command history for all SSH commands you have run.

Text Processing Power Tools

Linux ships with a suite of command line text processing tools that are far faster than writing custom scripts:

• grep -r "TODO" ./src --include="*.py" — Recursively find all TODO comments in Python files.
• grep -c "ERROR" app.log — Count lines containing ERROR in a log file.
• sed 's/foo/bar/g' file.txt — Replace every occurrence of “foo” with “bar” in a file.
• awk '{print $1, $3}' access.log — Print the first and third whitespace-delimited fields from each line.
• sort -k2 -n file.txt — Sort by the second field numerically.
• uniq -c | sort -rn — Count duplicate lines and sort by frequency — essential for log analysis.
• cut -d',' -f1,3 data.csv — Extract columns 1 and 3 from a CSV file.
• wc -l file.txt — Count lines in a file.

Process Management

Keeping track of what is running on your system is a core skill:

• ps aux | grep nginx — Find all processes related to nginx.
• top or htop — Real-time process monitor. htop is more user-friendly but may need installation.
• kill -9 PID — Force-kill a process by PID. Use kill PID (no -9) first for a graceful shutdown.
• lsof -i :8080 — List processes listening on port 8080. Essential for debugging “port already in use” errors.
• nohup command & — Run a command in the background, immune to hangups. Use disown to detach it from the shell.
• screen or tmux — Terminal multiplexers that keep sessions alive after you disconnect from SSH.

Networking on the Command Line

Diagnose and interact with networks directly from the terminal:

• curl -I https://example.com — Fetch only the HTTP response headers. Great for checking redirects and server software.
• curl -X POST -H "Content-Type: application/json" -d '{"key":"value"}' https://api.example.com — Send a POST request with a JSON body.
• wget -O output.html https://example.com — Download a URL to a specific file.
• netstat -tlnp or ss -tlnp — List all listening TCP ports and the processes using them.
• ping -c 4 8.8.8.8 — Send exactly 4 ICMP packets to test connectivity.
• traceroute google.com — Trace the network path to a host.
• dig example.com +short — Quick DNS lookup returning only the IP addresses.

File Permissions and Ownership

Understanding Linux file permissions is essential for secure server management:

• chmod 755 script.sh — Owner can read/write/execute; group and others can read/execute.
• chmod -R 644 /var/www/html — Recursively set files to 644 (read/write for owner, read-only for others).
• chown -R www-data:www-data /var/www/html — Recursively change owner and group to www-data (common for web servers).
• ls -la — Show permissions, owner, group, size, and modification time for all files including hidden ones.
• stat file.txt — Show detailed file metadata including access, modify, and change timestamps.

Disk Usage and System Health

Before a disk fills up and crashes your application, monitor it proactively:

• df -h — Show disk space usage for all mounted filesystems in human-readable units.
• du -sh /var/log/* — Show the size of each item inside /var/log.
• du -sh * | sort -rh | head -20 — Find the 20 largest files or directories in the current location.
• free -h — Show RAM and swap usage.
• uptime — Show system load averages for the last 1, 5, and 15 minutes.

SSH Productivity

Most developers spend significant time managing remote servers over SSH:

• Use ~/.ssh/config to define named host aliases with user, port, and key settings — then ssh myserver instead of remembering full connection strings.
• ssh-copy-id user@host — Install your public key on a remote host for passwordless login.
• ssh -L 8080:localhost:3000 user@remotehost — Forward a remote port to your local machine for secure access to web apps running on a server.
• scp file.txt user@host:/remote/path — Securely copy a file to a remote host.

Try our free developer utility tools — JSON formatter, Base64 encoder, regex tester, and more, all in one place.