DevOps 101

Courtesy: Personal Archives of Jedi Knight Obi-Wan Kenobi

Whenever I’m studying for something, I have a habit of writing out my notes in full as if someone else were going to read them. It’s not because I think anyone ever will read them; it’s because I only have two modes of note-taking:

  • I can be a polished author, writing in full sentences and carefully formatting things so that it’s well-presented, and somewhat aesthetic.
  • Or I can write in the shortest of short-hands, like I’m an ancient scribe and my ink is worth more than I am: I’ll use half-words and abbreviations that I’m likely to forget in a few days. I’m not really capable of doing anything in between: my notes are either Hemingway or they’re “Obs: mtrc, trc, lg!”

Obviously once I go to review my notes, one of these forms is far easier to read. So, I tend to tell myself that I’m writing for someone else in the future who will need these notes.

Which is how we got here: I have a small corpus of notes that I took a few years ago as I was reviewing basic DevOps principles. I don’t know if they’d be useful to anyone else, but I figure I might as well publish them.

This isn’t a comprehensive resource. As it stands, it doesn’t do much more than touch the surface of each topic. I’ll include links to books, courses, articles, videos, and whatever other materials I can find to supplement your learning. I’m not, however, going to link to anything I haven’t used myself, so it may take some time to fill out the recommendations.

Also, I have deliberately avoided discussion of specific tools, except in a few places (for example, Infrastructure as Code) where I felt it was important to the subject to have a surface understanding of the types of tools.

So get reading some of the substance! I’ll publish new pages as quickly as I can get them cleaned up. Here’s what we have so far and what I expect to cover soon.