I'm a quite good programmer who is a pretty terrible sys admin.
Of your 11 points, I understand 1-10 quite well, but I'm not great at 11.
I think the skill sets are quite different, despite the fact that a lot of people have both. I was never really that "into computers", but I have a burning passion for building large software systems fast and well.
Metaphor: I love to travel to exotic locations across the planet. That doesn't mean I'm also interested in building airplane engines.
To be clear, I'm not bragging. It would be great if I was good at this stuff.
I don't think the OP is talking about low-level OS stuff like perhaps a flaky hard drive, but about installing the things that turn a vanilla machine into your working environment, plus being able to sort out things when something goes wrong with that environment. If you're in IDE Foo all day every day, you should know your tool enough to fix it when it goes wrong.
I've not had them myself, but I have talked to other sysadmins who've had devs that couldn't install their own IDE. These people weren't seniors, admittedly, but they were still drawing pay...
Of your 11 points, I understand 1-10 quite well, but I'm not great at 11.
I think the skill sets are quite different, despite the fact that a lot of people have both. I was never really that "into computers", but I have a burning passion for building large software systems fast and well.
Metaphor: I love to travel to exotic locations across the planet. That doesn't mean I'm also interested in building airplane engines.
To be clear, I'm not bragging. It would be great if I was good at this stuff.