DevOps Career Accelerator Series
github.com
github.com
Literally this is almost verbatim what is present in the Getting Started page from the official Docker docs:
In a way the Docker part of this is just a prerequisite to get to Docker Compose. I've found that once people understand the compose part they start to see the bigger picture and get some curiosity about networks, databases and configuration which is not as easy to intuit from a single Dockerfile.
Also this whole tutorial is just one lesson in a much larger email based mini-series on DevOps: https://miniseries.opscentric.io/devops-career-success The progression in the series makes more sense than the standalone lesson.
Someone interested in "leveling up" their DevOps career is intimidated by official documentation... and more comfortable with github?
Seems like a stretch to me.
I suspect you are like me and prefer to just read the docs and learn on your own. But there's a huge percentage of people that don't learn that way and need more hand holding at first. There's a reason that Youtube videos are so popular for learning technical subjects. I would never watch a video to learn anything technical myself yet millions of people prefer it over reading.
What I'm doing is based on experience of what works to get more people started and interested. Not everyone is an OG hacker who's been programming since they were twelve. If you are that type like I am, this is not for you as you can learn it faster on your own than you can read the tutorial. This is for those who are less experienced and might be intimidated getting going.
I generally agree with:
>"Successful DevOps practitioners don't get paid to write code or configure servers. They get paid to solve problems."
However, I'm curious how your miniseries ties this in. You're starting with what is, ostensibly, rote technical knowledge. How do you convey/teach things like:
- navigating abstract problem spaces
- owing deliverables to cross-team non-technical stakeholders
- responding to severe outages in highly complex, large-scale distributed systems
- designing operational processes to make said outages easier to deal with
Skills I've generally found incredibly important to have, but hard to teach absent the experience of dealing with them in the first person.