Earlier quoted context omitted.
Okay, but you spend 2000 hours per year at work. So 10 hours on a config is only .5%, which is the productivity gain you need to realise to get that time back in one year (assuming you also spend 0 hours on fighting vscode). Unless you're retiring within the year, that calculus doesn't make sense. The productivity boost you get with from Emacs/vim is huge once you learn it well. I strongly believe that learning one o…
I've been coding for nearly 40 years and I just don't see any correlation between editor usage and developer productivity. Being able to design and work with complex software systems is what makes a senior dev productive, not which keys they hit to copy and paste.
I’ve been building corp infrastructure for a decade and I can tell you first hand how much of an impact fast, stable, updated environment can have on organizational productivity and overall output. I doubt devs are some how excluded from the pack.
The old proverb of shit in shit out also applies.