Two hours a day sounds modest. Over a year, it is 500 hours — more than 12 full work weeks. That is the gap between a good developer and a great one: not raw intelligence, but systems that eliminate friction.
This guide covers the tools and habits that compound into a 2+ hour daily advantage. Not theory — specific software, specific configurations, and the reasoning behind each choice.
The Three Layers of Developer Productivity
Before tools, understand the structure:
- Elimination — Stop doing things that do not need to be done
- Automation — Let machines do things that do not need human judgment
- Acceleration — Do the remaining things faster
Most developers jump to acceleration (faster keyboard shortcuts) while skipping elimination and automation. The tools below hit all three layers.
Terminal & Shell
1. Zsh + Oh My Zsh (or Fish)
Switch from bash to Zsh and install Oh My Zsh. The productivity gain is immediate:
# Install Oh My Zsh
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
Essential plugins to enable in .zshrc:
plugins=(git zsh-autosuggestions zsh-syntax-highlighting z docker kubectl)
- zsh-autosuggestions — suggests commands as you type based on history (accept with →)
- zsh-syntax-highlighting — colors valid commands green, invalid red
-
z — jump to any recent directory by fuzzy name:
z proj→~/projects/my-project
Time saved: 20–30 minutes daily from faster navigation and command recall.
2. fzf — Fuzzy Finder
fzf transforms command-line searching into an interactive experience.
# Install (macOS)
brew install fzf && $(brew --prefix)/opt/fzf/install
# Search command history interactively (Ctrl+R)
# Search files interactively (Ctrl+T)
# Switch between recent directories (Alt+C)
Custom integrations:
# Interactively kill a process
alias fkill='kill $(ps aux | fzf | awk "{print \$2}")'
# Interactively checkout a git branch
alias fco='git checkout $(git branch | fzf)'
# Open a file in VSCode from fuzzy search
alias fcode='code $(fzf)'
Time saved: 15 minutes daily from history search and file navigation alone.
3. Starship — Cross-Shell Prompt
Starship shows git status, language versions, and command duration in your prompt — all with near-zero latency.
curl -sS https://starship.rs/install.sh | sh
echo 'eval "$(starship init zsh)"' >> ~/.zshrc
Why it matters: Your prompt is your dashboard. Knowing your current branch and whether the last command succeeded/failed without typing extra commands saves dozens of micro-decisions daily.
4. Useful Aliases
Add to ~/.zshrc or ~/.bashrc:
# Git shortcuts
alias gs="git status"
alias gp="git push"
alias gl="git pull"
alias glog="git log --oneline --graph --all"
alias gdiff="git diff --staged"
# Navigation
alias ..="cd .."
alias ...="cd ../.."
alias ll="ls -lah"
alias la="ls -A"
# Safety
alias rm="rm -i"
alias cp="cp -i"
# Dev
alias serve="python3 -m http.server 8080"
alias ports="ss -tlnp | grep LISTEN"
alias myip="curl -s ifconfig.me"
Code Editor
5. VSCode with the Right Extensions
VSCode's power comes from configuration. Extensions that deliver the most ROI:
| Extension | What it does |
|---|---|
| GitLens | Inline git blame, commit history, diff view |
| Error Lens | Inline error messages (no need to hover) |
| GitHub Copilot | AI code completion |
| Path Intellisense | Autocomplete file paths |
| REST Client | Test APIs directly from .http files |
| Thunder Client | Lightweight Postman alternative in-editor |
| Todo Tree | Aggregates all TODO/FIXME comments |
| Auto Rename Tag | Renames paired HTML tags simultaneously |
Essential VSCode settings (settings.json):
{
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.wordWrap": "on",
"editor.minimap.enabled": false,
"editor.tabSize": 2,
"files.autoSave": "onFocusChange",
"terminal.integrated.defaultProfile.osx": "zsh",
"workbench.colorTheme": "One Dark Pro",
"editor.fontFamily": "JetBrains Mono, monospace",
"editor.fontLigatures": true
}
Time saved: 30 minutes daily from faster navigation, inline errors, and autocomplete.
AI-Powered Tools
6. GitHub Copilot
Copilot has evolved from a novelty to a daily necessity. Its value is not in writing code for you — it is in eliminating the boilerplate between your ideas.
Where it shines:
- Writing test cases (describe the behavior, let Copilot write the test)
- Generating repetitive CRUD operations
- Writing documentation from code context
- Converting pseudocode to working implementations
Workflow tip: Write a comment describing what you want, press Enter, and accept the suggestion. Then refine. This is faster than typing from scratch for 80% of code.
7. AI for Code Review
Before pushing a PR, paste your diff into an AI and ask: "What edge cases am I missing? What could go wrong?" Claude, GPT-4, and Gemini all catch things human reviewers miss — especially around error handling, input validation, and concurrency.
Time saved: 45 minutes per PR cycle in reduced review rounds.
DevPlaybook has free tools for this: AI Code Review, AI Error Explainer, and AI Test Generator.
API & Backend Development
8. HTTPie or Bruno (Instead of Postman)
Postman became bloated. Two leaner alternatives:
HTTPie (terminal):
http GET api.example.com/users Authorization:"Bearer token123"
http POST api.example.com/users name="Alice" age:=30
Bruno (GUI, offline-first, Git-friendly): stores collections as files in your repo instead of the cloud. Your API tests travel with your code.
9. jq — JSON Swiss Army Knife
# Pretty print
curl api.example.com/users | jq .
# Extract specific field
curl api.example.com/users | jq '.[].name'
# Filter by condition
curl api.example.com/users | jq '[.[] | select(.age > 25)]'
# Transform and output CSV
curl api.example.com/users | jq -r '.[] | [.name, .email] | @csv'
Time saved: 10 minutes daily if you work with APIs.
Task & Focus Management
10. A Real Todo System
Tools do not matter — consistency does. The minimum viable system:
- Capture — one place for everything (Notion, Obsidian, plain text, paper)
- Triage daily — every morning, pick 1-3 non-negotiable outcomes
- Time-block — schedule deep work before 11am when possible
- Review weekly — 30 minutes every Friday to clear the backlog
The developers who ship consistently are not the ones with the smartest tools. They are the ones who know exactly what they are supposed to be doing right now.
11. Pomodoro + Focused Work
The technique is simple: 25 minutes of focused work, 5-minute break, repeat. The actual mechanism is the commitment to stop context-switching for 25 minutes.
Apps: Flow (macOS), Session (cross-platform), or just a phone timer.
Why it works: Most interruptions are self-generated. The Pomodoro structure externalizes the decision to focus — you are not choosing to focus, the timer is running.
Git Workflow Accelerators
12. Git Aliases (Already in Your .gitconfig)
[alias]
st = status -sb
co = checkout
br = branch
lg = log --oneline --graph --all --decorate
undo = reset --soft HEAD~1
wip = "!git add -A && git commit -m 'wip: checkpoint'"
done = "!git wip && git push"
standup = log --since yesterday --oneline --author="$(git config user.email)"
git standup gives you your yesterday's commits for the daily standup — instant.
See our full Git Commands Cheatsheet for 50+ commands organized by workflow.
13. GitHub CLI (gh)
The gh command turns GitHub into your terminal:
# Create a PR from current branch
gh pr create --title "feat: add login" --body "Closes #42"
# View PR status
gh pr status
# Check out a PR locally
gh pr checkout 123
# View CI status
gh run list
# Open current repo in browser
gh browse
Time saved: 10 minutes per PR cycle in tab-switching and UI navigation.
Automation & Scripting
14. Task Runners: make or just
Every project should have a Makefile (or justfile) that documents common operations:
.PHONY: dev build test lint deploy
dev:
npm run dev
build:
npm run build
test:
npm test
lint:
npm run lint && npm run typecheck
deploy:
./scripts/deploy.sh production
Now make dev works for any developer on any machine, regardless of the tech stack details.
15. Dotfiles Repository
Your development environment is a product. Treat it like one.
A dotfiles repo stores:
-
.zshrc/.bashrc .gitconfig- Editor settings
- SSH config structure
- Custom scripts in
~/bin/
With a setup script, you can clone your entire environment onto a new machine in 5 minutes.
Monitoring & Debugging
16. htop / btop — Better System Monitoring
htop is top with a usable interface. btop adds graphs. Both let you kill processes, sort by CPU/memory, and filter by name — all without memorizing ps aux syntax.
brew install htop btop # macOS
apt install htop btop # Ubuntu
17. tldr — Practical Man Pages
man curl gives you 10,000 words. tldr curl gives you 20 examples.
npm install -g tldr
tldr curl
tldr docker
tldr git
Communication & Documentation
18. Markdown Everywhere
Write all notes, documentation, and specs in Markdown. The habit pays dividends:
- GitHub renders it automatically
- Most wikis support it (Notion, Confluence, Obsidian)
- Easy to version-control with git
- Portable — no vendor lock-in
Use our Markdown Cheatsheet as a reference.
19. Loom for Async Video
Record a 3-minute Loom instead of writing a 500-word Slack thread. Video:
- Shows context automatically (your screen, your face)
- Asynchronous — no scheduling required
- Faster to produce than clear written explanation
- Recipients watch at 1.5x speed
Use it for bug reports, PR explanations, and feature walkthroughs.
The Compound Effect
Individual tools save minutes. The stack saves hours. Here is the math:
| Tool/Habit | Daily Savings |
|---|---|
| Zsh + autosuggestions + z | 20 min |
| fzf history + file search | 15 min |
| AI autocomplete (Copilot) | 25 min |
| Better editor setup | 20 min |
| Git aliases + gh CLI | 15 min |
| Focused work (fewer context switches) | 30 min |
| Total | ~2 hours |
The key is installation + configuration. A tool you have not set up does not save you anything.
Start here:
- Install Zsh + Oh My Zsh with the three plugins above
- Add
fzfand configureCtrl+Rfor history search - Set up 10 git aliases in
.gitconfig - Get an AI code assistant
- Build a dotfiles repo
Do these five things this week. Everything else follows.
Want to build faster without leaving your browser? Try our free developer tools — over 40 utilities for everyday coding tasks.
Level Up Your Dev Workflow
Found this useful? Explore DevPlaybook — cheat sheets, tool comparisons, and hands-on guides for modern developers.
🛒 Get the DevToolkit Starter Kit on Gumroad — 40+ browser-based dev tools, source code + deployment guide included.
Top comments (0)