Build a setup you’re comfortable working in and actually enjoy using. And stop caring about other people’s opinions on your workflow.
Being comfortable with your tools is not the same as being stuck in a comfort zone.Comfort from mastery removes friction. Discomfort for optics just wastes time.
Your workflow exists to help you think clearly and ship correctly,not to impress strangers who won’t debug, maintain, or own your failures.
Yes, I use Arch.
Yes, I use Hyprland.
Yes, I use IntelliJ for Java backend work.
Not because it’s cool.
Not because minimalism demanded it.
Not because pain was confused with competence.
I chose tools I actually enjoy working in.
I’ve tried the setups people love to recommend.
Ubuntu.
NixOS.
Gentoo.
Neovim with layers of plugins and configs.
They’re all fine.
If a tool makes you slower, more anxious, or constantly second-guessing yourself, it doesn’t matter how correct the internet thinks it is.
Most takes that say something “slows you down” really mean I am fast in my setup, so yours must be wrong.
That is not engineering.
That is ego with benchmarks.
You are the bottleneck, not your editor.
I’ve lost more time chasing a race condition through logs
than I ever have stepping through it once in a debugger.
So stop optimizing for approval and start optimizing for clarity.
Use tools that help you debug calmly.
Refactor safely.
Enjoy sitting down to work.
If someone’s biggest achievement is their setup philosophy,
they probably haven’t shipped anything that puts stress on it.
Build a setup you like.
Stop apologizing for it.
Ship anyway.
Top comments (0)