Optimizing Linux for Development Workflows

A well-configured Linux environment is one of the highest-leverage investments a developer can make. The initial setup cost is real, but you pay it once and compound the returns for years.

Start With the Shell

Most developers underinvest here. A fast, informative prompt and a handful of well-chosen aliases will save more time over a year than almost anything else you can configure. The move from Bash to Zsh or Fish isn't critical — the key is actually learning the shell you use.

# .zshrc — worth every line
export EDITOR='nvim'
alias gs='git status'
alias gd='git diff'
alias ll='ls -la --color=auto'

# fzf for fuzzy finding — install this immediately
[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh

Terminal Multiplexing

If you're not using tmux or zellij, you're leaving productivity on the table. Persistent sessions mean your workspace survives SSH disconnects, reboots, and typos. Learn five tmux keybindings and use them until they're muscle memory before adding more.

Profiling Before Optimizing

The temptation to endlessly tweak your environment is real. Before you go deep on any optimization — build times, shell startup, editor startup — measure first. hyperfine is excellent for benchmarking shell commands. Know your baseline, or you'll spend an hour saving 200ms you won't notice.