I’ve spent more time than I’d like to admit tweaking my dev setup. Trying new plugins, swapping terminals, reorganizing dotfiles at 1 AM. Most of it was yak-shaving. But over the years, a handful of tools and workflow changes genuinely moved the needle on my productivity. Not in a “10x developer” fantasy way, but in a “I shipped the feature before lunch” kind of way.
Here’s what actually stuck.
Start With Your Editor, But Don’t Stop There
Your IDE is the center of gravity for your workflow. Whether you’re in VS Code, JetBrains, Neovim, or something like Kiro, the goal is the same: reduce friction between thinking and doing.
A few editor-level changes that made a real difference for me:
- Keyboard-driven navigation. I forced myself to stop reaching for the mouse. Learning just 10-15 shortcuts in your editor (go to file, go to symbol, rename symbol, toggle terminal) compounds fast.
- Workspace-scoped settings. Instead of one global config, I keep per-project settings for linting rules, formatters, and font sizes. It sounds small, but context-switching between a Python data pipeline and a React frontend is smoother when your editor adapts with you.
- Snippet libraries. Not the built-in ones. I mean custom snippets for patterns you actually repeat. A React component skeleton, a test file scaffold, a SQL migration template. Five minutes of setup saves hours over a quarter.
IDE Plugins Worth Installing (and a Few to Skip)
Plugin fatigue is real. I’ve seen setups with 40+ extensions where the editor takes 8 seconds to boot. Here’s my short list of plugins that earn their keep:
GitLens (VS Code) or Equivalent
Inline blame annotations and commit history per line. When you’re debugging something weird in a legacy codebase, knowing who changed a line and why is invaluable. I use this daily.
Error Lens
This one surfaces diagnostics inline, right next to the offending code. No more squinting at the problems panel. It looks like this in practice:
const name: string = 42; // Error: Type 'number' is not assignable to type 'string'
The error shows up right there on the line, in red, impossible to miss. It tightens the feedback loop significantly.
AI-Assisted Coding Tools
This category has matured a lot. Tools like Kiro’s AI assistant, GitHub Copilot, and Codeium can genuinely speed up boilerplate-heavy work. The key is knowing when to lean on them and when to think for yourself. I use AI suggestions for test scaffolding, repetitive CRUD operations, and generating types from API responses. I don’t use them for architecture decisions or complex business logic.
Plugins I Stopped Using
Bracket colorizers (most editors do this natively now), overly aggressive auto-importers that guess wrong half the time, and any plugin that adds decorations to every single line. Less visual noise means more focus.
Workflow Patterns That Compound
Tools matter, but how you use them matters more. A few workflow patterns I keep coming back to:
The 15-Minute Rule
If I’m stuck on something for 15 minutes without making progress, I change my approach. That might mean reading the source code instead of the docs, writing a minimal reproduction, or just asking someone. The instinct to “push through” often wastes more time than it saves.
Terminal Aliases and Scripts
I keep a small collection of shell aliases that remove daily friction:
# Quick project navigation
alias work="cd ~/projects && ls"
# Run tests for just the changed files
alias tt="git diff --name-only | grep '\.test\.' | xargs npx vitest --run"
# Spin up a scratch file fast
alias scratch="code ~/scratch/$(date +%Y%m%d).ts"
None of these are clever. They’re just small time-savers that add up across hundreds of uses.
Commit Early, Commit Often
I used to write code for hours before committing. Now I commit in small, logical chunks. It makes code review easier, git bisect actually useful, and reverting painless. A good rule of thumb: if you can’t describe your commit in under 50 characters, it’s probably doing too much.
Automate the Stuff You Keep Forgetting
Linting, formatting, type-checking. If these aren’t running automatically, they’re not running consistently. My baseline for any project:
- Pre-commit hooks via Husky or lefthook for linting and formatting.
- CI that runs the full test suite on every PR. No exceptions.
- Auto-formatting on save. Prettier, Black, gofmt, whatever your ecosystem uses. Stop debating tabs vs spaces and let the machine decide.
The goal is to make the right thing the easy thing. If developers have to remember to run the linter manually, someone will forget. Automate it and move on.
Protect Your Focus Time
This isn’t a tools tip, but it’s the highest-use productivity change I’ve made. I block 2-3 hours every morning with no meetings, no Slack, no context switches. That’s when the hard problems get solved. All the plugins and shortcuts in the world can’t compensate for a fragmented calendar.
If your team culture makes this hard, start small. Even one protected hour a day is better than zero.
Wrapping Up
Developer productivity isn’t about having the most tools. It’s about having the right ones, configured well, and backed by habits that reduce friction. Start with your editor. Add a few high-value plugins. Automate the repetitive stuff. Protect your focus.
If you’re looking for an environment that brings a lot of this together, agntbox.com is a good place to explore what modern AI-assisted dev workflows can look like. Give your setup an honest audit this week. You might be surprised how much time you get back.
🕒 Last updated: · Originally published: March 19, 2026