Reliability results require visibility & accountability

Reliability doesn’t just happen if you build a good tool. It takes visibility and accountability to get results. Find out how to be reliable at scale with Gremlin → https://www.gremlin.com/

FULL TRANSCRIPT:

 One of the things I've observed over the last 10 years in the software engineering culture is this idea of kind of Field of Dreams DevOps. If you build it, they will come. And there's a lot of this in the developer tool space in particular. "Hey, if we just build a great tool and we make it easy to use, engineers will use it because they want to do the right thing."

And I think that's a great intent. But the truth is people are very busy. Their time is split. They have to prioritize. And so the analogy I draw is with security. With security, we don't take this, like, laissez-faire, "Hey, if you can get to it," approach. We have pretty strict requirements. We have a set of criteria that have to be met. If a certain type of vulnerability arises, it's a drop everything and fix kind of vulnerability. And part of what makes that effective is the visibility and the accountability.

That comes from leadership. The truth is, if we don't have good visibility into what's being done, then we don't have the tools to make sure that that work is getting covered or to reward folks for the good work that's being done. Security is a must have, not a nice to have.

And if we know there's things out there that are putting us at risk, we drop everything to go fix them. We need that same urgency and accountability around reliability.