"DevOps" is so often misunderstood, many companies who think they're doing DevOps are actually doing one of these anti-patterns.

Unless literally work alone, you will experience workplace politics. The question is: is it abusive?

We can count retrospectives, but that feels like a vanity metric. How do we know if we're actually improving?

Even in the manifesto, the word "agile" is used as an adjective, not a noun. I think this clarifies the meaning significantly.

Abhinav Dhasmana joins the adventure to discuss how he got Kafka to scale to handle thousands of messages. He explains how to scale Kafka up and how to allow applications to scale with the messaging architecture provided by Kafka.

In the best interest of the IT system as a whole, optimize for the engineer's time, since that time is expensive.

In this episode, Daniel Bartholomae, CTO of Optilyz, "borrows my brain" for a consultatative discussion about how to improve the integration of QA in a growing startup with just two dev teams.

What if you're in a business where you know all the requirements up front, you do not need to respond quickly to change?

In this short, Halloween bonus episode, I talk about a very scary technical screening process I learned about just a couple of days ago. I explain why the screening process is scary from the perspective of both the candidate, and the hiring manager.

I recently created an 8-minute video where I walk through my daly routine of writing one of these emails.

DevOps is usually viewed in the context of large organizations. But what does DevOps look like in small organizations? Does DevOps make sense in this context? Is it even feasible?