It looks like I've linked you here myself. Linking people to a blogpost I wrote is often a bit akward, especially at work.
I likely shared this blog in an attempt to further a conversation. Usually the post does a better job at succinctly sharing information than I could by talking.
In any case, I hope me sharing this post doesn't come across as humblebragging, that's really the opposite of what I'm trying to achieve.
Thanks for reading!
DevOps is a buzzword - few will deny that. It’s used left and right, meaning different things to different people. There are plenty of good general introductions from folks that have done that far better than I ever could.
So instead of repeating that, here’s a few thoughts and resources I’ve discovered and used in the past years.
Some of my favorite learning resources:
Linux requires a special call-out. Without Linux, no DevOps in its current form or perhaps at all. While the former doesn’t the require the latter per se, truth is that many DevOps techniques and technology are just applications, abstractions or integrations of Linux concepts and primitives. So learn more about Linux, and everything else will become easier and better.
Here’s a few excellent resources to learn more about linux:
Note that being comfortable around the command-line is only the entry point to “knowing linux”. Here’s a few topics I recommend researching in-depth:
When it comes to Linux, there’s always more to learn. I can easily get lost for hours on these topics, and it’s some of the most interesting and rewarding learning I do.
Make sure you don’t just read, but take notes (build a digital brain!) and actively experiment. Do it in the open so you can share and showcase it easily.
Too often, people understand the core ideas and practices behind DevOps, but miss nuance and depth because they haven’t spend time reading some of the source material. It’s telling that some of the most experienced practitioners keep referring back to the following books. You won’t regret spending time on these, even if it’s just skimming them.
Keeping up with new developments is critical to stay relevant, especially in our industry. What was state-of-the-art two years ago is now considered The New Normal, and will be referred to as legacy in four years from now.
Here’s a few ways to keep up with latest developments in the DevOps space.
I usually only attend 1 or 2 conferences a year but regularly browse conference schedules and pick out topics for researching. I prefer to browse slides or do separate research rather than attending in-person or watching video recordings as it allows me to tailor and optimize learning time.
Here’s a few DevOps-related conferences with interesting schedules: