4 ms·
I no longer fall into deep pits of yak shaving, but I'm not sure I agree with the opposite extreme either ("use the absolute vanilla defaults"). But I would ex
by telemachos 14y ago
I no longer fall into deep pits of yak shaving, but I'm not sure I agree with the opposite extreme either ("use the absolute vanilla defaults").
But I would expect that there's a natural progression (sort of like the many "evolution of a <language> programmer" posts[1]). You start using these programmer's tools, and at first you struggle to do basic things with default settings. Then, later, you learn that everything can be configured. You spend days (weeks? months?) getting very little real work done, but configuring everything. Then, later again, you calm down, find a set of reasonable and productive configurations, automate getting them onto new machines when necessary and go back to work.
[1]: Example for Python: https://gist.github.com/289467 https://gist.github.com/289467.
- dice 14y agoIt likely depends on what you're doing as well. For programmers who spend most of their time editing source code and working on a small number of development machines it makes sense to put some effort into customizations to optimize workflow. For sysadmins who have to be able to do work on thousands of machines across various environments it makes sense to know the stock settings inside and out.