In partnership with

The voice-to-text app that built its own speech model

Most dictation apps are a wrapper around someone else's speech model. Wispr Flow trained its own.

It's called Canto, and it was built for the way people actually talk to AI: thinking out loud, changing direction mid-sentence, half-whispering in an open office.

Wispr tested it on 10 hours of real dictations from more than 2,300 speakers. Canto had the lowest word error rate of every model tested, including models from Google, OpenAI, AssemblyAI and Deepgram. That means your prompts to ChatGPT, Claude and Cursor come through the way you said them.

Talk naturally in any app and Wispr Flow types clean, formatted text, 4x faster than typing.

Most of us learned Linux the same way: ls, cd, grep, cat, repeat. That works, and you should know those commands cold.

Then one day you watch someone jump across five folders with one word, or find a file by typing half its name, and you realize the terminal you started with is the basic version.

This week is a break from firewall logs and failed SSH attempts. No hardening, no audits. Just 10 tools that make the Linux terminal faster, easier, or more fun, with something you can try for each one in a couple of minutes.

A few notes before you start:

  • Every tool here is free, open source, and actively maintained as of this week.

  • Install commands are for Ubuntu. Where Ubuntu's package is old or missing, I'll say so and point you to the official instructions.

  • Several tools add a line to ~/.bashrc. Make a copy first so you can undo anything: cp ~/.bashrc ~/.bashrc.bak

1. fzf: find anything by typing part of its name

What it improves: scrolling through ls output, or running history | grep and hoping.

Why it feels like a cheat code: fzf is a fuzzy finder. Give it any list, start typing a few letters from what you want, and the list narrows as you type. You don't need the exact name, just enough of it.

Try it:

find . -type f | fzf

Pick a file and press Enter, and fzf prints its path. The real fun starts once the shell keys are set up: Ctrl+R searches your command history, Ctrl+T drops a file path onto the line you're typing, and Alt+C jumps into a directory.

It's not a replacement for find or grep. It's what you put in front of a long list when you only half remember what you're looking for.

Install:

sudo apt install fzf

To turn on the keys, newer versions (including Ubuntu 26.04's) use this line in ~/.bashrc:

eval "$(fzf --bash)"

Ubuntu 24.04 ships an older fzf that doesn't have that option. On 24.04, add this line instead:

source /usr/share/doc/fzf/examples/key-bindings.bash

Then open a new terminal.

2. zoxide: cd, but it remembers where you go

What it improves: typing cd ~/projects/securebydefault/labs/issue-015/screenshots for the tenth time this week.

Why it feels like a cheat code: zoxide learns which directories you use. After that, one word is enough:

z screenshots
z labs 015

The first jumps to the best match for "screenshots." The second needs both words to match, which helps when you have several similar folders. z .. goes up a level, like cd ...

Try it: install it, use your terminal normally for a day so zoxide sees where you go, then try jumping somewhere with one word.

Install:

sudo apt install zoxide

Then add this to the end of ~/.bashrc and open a new terminal:

eval "$(zoxide init bash)"

The project notes that Ubuntu's packages lag behind its releases and offers an install script, but the Ubuntu package is fine for trying it. One catch: zoxide's interactive picker (zi) needs a newer fzf than Ubuntu 24.04 ships. On 24.04, z works; zi may not.

3. Yazi: a full file manager inside the terminal

What it improves: ls, cd, cp, and mv, one command at a time.

Why it feels like a cheat code: run yazi and the terminal turns into a file manager. You move with the arrow keys (or h, j, k, l), and the right side shows a live preview of whatever you're on. Text and code show with highlighting. In supported terminals, images preview right there too.

The basics:

  • Enter opens a file

  • Space selects files

  • y copies ("yanks"), x cuts, p pastes

  • d moves to the trash

  • . shows hidden files

  • q quits, and F1 or ~ shows every shortcut

Try it: open it in a folder with a mix of files and press the keys above.

Previews depend on your setup. Image previews need a terminal that supports them (kitty, WezTerm, Konsole, Ghostty, and recent Windows Terminal are on the project's list), and some previews need extra tools, like ffmpeg for video thumbnails or poppler for PDFs.

Install: Yazi isn't in Ubuntu's own repositories. The project offers an official APT repository for Debian and Ubuntu, and a Snap:

sudo snap install yazi --classic

Both options are on the official installation page.

The docs also have a small shell function, y, that leaves you in whatever folder you were browsing when you quit. It's worth adding once you like it.

4. btop: a dashboard instead of a wall of numbers

What it improves: staring at top and trying to work out what matters.

Why it feels like a cheat code: btop shows CPU per core, memory, disks, network, and processes as live graphs in one screen. You can click things, sort the process list, and filter it.

When someone says "the server is slow," this is a good first look. In ten seconds you can usually see whether it's CPU, memory, disk, or network, and which process is responsible. It won't replace real performance analysis, but it tells you where to start.

Try it:

btop

Press q to quit.

Install:

sudo apt install btop

5. bat: cat, but readable

What it improves: cat, which dumps raw text, and less, which you then need for anything long.

Why it feels like a cheat code: bat shows files with syntax highlighting, line numbers, and, inside a Git repo, markers for lines you've changed. Long files open in a pager automatically.

Try it (on Ubuntu the command is batcat, more on that below):

batcat /etc/ssh/sshd_config

That's the SSH config from #012, now with color and line numbers. Comments fade back, so the settings stand out.

Install:

sudo apt install bat

On Ubuntu, the command is batcat instead of bat because another package already uses the name. If you want to type bat, add an alias to ~/.bashrc:

alias bat="batcat"

6. eza: ls with color, Git status, and trees

What it improves: ls -la.

Why it feels like a cheat code: eza colors files by type, shows sizes in readable units by default, and can show each file's Git status right in the listing. It also has a tree view built in.

Try it:

eza -la --git
eza --tree --level=2

The first shows a long listing with a Git column. The second draws the folder as a tree, two levels deep. Add --icons if your terminal uses a Nerd Font.

One gotcha if your fingers type ls -lah: in eza, -h adds a header row. It doesn't mean "human-readable," because eza's sizes already are.

Don't alias ls to eza on day one. Use it side by side for a while and see if you keep reaching for it.

Install:

sudo apt install eza

Ubuntu's package is behind the latest release. The project also runs its own APT repository if you want the newest version.

7. ripgrep: search a whole folder tree almost instantly

What it improves: grep -R, which also searches .git folders, build output, and binary files you didn't mean to search.

Why it feels like a cheat code: rg searches recursively by default, shows file names and line numbers in color, and skips the noise. It respects your .gitignore and skips hidden and binary files unless you ask for them.

Try it:

rg "TODO" ~/projects
rg -i "permitrootlogin" /etc/ssh/sshd_config

The first searches a whole project folder. The second searches the SSH config, ignoring case. If you need hidden files too, add --hidden.

Searching a directory tree just stops being a chore.

Install:

sudo apt install ripgrep

The command is rg.

8. tldr: man pages for when you're in a hurry

What it improves: opening man tar when all you need is "how do I extract this?"

Why it feels like a cheat code: man pages are complete and authoritative, and you should keep using them. But sometimes you already know the command exists and just want a reminder of how people usually use it. tldr gives you the handful of common examples, and that's all.

Try it:

man tar
tldr tar

Same command, very different experience. Use tldr for "remind me," and man when you need the details.

Install: the tldr project lists a few official clients. On Ubuntu, the easiest is the official Python client:

sudo apt install pipx
pipx ensurepath
pipx install tldr

Open a new terminal, then try tldr tar.

You may also see tealdeer, a popular Rust client. On Ubuntu 26.04, sudo apt install tealdeer works (run tldr --update once to download the pages). Avoid Ubuntu 24.04's tealdeer package, though: it's too old to download pages since the tldr project changed where it hosts them.

9. lazygit: see what Git is actually doing

What it improves: running git status, git add, git diff, and git log over and over to build a picture in your head.

Why it feels like a cheat code: lazygit puts that picture on screen. Changed files, staged files, branches, commits, and the diff of whatever you select, all visible at once.

Try it: in any Git repository, run:

lazygit

Then:

  • Space stages or unstages the selected file

  • c commits staged changes

  • P pushes and p pulls

  • ? shows every keybinding

  • q quits

One honest note: learn what Git is doing first (add, commit, push, branch). lazygit doesn't replace that. It just makes the workflow less annoying once you understand it, which is handy if you're documenting your labs on GitHub.

Install: on Ubuntu 25.10 and newer, including 26.04:

sudo apt install lazygit

Ubuntu 24.04 doesn't have a package. Use the official instructions, which download the release from GitHub.

10. Atuin: your shell history, searchable

What it improves: bash's Ctrl+R, which shows you one match at a time and hopes you recognize it.

Why it feels like a cheat code: your shell history probably knows more than you think. Atuin stores it in a small local database along with where you ran each command, whether it worked, and how long it took. Press Ctrl+R and you get a full-screen search of all of it.

You can filter, too. For example, only commands that worked:

atuin search --exit 0 docker

Or only commands you ran in the current folder:

atuin search --cwd .

A privacy note, because this is a security newsletter. Shell history can hold things you'd rather not keep: a token pasted into a command, a password typed in the wrong place. Atuin tries to filter out common secrets and lets you exclude patterns, but the best habit is still to keep secrets out of commands in the first place.

Atuin works entirely on your machine by default. It can also sync your history between computers. That's optional, it needs an account, and Atuin says synced data is end-to-end encrypted with a key that only you hold. Understand what you'd be syncing before you turn it on. You can use Atuin locally and never sync anything.

Newer versions also add features for AI coding tools. I'm only covering shell history here.

Try it: after installing, bring in your existing bash history and press Ctrl+R:

atuin import bash

Install: Atuin needs a bit of shell setup, especially in bash, so follow the official guide.

Its install script walks you through importing history and offers to set up sync. You can skip sync. Ubuntu 26.04 also has an older atuin package if you'd rather use apt.

Bonus: make the terminal look like yours

Productivity aside, there's nothing wrong with making the terminal look good.

Starship replaces your prompt with one that shows useful context at a glance: the current folder, your Git branch and whether it has changes, the version of whatever language you're working in, and whether your last command failed.

On Ubuntu 25.04 and newer (including 26.04):

sudo apt install starship

Then add this to the end of ~/.bashrc:

eval "$(starship init bash)"

On Ubuntu 24.04, use the official instructions at starship.rs. A Nerd Font makes the icons display properly.

One small security habit

Several of these projects offer a one-line installer like this:

curl -sS https://example.com/install.sh | sh

That runs whatever the script says, right away. It's convenient, and from the official project it's usually fine. But don't copy curl | sh commands from random blog posts. Get them from the project's own documentation, and if you're curious, download the script and read it first:

curl -sS https://starship.rs/install.sh -o install.sh
less install.sh

Then run it if it looks right.

Which ones would I install first?

New to Linux: btop, tldr, bat, eza. They make the basics clearer without changing how you work.

Comfortable with Linux: fzf, zoxide, ripgrep, Atuin. These save real time once they're in your fingers.

Writing code or documenting labs on GitHub: lazygit, ripgrep, fzf, Yazi.

Try This: upgrade your terminal

Don't install all ten. Pick three:

  1. One tool that saves you time.

  2. One tool that helps you see what's going on.

  3. One tool you just think is cool.

Use them for a week. Keep the ones you actually reach for, and remove the rest (along with their lines in ~/.bashrc).

That's the whole lesson: don't install things because someone on the internet said they're essential, including me. Keep what makes your work better.

Remote roles worth a look this week

Shorter list this week, since the main issue is long. I checked each one on the employer's own page while preparing this issue, but listings close quickly, so check before applying.

Customer Support Engineer, LILT
Remote (Pacific or Mountain time zone) | $64.4K-$90.2K + equity | 1-3 years
First-line support for a translation platform: triage, bug reproduction, and customer calls.
View the role

Technical Support Engineer (L1), Runpod
Remote U.S. | $55K-$73.3K | about 2 years
Support for an AI cloud platform. Wants shell scripting, Python, SQL, SSH, and Linux. May require weekend work and an assigned shift.
View the role

Technical Support Engineer I, EasyPost
Remote U.S. | $53.5K-$67.1K | degree, bootcamp, or 2+ years
Support for enterprise shipping software, with basic SQL and Windows server administration. Must be based in the U.S.
View the role

Cloud Support Administrator, Atmosera
Remote U.S. | Pay not listed | 3+ years of Azure support
Azure, Windows and Linux servers, networking, and PowerShell. Includes on-call, AZ-104 within 90 days, and a Public Trust background check.
View the role

Technical Support Engineer, Vultr
Remote U.S. (limited states) | $30-$40 per hour | 3+ years
Cloud infrastructure support with strong Linux command-line troubleshooting. 24/7 environment with scheduled shifts.
View the role

Looking for flexible side work?

Disclosure: the two links in this section are my referral links. If you sign up through one and meet that program's requirements, I may receive a referral reward.

These are contract platforms, not jobs. Project availability and hours vary, and neither one guarantees you any work or income.

Handshake AI: Handshake describes its AI Fellowship as flexible, project-based contract work, not a full-time job, with no guaranteed hours. Eligibility depends on your location and work authorization.

Mercor: Mercor lists contract projects for independent contractors. Its own postings say projects can be shortened or ended early. Pay and requirements vary by project.

Both links above are referral links, as described at the top of this section.

If you're learning Linux from the beginning

The free SecureByDefault Learning Paths on GitHub organize the fundamentals, troubleshooting, hands-on projects, and career skills into a structured path. It's a work in progress, and I add to it regularly.

And if you're brand new, the free Linux Starter Kit has the commands, a practice plan, and a beginner server checklist.

What terminal tool feels like a cheat code to you? Hit reply and tell me. If enough of you name the same one, I'll write a full tutorial on it.

Talk soon,

Ron
SecureByDefault

Reply

Avatar

or to participate

Recommended for you

View all
caret-right