 I love chat ops. I love chat ops almost as much as I love chili dogs. As you can see here, as you can see here, one of our engineers also loves chat ops. It's been very transformative in terms of where we've gone. We talked a lot about change agents and transformations yesterday in the open spaces. I would say you don't have to be a person to be a change agent and we're going to explore this concept in a couple of ways with onboarding and with friction. Okay, so chat ops, we talk a lot about chat bots, chat clients, et cetera, very necessary, but I would also say that collaboration and people is the true power of chat ops. A while ago, we had a team builder at Topgolf. We also had a storage migration that was underway. So this engineer decided not to miss out on the team builder and he built the tooling and telemetry that way we could all monitor the storage migrations. Onboarding, so the key thing here, definitely bring it on new folks to your effort. Don't have to be new timbers, two members. It could be new teams that want to participate with your process. Confession, we totally ripped off the Etsy day one deploy idea. So don't tell John Osbob, but essentially our last four engineers have all developed and deployed new scripts on their first day of working. Great thing about that is not only do we reinforce that we're really excited to have them on the team, but we also, they're committing from the get go and they have some great stories for ex-co-workers about the cool stuff that we're doing. We chose to abstract a lot of the complexity away, so we built a wrapper process to wrap PowerShell scripts. That way we can make it less intimidating for people to get on board. You can eventually build up the coffee scripts when you're ready for more features. ChatOps is really a gentle introduction to our stack, so as we're working with new members, we can kind of talk through the concepts around CICD, DevOps, other ideas, and we can show them how their script is shown up in the production environment. All of us have a ton of friction in our environment, whether it's organizational debt, technical debt, other friction, and I think ChatOps really helps to identify the source of that friction that way can do something about it. As we started to work across silos, we ran into a number of permissions roadblocks, and ChatOps was great to kind of shine a light on those that way we could actually do something about it and make our automation run better. In the early days, our lead engineer would have to run around from desk to desk, debugging PowerShell modules, RubyGems, et cetera, and the combination of ChatOps and Artifactory dramatically stabilized our environment as well as helping us gain momentum. Think about ChatOps as training wheels for your organization. You can actually use it for crawl walk run, pairing sessions to help members gain intuition for how to work in your environment. One of my very favorite things about ChatOps is context, you get stimuli, you get discussion, you get action, you get outcome, all tightly coupled, and it's something you can go back and review at a later time either through retrospectives or other things. ChatOps has definitely helped us to work in a more decentralized manner around the world and also build engagement and empowerment and decentralized teams. ChatOps necessarily cuts across your organizational structure, so we've been very happy to see spontaneous collaboration and new patterns of teams working together that wouldn't have worked together otherwise. As we did ChatOps, we wanted to do more ChatOps and that really encouraged us to bring out any scripts that we had laying around and get them into our repo and every time we check into a repo, the organization automatically gets smarter. We talked about the GitLab postmortem yesterday and how transparency builds empathy, trust, understanding, the fact that you're in a shared console, you can keep an eye on one another, you can help each other, you can coach each other, and it's a great thing. So we talked about day one deploys, we talked about people going outside their comfort zone, we talked about new collaborations. That's only possible because we have guardrails that make it safer to go fast, safer to experiment and innovate. We talked about columns yesterday, so culture, automation, lean metrics and sharing. I believe that ChatOps really touches the heart of all of that and it's been a very useful change agent in our DevOps journey. All right, give it up for Scott, thank you.