There have been countless threads on this forum talking about coding-skills among sysadmins and network engineers. In some cases, it's been complaints that there are plenty of top-notch schools offering four-year and graduate programs in computer science, but not enough of them offering IT-related degrees. In other cases, it's been complaints about programming courses required for existing IT degrees that some have found to be tedious and 'useless'.
So, why should an IT admin that's busy studying for server or networking exams bother learning to code, or even go so far as to take a degree focused on the subject? Well. . . maybe because it could get you
a job at Blizzard:
Senior Windows Systems AdministratorIT - NETWORK OPERATIONS
Office: Irvine, California, United States
Blizzard Entertainment is seeking an experienced senior Windows system administrator to join a team of system and network administrators. This position will fill a key role in maintaining and optimizing Windows servers and services. The ideal candidate is a dedicated problem solver who can multitask and prioritize tasks in a fast-paced and demanding environment.
Responsibilities
- Implement and maintain a worldwide Windows Server 2003 / 2008 Active
- Directory based forest.
- Design a global patch management solution.
- Troubleshoot and improve a proprietary .NET based application environment.
- Assist in Windows / Unix TCP / IP connectivity troubleshooting issues.
- Standardize and update existing Windows infrastructure.
- Develop internal application testing and QA environment.
- Mentor and train other administrators in all things Windows.
- Share in off-hour / on-call duties.
Requirements
- A minimum of 5 years Windows Server system administration experience, with an emphasis in managing customer-facing applications and services
- Extensive Active Directory design and management
- Experience with patch management tools (WSUS or equivalent)
- An in-depth understanding of basic network services (DHCP, DNS, SMTP, NFS, LDAP)
- Experience with Windows system and .NET application performance monitoring and tuning
- Basic understanding of .NET programming
- WMI and / or PowerShell scripting and management experience
- MSSQL installation and administration experience
- Strong interpersonal and communications skills
Pluses
- A degree in computer science or a related field
- Windows Virtual Machine management
- Windows host-based load balancing experience
- Technical writing and documentation skills
See those four items highlighted in red? Having some experience in the video game industry, I can tell you with a certain amount of confidence that when Blizzard says "experience with" or "basic understanding", it doesn't mean "I read a Step-by-Step book"; it means that you have data structures & algorithms level programming knowledge and you've written enough C# code and PowerShell scripts to call yourself at least a junior-level coder/scripter. . . in addition to having a professional-level understanding of how to administrate the system the code runs on.
That doesn't mean every single job out there requires you to be both a programmer and a sysadmin, but it does mean that there
are jobs you might be losing out on, with great companies like Blizzard for example, if your skill-set falls exclusively on one side of the fence. For those of us with an extensive IT background, working with networking or servers, it's not a bad idea to consider picking up a little bit of coding, or at least scripting, instead of turning our noses in the air and saying, "that's not part of my job."
For those out there just starting out, consider at least getting a few programming-related courses under your belt as you go through college, if you're not already considering doing a Bachelor's degree in computer science. (Or maybe either minor or take an Associate's in CS while studying for your field of interest?) The same can be said for you software-guys: consider taking a couple of basic IT-related courses as you study, or at least consider reading through some A+/Network+ related books, so you're not left on the other side of the fence, losing out on job-opportunities to CS majors who worked as computer lab-techs while they were earning their degrees.