Devops

A path to DevOps When Lara Hogan asked Bridget Kroumhout (on stage, at Velocity), "So, how did you get tricked into operations?" it was funny, but it got Kroumhout thinking. It's a question she's been asked before, and has sometimes been at a loss for an answer since she didn't follow a plan originally. Kroumhout now offers a plan-a wonderfully thoughtful and pragmatic set of resources beginning with culture (e.g., if you work in tech for even a little while, you'll notice that you have a lot of social and economic privilege, no matter your demographic identity, because you have more choices in your work and life than do many of your fellow humans), tools, education, community, and how to launch your career. Even if you're already well established, this is worth a read if only to rekindle your fire.

This checklist is comprised of 48 items you can use to gauge the maturity of your software delivery competency, and form a baseline to measure your future improvements. It's not meant to say "you're failing DevOps" or deprive you of a badge (make yourself a badge just for reading this!), but surface areas of potential improvement.

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

Until recently I was not able to clearly articulate what DevOps is. Then one day, when trying to describe what we are building at Nirmata to an investor, I said something to the effect of, "its all about enabling developers to perform operations, using automation". That made sense to them; and, I've since started using the following definition for DevOps: Developers doing Operations using Automation

DevOps Knowledge Base - This knowledge base includes topics of: Software Configuration Management, Continuous Delivery, Infrastructure Orchestration and DevOps

We have a variety of tutorial videos all related to DevOps. Our goal is to make the lives of SysAdmins everywhere easier by helping them use the tools that developers have been using for a long time, as well as helping developers realize how to solve some of the issues that Operations has traditionally had to deal with. If you have any comments or suggestions, please let us know!

A list of software and SaaS, PaaS etc offerings that have free tiers for devs