"What is the RGB color code for yellow?" and other actual questions I actually got during the worst SRE interview of my life.

My critique of the DevOps.com article "Yes, You're Doing DevOps". Spoiler alert: No, you're not doing DevOps (according to the reasons in the article).

Jonathan Hall joins the Adventure this week to discuss the advice he gives to clients to start continuous deployment before they have automated tests around their code.

There's no one-size-fits-all solution to all testing needs. Ephemeral review environments are great, but they don't solve all problems. Most teams will also want a long-lived staging environment, too.

Regadless of how much automation you have (or don't have), if you have hand-offs, you're not doing DevOps.

When Scrum was formulated, it was seen as a “wrapper” for more technical agile practices, such as Extreme Programming. A conscious choice was made to focus on the relationship between software developers and management. It was assumed that Scrum would be used to promote more technical developer practices, which Scrum leaves unaddressed. DevOps not only works hand-in-glove with Scrum to fill in these missing gaps, it is more and more seen as an essential tool for Agile success.

Perl, Java, C++ are as hard for novices to read as a randomly designed langauge.

Simply adding a linter to your build pipeline is usually the simplest, cheapest single step you can do to improve code quality.

The purpose of metaphor is to communicate. So use a metaphor that helps you best communicate in the moment.

We automatically created a test environment for every pull request, and it had a revolutionary impact on the development process.

As usual, the biggest obstacle to Continuous Deployment was the fear of losing control.