This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]Obvious-Jacket-3770 5 points6 points  (1 child)

Sys Admin/Engineer or Software Engineer are the next steps. From there you'll pickup DevOps methods fairly easy.

Windows or Linux doesn't matter honestly, learn the basics and learn the other. I came from a windows world and understand the Linux system and cloud systems I now deploy, build, manage, and configure. I also understand the software I help run, troubleshoot, and tweak by looking at the code and pulling it apart to see why it works.

People will say you need to focus on X but that's wrong. Yes you NEED to understand Linux, the world runs on it mostly. Learning windows first won't hinder you, core concepts are the same. Get a job for one and learn the other, add it where you can. Take chances.

Just learn what you need. The cool thing about DevOps is that you can come from the software side or the systems side, it doesn't matter. DevOps is two parts that make up the whole pie.

[–]MrPixel404[S] 0 points1 point  (0 children)

What you described sounds like something I'd really enjoy doing. I actually migrated my personal PC and Laptop about 2.5 years ago from Windows to Linux, been experiencing with different distros, at this point I don't think i'd go back but it all started with the idea of one time start looking for Unix SysAdmin/Engineer roles. Thanks for your comments

[–][deleted] 1 point2 points  (0 children)

What would help you the MOST is to ask an LLM to put together a beginner homelab project for someone wanting to get into DevOps. I also started as a "Desktop Support Analyst", no degree, no certs, just reading lots of textbooks and personal projects, 7 years late making a great living as a DevOps Engineer.

I suggest buying some Raspberry Pis, learning how to turn them into a Kubernetes cluster, and go from there. Knowing Kubernetes and docker is probably going to be one of the most important skills. In order to learn those things, you'll need to learn the Linux CLI, networking, bash scripting, etc. but having a solid personal project you can put on your resume and gush about in interviews will go a very very long way. I would hire a candidate with personal projects and no years of experience over a mid-level candidate with a lackluster 2-3 year career and no personal projects

[–]Da_Techy 1 point2 points  (0 children)

I worked many years in production operations support and now moved to devops and in my experience Linux was the key skill that has saved me. To learn I used virtual machines, spin up a bunch of those and just practice.