How many people are on your team? How many of them look like you? Do you have a Star Trek team?

Not everyone feels the need for your solutions. That's okay. You don't need to convince them.

Will and Jonathan have a conversation about whether or not you can use Scrum with DevOps.

The panel puts their heads together to talk about how to bring DevOps practices into a work situation based where they're not implemented. They discuss the various pro's and con's of specific practices and how to get people on board with adoption.

After we find land a first job we learn that correct answers often often technically inferior solutions, answers, or proposals win the day. Why?

"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?

Change is hard. We're more receptive to change when we're facing crisis. How can you change to face a crisis effectively?

If your application relies on serverless functions, often there's limited opportunity for "from an airplane" work.

Doing DevOpsy things begins to transform your culture for you.

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.