11–17 of 17 posts
Source: have worked as a devops engineer in the past, for a few years.
Learn Version Control: Familiarize yourself with Git, as version control is a crucial skill in DevOps. You can start with online tutorials and documentation like the "Pro Git" book by Scott Chacon and Ben Straub.
Master the Command Line: DevOps heavily relies on command-line tools for automation and management. Practice using the terminal extensively and learn essential commands and scripting (e.g., Bash, PowerShell).
Infrastructure as Code (IaC): Get familiar with IaC tools like Terraform or Ansible, which allow you to manage and provision infrastructure programmatically. Online courses like those on Udemy or Pluralsight can be helpful.
Continuous Integration and Deployment (CI/CD): Understanding CI/CD pipelines is crucial in DevOps. Consider learning tools like Jenkins, GitLab CI/CD, or CircleCI. "Continuous Delivery" by Jez Humble and David Farley is an excellent book on this topic.
Cloud Platforms: Familiarize yourself with cloud providers like AWS, Azure, or Google Cloud Platform. You can take vendor-specific certifications or explore resources like the AWS Well-Architected Framework.
Earlier quoted context omitted.
This is pretty vapid advice. Setting aside the absurdity of the idea that you need to decide whether you can like a type of work before you're capable of doing it you've not answered OP's question to any degree. If you have any experience with the field that allows you to answer OP's question please offer that rather than this feel good nonsense.
It's not completely unreasonable point. I do see it's a very different type of work compared to mine. But I learned that life is not about doing something you love, but learning to love what you do. So I'm game to try something new.
Earlier quoted context omitted.
This theory and academic prep that you dismiss is actually pretty damned important. It lays the foundation upon which the experience becomes valuable. What you've suggested is taking the lazy way out on the premise that you don't really need to understand any of it as long as you can muddle through doing enough of it. It is not very good advice. I do agree that experience is important but experience on top of knowled…
Well, don’t take it in the wrong way… I do agree that it’s important, and I’ve personally always made sure to learn lots of theory and do academic and other types of research. I agree with you that preparation and knowledge are super important. What I was trying to say is that you get a really valuable perspective from actually working on a field. You get that plus you see how others work, possibly more senior engine…
The 3xperi3nce and mentorship are obviously important to your success but it's popular for people to try and rely solely on those because it is less effort than learning the mechanics of the subject and often allows people to place rhe blame for their failures on others.
If you want to master something you need both the academics and the experience. Either of them alone leaves you at a disadvantage.
Earlier quoted context omitted.
Thanks! Those Cloud Guru courses look great and are also much more affordable than those from Linux Foundation. Replying to your other comment - yup, I do plan to get my hands dirty, either on my pet project or by helping out my DevOps colleague. I wanna ask - how deep should I know Linux? I bought this crazy book years ago, Linux Programming Interface, which is clearly overkill. Do you have some recommendations ther…
That book is great, I own it myself and it's really good. But that book is more to learn the programming interface - so how the operating system works and the functions you would call for systems programming. It's an excellent book, but it's also more like a reference book. Apart from that, I would say that it's not related that much to devops as a job. It's more related to Linux systems programming. If you work as a…
Earlier quoted context omitted.
That book is great, I own it myself and it's really good. But that book is more to learn the programming interface - so how the operating system works and the functions you would call for systems programming. It's an excellent book, but it's also more like a reference book. Apart from that, I would say that it's not related that much to devops as a job. It's more related to Linux systems programming. If you work as a…
Thank you. These tips are great. Offtopic but I love your simplistic website
Earlier quoted context omitted.
This theory and academic prep that you dismiss is actually pretty damned important. It lays the foundation upon which the experience becomes valuable. What you've suggested is taking the lazy way out on the premise that you don't really need to understand any of it as long as you can muddle through doing enough of it. It is not very good advice. I do agree that experience is important but experience on top of knowled…
Well, don’t take it in the wrong way… I do agree that it’s important, and I’ve personally always made sure to learn lots of theory and do academic and other types of research. I agree with you that preparation and knowledge are super important. What I was trying to say is that you get a really valuable perspective from actually working on a field. You get that plus you see how others work, possibly more senior engine…
I see this all the time with people looking to transition into software development. Everyone wants to take some courses and show their completion certificates as a reason why they should be hired. But most companies care about actual experience. How familiar are you with it really?
Theory is important, but you can be a perfectly fine mid level/mid proficiency dev ops engineer with just about none of it.