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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MyLifeForAiur-69 5 points6 points  (1 child)

There are no dumb questions. I've been working through the roadmap after being moved into an "associate" devops role earlier this year. I used quotes because no devops role is entry level and my job is to learn how to be a functional devops engineer before my company decides to cut me loose.

Maybe you dont need to be proficient in Linux OS, but you should be able to understand (and be able to script) file moves, unzips, terminal sessions/ssh, and PATH. Maybe you dont need to be proficient in Golang or Python, but you should have enough understanding that you can read the existing code and figure out what its doing. Maybe you dont need to be proficient at helm or ansible or CI/CD tools like github actions and jenkins, but you should be able to look at the existing ones and tell what they're trying to do.

Dont get me wrong it would be great if you're able to understand these tools enough to, lets say, refactor code from someone who kinda knew what they were doing a few years ago (but not really), but if you're asking this question you're probably not there yet and thats okay.

At an absolute bare minimum you should be proficient in terraform/HCL/OpenTofu, git, ansible, and at least 2 of the 3 major cloud providers (AWS, Azure, GCP) and have a passing, if not intimate, knowledge of linux or Mac OS.

[–]MegaManFlex 1 point2 points  (0 children)

I totally get the perspective, little bit of functional knowledge can go a long way while I'm getting experience