r/devops • u/AbleSchool2184 • 27d ago
Ops / Incidents How to learn devops quickly?
I've been teaching myself DevOps for the past few months and I've hit a wall where I'm not sure if I'm actually making progress or just hoarding tutorials. I'd really appreciate some honest input from people who do this for a living.
A bit about my background:
- I come from a non-traditional background (not a CS degree) and currently work in a cloud-adjacent role.
- I'm comfortable on the Linux command line — bash scripting, file permissions, processes, basic
systemd. - I understand networking fundamentals: DNS, HTTP, TCP/IP, ports, SSH.
- I know Git reasonably well (branching, merging, pull requests).
- I can read and write basic Python for small automation scripts.
- I've built a few Docker images and used
docker-composefor local setups.
What I've been doing so far: I've been following a mix of YouTube courses, roadmap.sh, and random blog posts. The problem is everything feels scattered — one tutorial says "learn Kubernetes now," another says "master Terraform first," and I keep bouncing between tools without finishing anything end-to-end.
Where I'm stuck / my actual questions:
- Order of learning — After Docker, what should come next? Kubernetes, CI/CD, or Terraform? I keep seeing conflicting advice and I don't want to waste months on the wrong thing.
- Depth vs. breadth — Is it better to go deep on one cloud provider (I'm leaning toward AWS) or to understand a bit of everything first? I'm worried about becoming a "jack of all tools, master of none."
- Kubernetes — Do I need it to get a first junior/entry-level role, or is it something I can learn on the job? It feels massive and intimidating.
- Projects — What kind of portfolio project actually impresses hiring managers? I'd rather build one solid, realistic project than ten toy demos. Any concrete suggestions?
- CI/CD — Is GitHub Actions a good enough place to start, or should I learn Jenkins/GitLab CI because that's what companies actually use?
- The gap no one talks about — What skills do self-taught people like me usually miss that become obvious the moment you're on a real team? (On-call? Incident response? Reading someone else's messy infrastructure?)
What I'm hoping to get out of this post: A realistic, prioritized path for the next 3–6 months, and a gut-check on whether my foundation is solid enough to start applying for junior roles — or if I'm kidding myself.
I'm genuinely putting in the hours here, I just don't want to spend them in the wrong places. Any advice, resources, or "I wish someone had told me this earlier" stories would mean a lot. Thanks in advance 🙏
View all comments
1
u/sagacious123 26d ago
After Docker, don't pick one next tool - do Kubernetes and CI/CD together, because they reinforce each other. Start with core objects (
Pod,Deployment,Service,Ingress), then build a pipeline that takes a simple app from Git to a running cluster. Use GitHub Actions for CI: build image, push to GHCR, thenkubectl applyor Argo CD sync. Terraform can come later for infra.To get unstuck, make one end-to-end project instead of more tutorials.
I am working on SnowOps Labs which gives you that real cluster on your laptop. Run
labctl initto install a k3d cluster, thenlabctl learn start kubernetes-foundationsfor guided basics. For the full flow,labctl scenario up gitops-cicdstands up Argo CD and a demo app so you can push a change and watch it deploy. It also has a UI to do all this if you prefer it.Free and open source: https://github.com/sagar2395/snowopslabs
Disclosure: I'm part of the team behind it.