I've been working in DevOps for a while and consider myself experienced, but I feel lost when it comes to understanding the direction of the field. I'm currently involved in things like Kubernetes emergency drills and CI/CD tuning, but I often hear buzzwords like "AI-driven infrastructure" without anyone really understanding what it means. I attempted to put together a learning plan, but it turned into a chaotic mess of tabs with Kelsey Hightower talks, an unfinished Terraform course, and system design resources for interviews. One moment I'm deep into notes, and the next I'm creating sketches or checking my work with coding assistants.
The problem is, everything feels so fragmented. One minute I'm learning about Pod Disruption Budgets, and the next, I'm reading about cost anomalies, then some blog says I need to know about L4/L7 load balancing. I don't have a clear learning roadmap that suits me, just scattered information that I need to piece together while also keeping up with industry changes. So, how do others manage to organize their learning structure when everything feels overwhelming? Do you dive deep into one topic at a time or switch between several topics weekly?
6 Answers
It sounds like you’re trying to tackle too many things at once. Instead of hopping around, I’d suggest taking a more sequential approach. For example, you could start with local Kubernetes development tools like kind or minikube. Then, maybe refresh your Kubernetes knowledge as if you're a beginner. If you’re using managed Kubernetes, consider focusing on the CKAD path instead of core management. After that, explore Kubernetes tooling like Helm and dive into the classic monitoring stack with Prometheus and Grafana. Just set clear objectives for each step, like setting up a local cluster or deploying a test app, and eventually build a project combining all of it.
A great way to structure your learning is by looking at specific job postings that interest you. The requirements in those postings can act as your roadmap. Check the skills that employers are looking for and prioritize your learning based on that. It helps give you direction and makes your learning more purposeful.
It's one thing to keep up with tech trends, but it's another to integrate them into your work experience. That’s something I've struggled with, too. Just keeping up doesn't mean you can mark it as practical experience on your resume.
I have this feeling that the demand for DevOps roles might shift in the next few years. With AI stepping in, junior roles are at risk, and eventually, seniors might face the same fate. Focus on learning future-proof skills, especially around AI and automation tools. They seem to be where everything's headed.
Have you checked out sites like roadmap.sh? They have ready-made plans that can guide you. That said, I find I often just learn what I need at the moment to complete tasks at work. It’s practical and gets the job done, even if it's not super organized.
Honestly, it sounds like you have a lot to learn. Many of the topics you mentioned are fundamental for any DevOps professional. It might be worth going back to basics and strengthening those core skills before diving deeper.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures