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).

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

Most of us don't need thousands of nodes, geo-redundancy, or even blue/green deployments. Is your chosen solution that fixing your actual problem, at your scale?

I've grown tired of the constant bickering about Kubernetes or no. But this article is more an informative case study in the viability of one alternative.

By solving the problem of reducing communication overhead, we often also provide shorter feedback loops, and automate toil away.

IaC can be complex, but it doesn't need to be. Start small. Start with the tools you know today.

In this episode, Zachary Randall of Chameleon Collective talks about his success using serverless technology to help understaffed technology teams save money on hosting fees, and reduce the complexity of maintaining infrastructure. He also plays the guitar for us.

Guest Patric Conant discusses the dangers of ignoring low-level infrastructure during a DevOps transformation, and some simple steps to avoid this common blind spot.

How can we discover conflicting changes on separate branches as early as possible?

The Mikado Method is a system of quick, iterative experimentation for rapid and safe code changes.

The twelve-factor app is a methodology for building software-as-a-service apps