"Testing" and "checking" are two different types of activities. They deserve a distinction.

When test writing is removed from code writing, there's no observed benefit in IT performance. Writing tests in a silo is an anti-pattern.

Is QA a separate stage in your software development pipeline? This is a "smell", an indicator of deeper problems.

CD leaves room for manual approvals, but once approved, all changes should be applied automatically.

I got a few complaints from developers who didn't enjoy splitting focus between dev and testing, but they admited it was better than before.

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.

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

The Toyota Production System's U-Shaped Cell is a favorite DevOps analogy: Put all the tools within reach of a single developer.