3 ms·
To which my answer would be: I've been in this game for 25 years. I lost my will to configure long ago, and now just use the default. The default is better test
by kstenerud 4y ago
To which my answer would be: I've been in this game for 25 years. I lost my will to configure long ago, and now just use the default. The default is better tested, good enough for most tasks, and doesn't leave you hobbled whenever you have to work on a fresh machine as you try to remember what custom things you had set up, or if your config git repo is properly up to date and doesn't introduce unwanted dependencies (or if you can even connect to it).
It's also a major source of WFM (works for me) syndrome, where something in your custom stuff is unintentionally needed by the build.
I'd rather be building things than playing with my tools. If I really need something esoteric, I'll find another tool or write a Python script
- 314 4y agolol. This is why I reach for vi
- ptr 4y agoSame for me, a custom configured environment has often become yet one more thing that can break and needs maintenance. I make sure I have basic emacs keybindings but that’s almost it. In my experience, the people that spend most time on customizing the tools have mostly been junior developers. Though if you asked me on productivity tools we’d have an interesting discussion. I guess it’s just a matter of focus.