I just wish someone would've told us we didn't need Computer Science degrees before we wasted four of the best years of our lives on something with negative value simply because we were trying to do the best for ourselves.
Take it from someone that didn't get a college degree: You didn't waste your time. I'm doing quite well in a technical track, however I'll be fighting uphill if/when I move into management at a large corporation. Given two employees with roughly the same ability to manage a group of people, senior management will tend to promote the person with the degree.
At some point Software Engineering should probably become its own degree (possibly an associates degreee) separate from Computer Science. Similar to how Computer Engineering split off. It's a bit strange that CS is this hodgepodge of computer related fields, training scientists, engineers and operationalists alike.
The difference is the Sys Admin don't know (or care) about the binaries produced by development. They simple configure a host, deploy it, and if they run into an issue, shoot it over to development to fix.
In DevOps, sys admins are, at some point, actively working with the development team during development to understand the logic, and members of the development team are actively working with the ops teams to understand how the code is deployed. The goal is that sys admins can understand production errors, and developers get a sense for how their code is deployed.
As I understand DevOps are often meant to have more developer skills than sysadmins. They might have to help with how some infrastructure things in the applications should work and should be able to script the applications themselves, not just the OS. That said I just think it is a role inside the system administrators group that is expected to know some extra things and have much more discussions with the developers (or a person inside the development group that knows more about sysadmin and has the right to do more things with the servers).
I like the sibling comments, here's my own take on that question. I spend my time proactively solving operational problems, while you typical sysadmin acts much more reactively.
I've found that there was always that one sysadmin who was thinking in the longer term and who spent their time working on proactive solutions to problems which weren't burning the house down (yet), the new name just codifies that type of role.
As the old saying goes, there's nothing new under the sun. DevOps is very closely related to sysadmin work. I think it would be fair to say that DevOps is just a specialized form of sysadmin work. You could even say that it is just an approach to sysadmin work.
DevOps means using orchestration and automation tools to perform sysadmin tasks, rather than doing everything by hand. It's a layer atop the tools that sysadmins are used to using. The "dev" part of the term relates to the "infrastructure as code" concept. This concept dictates that your infrastructure should be defined as code that outputs your infrastructure.
Depending on how far along you are in your sysadmin career, and depending on the size of the organization you work in, this may be nothing new, but more recent DevOps efforts extend this to organizations of much smaller size. For example, it is not unusual for environments requiring only a handful of servers (or even one!) to use a fully automated provisioning and deployment toolchain.
Ultimately, you can make the argument that this is nothing new. You can do that with just about anything. "DevOps" is not a provable assertion; it is a refinement of the language used to describe the jobs we do.
This actually sums it up pretty well and it's also the cause for the shortage. A lot of developers don't want to learn all the tools that sysadmins and devops are using. And I suspect that many sysadmins don't know enough about programming.
Isn't this basic economics at work? There's a shortage of workers with a skill-set that is in high demand, therefore, the cost of the workers is high.
Eventually, more workers will acquire the skills and the salaries will adjust accordingly. We saw the same thing with network engineers twenty years ago.
I have to agree... I don't have a formal education, but have been in software development for almost 20 years now... With IT, software development, devops and systems administration it comes down to keeping up with the tech, and being able to get the job done.
I don't think the lack of people to fill said jobs is quite as bad as the article states... many of these roles have been 100k plus for a while, and the people stepping into these jobs are likely to be several years out of high school at this point, having gained skill and experienced.
21 comments
[ 3.2 ms ] story [ 48.1 ms ] threadThe degree will help for management roles at Fortune 500 companies.
I've always felt DevOps was just a shiny new synonym for the decades old SysAdmin moniker.
In DevOps, sys admins are, at some point, actively working with the development team during development to understand the logic, and members of the development team are actively working with the ops teams to understand how the code is deployed. The goal is that sys admins can understand production errors, and developers get a sense for how their code is deployed.
I've found that there was always that one sysadmin who was thinking in the longer term and who spent their time working on proactive solutions to problems which weren't burning the house down (yet), the new name just codifies that type of role.
DevOps means using orchestration and automation tools to perform sysadmin tasks, rather than doing everything by hand. It's a layer atop the tools that sysadmins are used to using. The "dev" part of the term relates to the "infrastructure as code" concept. This concept dictates that your infrastructure should be defined as code that outputs your infrastructure.
Depending on how far along you are in your sysadmin career, and depending on the size of the organization you work in, this may be nothing new, but more recent DevOps efforts extend this to organizations of much smaller size. For example, it is not unusual for environments requiring only a handful of servers (or even one!) to use a fully automated provisioning and deployment toolchain.
Ultimately, you can make the argument that this is nothing new. You can do that with just about anything. "DevOps" is not a provable assertion; it is a refinement of the language used to describe the jobs we do.
Eventually, more workers will acquire the skills and the salaries will adjust accordingly. We saw the same thing with network engineers twenty years ago.
I don't think the lack of people to fill said jobs is quite as bad as the article states... many of these roles have been 100k plus for a while, and the people stepping into these jobs are likely to be several years out of high school at this point, having gained skill and experienced.