i used to be that developer. you know the one. the one with 47 vscode extensions installed, a custom vim config that takes 20 minutes to explain, and a terminal setup that looks like a space station control panel.
i spent hours, maybe days, tweaking my development environment. i’d read blog posts about “ultimate vim config” or “vscode extensions you need in 2025” and immediately install everything. my dotfiles repo had over 5000 commits. i had keybindings for everything. i could navigate my terminal blindfolded.
but i wasn’t more productive. i was actually less productive.
the problem with optimization
there’s a phenomenon in software development i like to call “optimization addiction.” it’s when you spend more time optimizing your tools than actually doing the work. you convince yourself it’s worth it because “it’ll pay off in the long run.” spoiler: it doesn’t.
here’s what actually happened:
- i spent 2 hours configuring a new vim plugin. used it for 3 days. realized i didn’t need it.
- i spent a week setting up a custom IDE theme. gave up after a month because it was too different from what i was used to.
- i spent countless hours tweaking my terminal prompt to show exactly the right information. never looked at most of it.
the time added up. probably hundreds of hours over the years. and for what? to save myself 2 seconds here and there? to feel like a “power user”? to have something cool to show in a blog post?
the realization
the turning point was when i got a new laptop and had to set everything up from scratch. instead of spending days replicating my complex setup, i just… didn’t. i used the default terminal. i used vscode with no extensions. i used git without any aliases.
nothing changed. my productivity stayed exactly the same. maybe even improved slightly because i wasn’t constantly tweaking things.
that’s when it hit me: my fancy tools weren’t making me faster. they were making me feel busy without actually being productive. they were a form of procrastination disguised as work.
what i learned
after that, i changed my approach:
1. default is fine. the default settings in most tools are there because they work for most people. you probably don’t need to change them.
2. if it takes more than 5 minutes to set up, it’s not worth it. if a tool requires a 2 hour setup process, you probably don’t need it.
3. one new thing at a time. instead of changing everything at once, i now add one tool at a time and use it for a month before deciding if it stays.
4. if you can’t explain why you need it, you don’t need it. before installing something, i ask myself: “what specific problem does this solve?” if i can’t answer that, i don’t install it.
5. time spent optimizing is time spent not learning. the best developers i know aren’t the ones with the best configs. they’re the ones who understand the fundamentals.
what i use now
my setup now is embarrassingly simple:
- vscode with 3 extensions (prettier, eslint, git lens)
- default terminal
- git with maybe 5 aliases
- notepad for quick notes
that’s it. i used to laugh at people who said “just use what works.” now i understand them.
the irony
the best part? since i stopped caring about my tools, i’ve become a better developer. i focus on solving problems instead of configuring my environment. i read more code. i write more code. i spend less time on reddit arguing about which editor is better.
the tool doesn’t make the craftsman. and spending all your time on the tool isn’t the same as doing the craft.
concluding thoughts
this isn’t a post saying “you should use simple tools” or “fancy tools are bad.” if your setup works for you, great. keep it.
but if you find yourself constantly tweaking, constantly trying new things, constantly optimizing… maybe ask yourself why. is it making you better? or is it just a way to avoid the harder work of actually getting better?
i spent years thinking i was being productive because my terminal looked cool. i wasn’t. i was just avoiding the work.
now i just write code. it’s not as pretty to look at, but it gets done.
if you enjoyed this, maybe share it. or don’t. either way, go write some code instead of reading about tools.