3 ms·
I don't think I'm missing any nuance. You wrote: > For anyone who is primarily a sysadmin, I would recommend sticking with the default behavior Am I reading
by Tehchops 8y ago
I don't think I'm missing any nuance.
You wrote:
> For anyone who is primarily a sysadmin, I would recommend sticking with the default behavior
Am I reading that wrong?
"Don't customize the default behavior if you're a sysadmin"
Do you not agree with what you wrote?
I'm simply arguing that, as a sysadmin today, you're far better served eliminating the need for N node access to make changes, and using your customized local config to push changes to a repository that is applied by a CM-esque system.
- kbenson 8y agoThe entire sentence was (including typo of "trade odd" instead of "trade off"): For anyone who is primarily a sysadmin, I would recommend sticking with the default behavior (which is rich, and lends itself to being more and more useful and they become familiar with more an more commands), and making a minimum of local config changes and plugins to suit their needs (it's a trade odd. Just choose wisely). The key (corrected) part you're missing is "it's a trade off. Just choose wisely." I go into more detail on that in subsequent comments to other replies. > I'm simply arguing that, as a sysadmin today, you're far better served eliminating the need for N node access to make changes, and using your customized local config to push changes to a repository that is applied by a CM-esque system. That good for many things, but not really an adequate solution for diagnosing a problem under stress.