Really? There's nothing on that list that suggests a guide for sysadmins. It's really about learning the basics of Windows and Unix so that you can not only be more productive but also let the admins do more productive work.
> So we developers need to focus more on building better software and leave as much admin as possible to those experts.
I've worked in a small company where there were only 3-4 sysadmins, and besides the usual user support they were also in charge of maintaing a few hundreds of servers. In this situation you don't want to bother the sysadmins with stuff like "how do I check if port X on foo is open? Why is ssh asking for my password?". You want to troubleshoot this kind of thing by yourself, so that admins have more time to build clusters and automate stuff instead.
Comments
Really? There's nothing on that list that suggests a guide for sysadmins. It's really about learning the basics of Windows and Unix so that you can not only be more productive but also let the admins do more productive work.
> So we developers need to focus more on building better software and leave as much admin as possible to those experts.
I've worked in a small company where there were only 3-4 sysadmins, and besides the usual user support they were also in charge of maintaing a few hundreds of servers. In this situation you don't want to bother the sysadmins with stuff like "how do I check if port X on foo is open? Why is ssh asking for my password?". You want to troubleshoot this kind of thing by yourself, so that admins have more time to build clusters and automate stuff instead.