If this is true then you may want to read this carefully.
The Software Development Lifecycle has taken a totally different approach due to the constant updates and growth of the software application infrastructure.
The initial Software Development Lifecycle suited the old fashioned SysAdmin role, where they were required to manage only number of Pilot & Production servers with very less frequent patches and updates to software.
It is not the same case now. You have hundreds of servers all running various components of the software with regular updates/patches are required to be uploaded onto them.
You simply can’t keep hiring more SysAdmin just because of the growth to your infrastructure.
It’s gone smarter, but someone has to pay the price for it. The word Automation has eliminated many SysAdmin roles on the job market.
Many tools are introduced in the market such as Chef or Puppet that provides automation process in DevOps environment. Basically doing all the leg work for engineer through a smart scripting.
Someone asked me. Hang on, DevOps guys don’t want to take a stress on managing the resources of the infrastructure. That’s true, they won’t. Thanks to cloud platforms who have taken all the headache of hosting the infrastructure and letting DevOps to focus on their tasks.
So…Where does this leave those SysAdmin who don’t possesses such skills and techniques?
They have two choices from here;
- Upgrade yourself to become a Systems Reliability Engineer or Cloud System Engineer. In order to do that, you need to start learning about cloud platforms, scripting and automation tools. Learn about Linux Administration if you haven’t already been working with Linux OS.
- If you can’t learn all of the above, then there are plenty of SysAdmin jobs in a non-DevOps environment. You may have to decide about this route, before your company decides it for you.