Laying the theoretical foundation
Theory is the foundation of everything. Before and alongside hands-on work, I've been building theoretical knowledge through structured courses, documentation deep-dives, community voices and continuous reading. KodeKloud has been my primary structured learning platform, combining video lessons with real browser-based labs across Kubernetes, Terraform, Helm, Linux, Ansible, Prometheus, Shell scripting and much more. This isn't a phase I completed and moved on from; it's a habit I maintain daily.
Duration: Ongoing — building day by day
"You can't debug what you don't understand. Theory is not optional. It's the multiplier on everything else."
Milestones
- Completed 15+ KodeKloud courses with hands-on labs. Covering Kubernetes, Terraform, Helm, Docker, Ansible, Prometheus, Linux, Shell Scripting and more
- Built habit of reading DevOps articles and community blogs regularly
- Following key community leaders across YouTube, LinkedIn and blogs
- Using official documentation as the primary reference source
Skills & Tools
Challenges & Solutions
The DevOps space is overwhelming to enter. Endless tools, conflicting roadmaps and well-meaning advice pointing in every direction at once. Knowing where to actually start was harder than learning the material itself.
Stopped trying to optimise the roadmap and just picked one. Anchored learning to official documentation and a single structured platform (KodeKloud), then used community content to fill gaps. Committing to a path and following it consistently beat endlessly comparing alternatives.
Some concepts are genuinely hard to grasp from documentation or course slides alone. The material makes sense on paper but doesn't click until you've seen it in action.
Combined theoretical material with hands-on labs as early as possible and relied on community content, YouTube breakdowns, blog posts and real-world examples whenever the official material wasn't enough. Seeing the same concept explained three different ways usually closed the gap.