6 ms·
Hi, I'm a systems administrator. I'm reasonably senior. I can tell you that pretty much all sysadmins code. In overlapping sets, some are good at it, some don't
by dsr_ 13y ago
Hi, I'm a systems administrator. I'm reasonably senior. I can tell you that pretty much all sysadmins code. In overlapping sets, some are good at it, some don't need to be good at it, and some like solving problems that way. But being a sysadmin is a different job from being a software developer, and people who are good at one and not the other are much more common than those who are good at both.
The nature of systems administration work falls into two broad categories. The first is small problem work: a user has a problem, a machine signals an alert, something isn't working. The second is, of course, large project work: users need a new service, the alerting system needs to be replaced, new infrastructure needs to be built. Most of the time, but not always, the small problems need and have immediate solutions, and the large projects are not as time-critical and require some amount of research, budgeting, selection, configuration and support before they can be deemed complete.
A sysadmin who has specialized into a particular problem domain will need the skills appropriate to that domain. Sometimes that means picking up a new configuration syntax -- which may be a complete language. Sometimes it means building better communications skills, so that you can diagnose what your users are complaining about. Whatever it is, you can assume that the people who specialize in an area that doesn't require much programming, don't do much.
Generalist sysadmins, on the other hand, need to be competent at a wide variety of skills, including two or three languages. That doesn't mean that they need to be UX designers (but they need to recognize a UI failure) and it doesn't mean that they need to be database administrators (but they need to understand how to back up and restore the databases they support, and figure out the replication system and find single points of failure). They do need to be able to write short programs to automate what they would otherwise do manually, to figure out what the debug logs are really complaining about, and to understand computer systems from electrical and environmental needs through virtualization systems and configuration management.
Finally, there are sysadmins who are also developers, who announce that they don't like any of the existing mail programs and so they will write a new one; who determine that there's no configuration management system that tracks and removes subsystems as cleanly as they would like, and so a new one will be needed; who write filesystems or music organizers or browser extensions because that's what they need and want and are good at.
The industry, nebulous quagmire that it is, needs specialists, generalists, and dev-ops hybrids. Making false generalizations merely reveals a bizarre lack of awareness.
- WestCoastJustin 13y agoI'd just like to mention something about specialists vs generalists. Over my career, as a sysadmin, I've noticed this trend. At smallish organizations (i.e. startups), you'll see almost exclusively generalists, because the company simply is not large enough to have a team of specialists running around. As the company grows (think fortune 500 companies, universities, government, etc), these generalists will have to make the transition into specialists, say for example into, security, networks, email, linux admins, windows admins, storage, racking/stacking/cabling, etc. You might even have these enterprise architects popping up. I have also seen less sysadmin programming (whatever that is) at the larger companies, because they will purchase prepackaged products that fit their need.
- ams6110 13y agoIn many cases the "prepackaged product" purchasing decisions are being made by managers who won't actually use them. That's why enterprise sysadmin jobs suck so much.
- ownagefool 13y agoTo counter, I worked at a small web hosting company between 2007 and 2010 who were responsbile for creating Europe's first cloud computing infrastructure and the worlds second, according to them at least. They had about 9 sysadmins go through their doors, a maximum of 7 at any one time with a max of 4 coders. Of those system guys I'd hazard a guess that around 50% of them couldn't code at all and only really two could get anything beyond procedural scripting, if that. Not to disrespect these guys because some of them were between good and really good at what they did do, but there were also decisions such as to rely on expensive SANs and proprietary software to tackle issues that could have been and later were replaced by internal code because, in my opinion, these guys were unable to comprehend automation on a scale that a developer could unless they already knew of software available to do such a thing. After that I worked for a massive hosting company with much more segregation of departments and as far as I'm aware operations didn't code despite the deparment being a lot larger than the previous company. It's funny because back then I was arguing with both these companies that operations should be driven from an automation stand point utilising devs skills but it wasn't exactly a great point since I was the only developer on staff for much of that time in the first company and the second wasn't interested at all. For the record, I'd like to be a devops but I'm pretty sure I get shut down from those roles from a percieved lack of operations experience and buzzwords. Much of that because I'm actually honest and my experience of sysadmins are that they were gatekeepers unwilling to so much as let me login to some of their systems. Meh. I'm sure theres a lot of sysadmins out there who a very capable software developers but I think it's a stretch attempting to call often simple configuration languages and extremely short glue scripts programming. But hey, as long as you're adding value, who cares what we're calling it.