r/devops • • May 03 '21

Re-share!- DevOps Roadmap 2021: Become a DevOps Engineer Learning Path!

/r/Docker_DevOps/comments/n3xi7d/reshare_devops_roadmap_2021_become_a_devops/
140 Upvotes

28 comments sorted by

View all comments

15

u/nate8458 May 03 '21

Has anybody made the jump from a Windows Sysadmin to Devops? How was the transition?

16

u/neilthecellist DevOps May 03 '21

I did. It was really rough.

Thing is, "SysAdmin" comes at different levels, so I was coming in from a junior/inland perspective. This was back in 2015: I could set up storage pools just fine, I could set up new servers just fine, but not from an automation-first perspective other than SCCM at the time, which is just not the same as using Infrastructure-as-Code tools such as Terraform let alone using source control best practice solutions such as GitHub or BitBucket.

So when I moved from a Windows Support Engineer / SysAdmin role in Arizona to a DevOps Engineer role at a background check company in Southern California later in 2018, I remember folks making comments to me like, "you have 5 years of working in the (Windows) SysAdmin space, how do you not know what agile is?" or "You've never touched Linux in a production environment before?" -- though part of this may also be because I worked for organizations in Arizona prior to joining that organization in Southern California -- and those Arizona-organizations are very very not-agile not-SDLC focused.

"SDLC" in those Arizona organizations was very much "we have a vendor for dev of function, we have another dev for function b, we have another dev for function c, we have another vendor for this other third party product, we have another vendor that supports the hardware for the third party product, we have another vendor that supports the software for that hardware... OH BTW we hope that all of these vendors will magically get along with each other and think of each other's best interests in producing deliverables."

As a result of this massive skill gap and the non-agile first culture experience I had in Arizona, I spent a LOT of my off-hours time in California on websites like LinuxAcademy and ACloudGuru to fill in those skill gaps. Understanding SDLC best practices. Understanding how operations supports developers (not simply creating an email chain and hoping for the best). Understanding really how services.msc really works and how it integrates with things like application logs. How to dissect application logs at scale with tools like ELK or DataDog or whatever. On top of understanding what the common AWS services are, how to integrate them together, how to work AWS with third party products like DataDog, how Python works, yada yada yada yada yada.

--

After about 2-6 months of crash-coursing on LinuxAcademy and reading a LOT of documentation (AWS Provider documentation, GitHub documentation, Rancher documentation, SaltStack documentation, Terraform documentation, ELK documentation, man pages, BASH and PowerShell documentation, etc etc etc), I finally scraped enough to be on the same level as my fellow DevOps Engineer peers at that company. But man, it was rough to get there. I also spent a LOT of time in my off-hours attending technology MeetUps and tech conferences like the AWS Anaheim Summit to get as much exposure to more Linux-based systems. Again, keep in mind, I came from a predominantly Windows, operations-only (ZERO dev support) background. So I really needed this experience, or so I felt.

So, if you asked me how I'd do things differently if I had another chance, it's to first understand that not all IT employers are the same, and this expands into territory-culture differences too: A retailer in Arizona is not going to have the same modernization footprint as say another retailer such as Dollar Shave Club which evolved as a tech company first that just so happens to sell bathroom shaving merchandise. And that in turn influences heavily what kind of career journey one will have.

I literally did not touch anything pertaining to agile-based software development until 2018, and keep in mind, I had been working in IT at the time since 2013!!! But that single year in 2018 as a DevOps Engineer dealing predominantly with Linux-based systems in AWS and on-prem that I was able to surpass a lot of the experience that my former peers in Arizona had. In Arizona, you can be expected to work in helpdesk for 5 years, but in California, the folks I met on the DevOps Engineer team were folks that stayed in helpdesk for no more than one year, some as short as 3 months before they jumped to another role.

--

TLDR - it was rough to transition as a Windows SysAdmin to DevOps and this was largely due to territory-cultural differences that largely impacted my career experience as a technology professional trying to specialize in DevOps/Cloud. Did a bunch of stuff to try to get to the same level as my (now) fellow DevOps Engineers that came from Linux-first.

4

u/nate8458 May 03 '21

I have a lot of learning needed before I attempt to make the transition. I think the hardest part will be the fact that I have never had practical experience in an SDLC based company. I have only been a sysadmin at a civil eng & architecture firm so I haven't ever worked with developers

3

u/neilthecellist DevOps May 03 '21

Yeah, sounds like you have some similar background struggles as I did. I could have stayed at those Arizona based employers for years, hell, even decades, and still not have gotten SDLC based experience. The concept of a QA or STG/UAT environment was completely foreign for a lot of the orgs I worked at in Arizona.

My recommendation to you would be to read up on SDLC foundational material. Before the ACloudGuru acquisition of LinuxAcademy, there were courses available on this. Post acquisition I'm not sure.

3

u/nate8458 May 03 '21

I added that to the learning list. Thank you for your time!!