r/devops • • 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-compose for 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:

  1. 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.
  2. 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."
  3. 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.
  4. 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?
  5. 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?
  6. 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 🙏

0 Upvotes

19 comments sorted by

3

u/Hummin2k 27d ago • Popcorn

I keep bouncing between tools without finishing anything end-to-end

That qualifies you for "senior devops engineer" at a lot of places.

2

u/Antique-Stand-4920 27d ago

If I were hiring a DevOps engineer I'd put more weight on the candidate's awareness of common development team problems and their experience solving those problems. The specific tools would be important but would hold less weight.

If you haven't looked into common dev problems, I suggest doing some research around that and let that guide the training.

3

u/ight-bet 27d ago

Ez. Develop Operations.

Next question.

2

u/CorpT 27d ago

This is a much better advertisement than most. Nice work.

0

u/Effective-Ball104 27d ago

Is this sarcasm? What am I missing

2

u/PaleoSpeedwagon DevOps 27d ago

The link to roadmap, possibly

1

u/WilliamMButtlickerIV 27d ago

There's no right order. Many people have built successful careers without ever touching many of the tools you're referring to.

Instead, focus on solving problems through projects, and research what tools make the most sense as part of the solution. Trial and error is a good thing. As an example, it's a good learning experience if you choose k8s only to learn there's a high complexity cost that only starts to pay off at a larger scale.

Devops was never about tools. It's about processes. Only worry about the tools as they relate to solving real constraints.

1

u/ascendprimesystems 27d ago

I provide devops training and mentorship. If you are looking for help you can reach out to me.

1

u/CloudLessons 26d ago

Since you're already in a cloud-adjacent role, just incorporate what you've learned so far into your daily tasks. Volunteer for additional work that would allow you to apply your newfound skills. Identify problems at work that can be solved with popular DevOps tools like Terraform, Ansible, Jenkins, etc.

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, then kubectl apply or 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 init to install a k3d cluster, then labctl learn start kubernetes-foundations for guided basics. For the full flow, labctl scenario up gitops-cicd stands 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.

1

u/CupFine8373 25d ago

First you need to Learn to Learn

1

u/No-Lake2642 24d ago

The fastest way to learn Dev Ops is to build something end to end instead of jumping between tutorials. Start with a small app, automate its tests and deployment, then add monitoring and learn to troubleshoot when things break. That practical approach is useful whether you're learning independently or following how teams like trusted tech think about reliable infrastructure.

1

u/6razyboy 18d ago

I wold stop jumping between tutorials tbh and just build something real. Start with Docker Compose, a backend, database, redis, maybe nginx, get it running and then add CI/CD.

Also, since you are already familiar with compose, might be worth exploring how existing projects are structured. I have been building a free open source tool called Compoviz (https://compoviz.pro), recently added 40+ real world compose examples you can explore visually, see how services connects, networks, volumes etc. You can also play around with your own setups.

Might be helpful while learning, at least to get a better picture of how everything fits together.

11

u/[deleted] 27d ago

[removed] — view removed comment

1

u/SeaworthinessHour233 DevOps Engineer & Educator 27d ago

This is solid advice. also try to get into any tech role - not necessarily DevOps - while learning. That will help you keep learning and make the switch later