The day I stopped Googling "how to rename 50 files at once" and just learned the CLI

It started with a stupid problem. I had a folder with 60 screenshots named something like Screenshot 2024-03-14 at 10.32.11 AM.png, and I needed them all renamed to a clean img-001.png format before shipping assets to a client.

My first instinct? Google it. Find a Stack Overflow answer. Copy a bash one-liner. Paste it. Pray. It worked — but I had zero idea what it did.

That moment made me realize something uncomfortable: I'd been treating the terminal like a vending machine. Put in a query, get out a command, move on. I understood nothing about what was actually happening.

So I spent a weekend actually learning a handful of CLI tools — not to become a Unix wizard, just to stop feeling helpless every time I opened a terminal. It changed how I work in ways I didn't expect.

Here's the thing about CLI tools: they compose. Once you understand tools like find, xargs, grep, and awk at even a basic level, you can chain them together to solve problems that would otherwise require writing a whole script or installing a GUI app.

Want to find every .env file you accidentally committed?

git log --all --full-history -- "**/.env"

Want to count how many times a specific function is called across your whole codebase?

grep -r "fetchUser" ./src | wc -l

Want to bulk-replace a deprecated API call across 30 files?

find ./src -name "*.js" | xargs sed -i 's/oldMethod/newMethod/g'

None of these are magic. They're small tools doing one job well, piped together. That's the whole Unix philosophy — and once it clicks, it starts feeling like a superpower.

Beyond the built-in tools, the modern CLI ecosystem is genuinely exciting right now. Tools like fzf (fuzzy file finder), ripgrep (grep but fast), bat (cat but readable), and zoxide (smarter cd) are worth adding to your setup. They slot into your existing workflow without demanding you relearn anything.

The real shift isn't about memorizing commands. It's about developing intuition — knowing "this is a job for the terminal" versus "this needs a script" versus "this needs a proper tool." That judgment gets sharper the more you practice.

Start small. Next time you're about to reach for a GUI file manager or write a throwaway Python script for a file task — try the terminal first. Look up one new command. Understand what it does before running it.

You won't regret it. Except maybe the first time you run rm -rf in the wrong directory. But that's a lesson you only need once.