Urgent.News

What's breaking now, across thousands of outlets.

Tech

How to Learn the Linux Command Line (and Remember the Commands You Actually Need)

I used Linux servers for about two years before I could do anything on one without a browser tab open. Every task started the same way: search "how to find a file linux", copy the first find command on Stack Overflow, paste it, hope. I'd done that exact search maybe forty times. It never stuck, because I never had to think about it. What finally worked was boring. I picked a small set of…

The author struggled with using Linux servers and often resorted to searching for commands online before even attempting tasks. They learned that mastering a few essential commands was more effective than memorizing many. First, learn how to navigate the file system: use pwd to see your current location, ls -la to view hidden files and permissions, and cd to change directories.

The cd command is particularly useful for moving between directories. Next, practice tab completion to avoid manual typing of long paths. Learn to read files using cat, less, head, and tail commands, with less being the most versatile. Understand pipes (|) to chain commands together, as they enable complex operations with multiple small commands.

Grep is the most widely used command, with key flags like -i for case-insensitive search, -r for recursive searching, and -n for displaying line numbers. When permissions or process issues arise, commands like ls -l, chmod, and ps aux help identify the problem. Regular practice is crucial; use ten commands daily for a week to build muscle memory.

Apply these principles to real tasks, such as renaming or moving files using the terminal. Consistently review the commands you've encountered twice, as frequent use reinforces memory. Finally, consider tools like Recl to aid spaced repetition learning through videos, podcasts, or articles, helping you retain knowledge long-term.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Honest talk: motivation is unreliable, so I stopped depending on it

Some days I'm excited to code. Some days I'd rather scroll. If my output depended on mood, I'd ship very little. This post is about building a routine that works on both kinds of day.

  • Motivation fluctuates and routines are more reliable for productivity
  • Define smallest task night before to minimize decision-making
  • Count non-zero work days to emphasize consistency over intensity

CI/CD for Monorepos 2026: Build Only What Changed

TL;DR: A monorepo with naive CI rebuilds the world on every commit, so pipelines get slower exactly as the repo succeeds.

  • Naive CI rebuilds entire codebase on every commit, causing slowdown
  • Affected-only delivery detects changes, expands through dependency graph
  • Start with path filters in GitHub Actions, graduate to build tools like Nx

More from Saturday 31 October →