3 ms·
> Is this why Silicon Valley is allergic to the phrase 'systems administrator' There is no need for 'systems administrator' in the Silicon Valley. The systems
by user5994461 10y ago
> Is this why Silicon Valley is allergic to the phrase 'systems administrator'
There is no need for 'systems administrator' in the Silicon Valley.
The systems administrators are the guys who buy the desktop computers, setup windows, and kinda manage the active directory.
DevOps/SRE names exist because the tech scene had to stop the confusion between the hardcore linux admins who can code and the dude who can setup your desktop computer. The first is needed in dev companies mostly located in the tech hubs, the second is needed in most companies all around the world. The two have very little in common.
- rhizome 10y agoThe people who take care of internal user systems are IT. IT may have sysadmins, but a sysadmin is not necessarily IT.
- flukus 10y agoSince when was the dude who can setup your desktop a sys admin? That would be tech support.
- nickpsecurity 10y agoA major, Fortune 100-500 firm in my area had many of their Win7 machines rolled out over the network by a guy that knows nothing about networking, can't tell cache from RAM unless explicitly marked, and calls me for basic, tech support on occasion. That it worked out fine with basic automation in place supports your assertion. ;)
- stonogo 10y ago> DevOps/SRE names exist because the tech scene had to stop the confusion between the hardcore linux admins who can code and the dude who can setup your desktop computer. If that confusion existed in any otherwise-competent organization, it was only in the valley. I was a systems administrator before any of "SRE," "DevOps," or "linux" came to be, and I don't think anyone has ever confused me for tech support.
- sk5t 10y agoMost of the working Windows system administrators I have met could not code their way out of a wet paper bag (but a majority could code their way into one). If you've been unlucky enough to work on a "managed" workstation, their near-total unawareness of optimization, state, and exception handling is why your Windows login script takes 10 minutes to crunch away.
- flukus 10y agoTo be fair, windows scripting is pretty limited. Then you have powershell which is way to bloated for quick and dirty things.
- sk5t 10y agoMost of the nasty Windows scripts I've seen were VBScript, used to bludgeon about various WMI providers and to launch unfortunate executables. I don't think the language was much of a hindrance on its own, but it did nothing to repel stupidity. Several years on, I still don't know what to think about Powershell, it's basically .NET + pipelines + some discoverability aids, not terrible in concept but I will probably go on ignoring it for the rest of its life.
- smitty1110 10y agoThe guy that sets up your laptop is an IT tech, not an SA. The SA is the hardcore linux admin who can code. From my perspective, and SRE is a SE that focuses entirely on back end performance and reliability, in order to support the SAs. DevOps is a term used by management to justify cost-savings by avoiding hiring someone to ensure system reliability, consistency, safety, and integrity.
- hibikir 10y agoMaybe in places that started well: I have no doubt that there have always been people out there that were doing system administration and could code. The places where I have seen DevOps become popular are those that completely separated programming keeping servers running, and where the people keeping said servers running were incapable of doing even mild automation. Places where rebooting a non-db server requires making a request 3 weeks in advance, and being OK with 4 hours of downtime. In those environments, those people that are called system administrators are very low productivity, can't help you with a performance problem if their life depends on them, and are easily replaceable with shell scripts. It's in those environments where DevOps and enterprise cloud migrations are popular: The developers might not be experts in scalability or in getting great uptime, but at least they can get something done. Ultimately this gives management an excuse to lay off all the sysadmins that don't know what /proc is, and make technical decisions based on Gartner reports. Again, that doesn't mean that everyone that has the title of sysadmin in the world can't code or is unproductive: This is not a judgement on the value of a good SA. I am just trying to open a window to a world that many developers get to see, but few good SAs notice, because there's no way in hell a good SA would work in said companies for long.