Getting Into DevOps.

Are you a developer that’s interested in infrastructure? Are you a sysadmin that thinks that writing software is cool? Are you neither but think that systems and software are is fun?

If so, this talk will give you some pointers on how to “get into DevOps.”

I’ve observed a sharp uptick of developers and systems administrators interested in “getting into DevOps” within the last year or so. This pattern makes sense, too: in an age where a single developer can spin up a globally-distributed infrastructure for an application with a few dollars and a few API calls, the gap between development and systems administration is closer than ever. While I’ve seen plenty of blog posts and articles about cool DevOps tools to use and thoughts to think about, I’ve seen fewer content on pointers and suggestions for people looking to get into this field.

My goal with this talk is to, hopefully, draw what that path looks like. My thoughts are based upon several interviews, chats, and discussions with many developers and systems administrators. First, we will discuss a brief, anecdotal look into the world of IT prior to the ideas behind DevOps taking the world by storm. We will also explore what hiring managers looking to bring DevOps into their companies are looking for and skills that are helpful for engineers looking to become DevOps champions. Lastly, I will outline common implementations of DevOps concepts that I’ve seen in the industry, along with some helpful books that discuss the ideas behind this post in more depth.

This talk is based on my blog post here: https://www.thoughtworks.com/insights/blog/getting-devops. I’ve “done DevOps” for most of my career at a bunch of interesting places (Google, Jane Street, Namely). Check out my resume here: http://resume.carlosnunez.me