Developer Productivity Tools That Actually Stick

Every month brings a new "10× productivity" tool. Most get tried once and abandoned. The ones that stick share a trait: they remove friction from something you already do daily.

Terminal & shell

tmux / zellij — persistent sessions across SSH disconnects. Non-negotiable for remote work.

fzf — fuzzy finding everything: files, history, git branches. Once you learn the keybindings, going back hurts.

ripgrep + fd — faster than grep and find. Your search muscle memory updates in a day.

Editor & AI

Cursor / Copilot — AI pair programming for boilerplate, tests, and refactors. Best used when you review every suggestion rather than accepting blindly.

LSP everywhere — consistent go-to-definition, rename, and diagnostics across languages. Invest in LSP config once per language.

Notes & docs

Obsidian / Notion — pick one system for technical notes. Link concepts, don't folder-hoard. A single inbox note beats a perfect taxonomy you never maintain.

Diagrams as code — Mermaid in markdown keeps architecture docs next to the code in git.

CI & local dev

Docker Compose — reproducible local stacks. If docker compose up doesn't work on a fresh clone, fix that before adding features.

pre-commit hooks — lint and format before push. Cheaper than CI failures 10 minutes later.

The meta-tool: saying no

The highest-leverage productivity move is removing tools, not adding them. Audit your stack quarterly:

• What haven't I opened in 30 days?
• What am I maintaining that a simpler default handles?

Final thought

Tools amplify habits. Fix the workflow first, then automate the boring parts. Everything else is shelfware with good marketing.