The hero is the one who stays until 8pm when customers can't log in.

Think of the time you released software to production...

One of these skills, if you're good at it, diminishes the need for the other other.

Of course, as a consultant, I can confidently tell you: It depends!

I had failed to complete the "refactor" part of "red/green/refactor" several weeks ago, leaving me with some redundant tests that came back to bite me.

A philosophical conversation around building code more responsibly and how ethics and accountability is to be integrated into the DevOps industry.

Software delivery is a lot like traveling. Less luggage makes for a better experience.

The "observation" that fixing a bug in production costs 1000x more than fixing it during design assumes a waterfall approach.

Is any failure to meet user expectations a bug?

Rather than seeing code review, or QA, as a gatekeeping process, let's frame it as an opportunity to elevate the output of the entire team.

Who is responsible for unit, integration, and acceptance testing? Developers.