Developer productivity is mostly determined by invisible friction. Not the hours you spend on hard problems, but the aggregate cost of slow tools, repetitive context switching, poor search, and workflows that require six steps to do something that should take one. This list focuses on the tools that reduce that friction in ways that compound over weeks and months.
1. Raycast
A Spotlight replacement for macOS that is fast enough to become your primary interface for anything that does not require a window. App launching, file search, clipboard history, snippet expansion, GitHub issue lookup, Jira/Linear ticket search — all accessible within a keystroke, without touching the mouse. The extension ecosystem covers most SaaS tools developers use regularly.
2. 1Password (with SSH agent and CLI)
The version of 1Password that most developers use is underpowered compared to what it can do. The SSH agent integration stores SSH keys in 1Password and signs requests without exposing private keys on disk. The CLI (op) injects secrets into shell scripts, CI pipelines, and environment variables at runtime. Combined, these eliminate two common categories of credential mishandling — SSH keys on disk and secrets in environment files.
3. Warp Terminal
Already mentioned in the AI automation piece, but worth its own entry. Warp’s block-based output model — where each command and its output is a discrete, copyable unit — solves a genuine terminal UX problem. Searching output history, sharing command output, and navigating long sessions are all meaningfully better than in iTerm or the built-in terminal. The AI features are additive, not the core value.
4. Zoxide
A smarter cd replacement that learns your most-visited directories and lets you jump to them with partial matches. z proj instead of cd ~/code/clients/acme/projects/web. Trivial to install, immediate payoff. One of those tools you forget about after a week because it becomes invisible — which is the highest compliment a productivity tool can receive.
5. fd and ripgrep
fd is a faster, more intuitive replacement for find. rg (ripgrep) is a faster replacement for grep that respects .gitignore by default. Both use Rust and are significantly faster than their Unix counterparts on large codebases. If you spend time searching through code on the command line, the combined speedup is noticeable.
6. tmux (or Zellij)
Terminal multiplexing is essential for anyone who runs multiple processes during development. A frontend dev server, a backend API, a database, and a tunnel do not need four separate terminal windows. tmux is the battle-tested option with extensive community configuration. Zellij is the newer alternative with a friendlier default configuration and a layout system that is easier to share across a team.
7. TablePlus
A native database GUI for macOS and Windows that is noticeably faster and less cluttered than DataGrip or Sequel Pro. Supports PostgreSQL, MySQL, SQLite, Redis, MongoDB, and most other databases through a single interface. The query editor, data viewer, and connection management are all well-designed. For developers who interact with databases regularly but do not need a full IDE, it hits the right point on the simplicity-power curve.
8. HTTPie
A command-line HTTP client with a sensible syntax for quick API testing. http POST api.example.com/users name=Brian role=admin instead of the curl equivalent. The output is formatted and colored by default. For quick one-off requests that do not warrant opening a GUI tool, it is significantly less painful than raw curl.
9. Obsidian
A local-first Markdown note-taking tool with a graph view and bidirectional linking. For developers who do a lot of learning, system design, or architecture documentation, the ability to build a connected knowledge base that lives on your filesystem and never touches a SaaS server is genuinely valuable. The plugin ecosystem is extensive. Unlike Notion, it works offline without ceremony and does not require an account.
10. Doppler
A secrets management platform that syncs environment variables across development, staging, and production environments. The CLI integration means your local development environment stays in sync with what runs in CI and production without manual copying of .env files. For teams that have ever had a “it works locally but not in prod because of a missing env var” incident, the problem Doppler solves is immediately obvious.
None of these are novel or obscure. They are the tools that consistently appear when experienced developers compare notes on what is actually in their workflow. The pattern: fast, focused, keyboard-driven, and designed to reduce the steps between intent and execution.
Related: AI tools for developers, software reviews, and the comparison of security tools worth paying for.
About Brian Detering
Brian Detering is a software engineer, educator, and tech writer based in Los Angeles. He teaches programming and software engineering at the University of Southern California, where his work spans programming languages, systems architecture, and applied AI. With over a decade of hands-on experience building production systems, Brian writes about the tools and workflows that actually make developers more productive — from CI/CD pipelines and containerization to API testing and security best practices. When he's not teaching or writing code, he's usually benchmarking the latest dev tools or tinkering with homelab infrastructure.