 So, what I'd like to do now is I'd like to invite someone who can spend a little bit of time talking about with me how their organization is using Cloud Foundry, frankly, at a very high scale, doing very important things and running their business on Cloud Foundry. So, I would like to invite Chuck Nosman, the Vice President of Digital Technology and Services and Strategy at T-Mobile. So, Chuck, come on up. Hey. Come on over here. All right. So, Chuck, thank you very much. Appreciate you coming. Yep. We had a prep call a couple weeks ago, and it was a very, very simple conversation. I said, you know, are you using Cloud Foundry at all? They said, yeah, a lot. Yeah. Yeah, a lot. So, maybe you could tell us a little bit about the journey that you went on. Yeah. We, well, first, I'm going to talk a little bit about T-Mobile just to set a context. We are at 73 million customers now. We've doubled in size in the last five years. We're changing the way we do our customer service, retail, expanding our network, 5G is coming, and we're doing IT transformation and IoT as well as it's coming as well. So, you're a startup? Yeah, we're a startup essentially with 73 million customers. Great. So, yeah, so our journey actually started, it was funny, we had a whiteboard session with James Waters and Aaron Hire from Pivotal in 2015. We're talking about 12-factor applications at that time. Cloud Native didn't quite resonate at that point in time, but 12-factor applications, how we should be refactoring our stuff and didn't believe them, right, came to the Cloud Foundry conference in 2015, saw the vibe or felt the vibe, saw all the participants, all the smart people that were utilizing the platform or getting on the platform, and that was really the catalyst for us taking off. We laid down a foundation, trained a lot, we had Cornelia Davis come in, was one of our first trainers from Pivotal. We started with a middleware application or a service, if you will, that was right in the heart of what we were doing to prove this stuff out. Sure. So, I'm sorry, just to, I want to make sure I understood that, so you took the hardest part, the most important part, you started that? Yeah, we tried a lot of things on the external side of the ecosystem, and they would work because they were standalone and off on the side, but we never get scale off of them. So we decided we were going to go right at the heart of this stuff, get customer, get subscriber information, and start with that one. And if it worked, awesome, or fail fast, right? And it worked. That's great. And then, so, we started building things out over 2016, 2017, about June, we were at about 1,000 containers running, by the end of the year we were at 12,000 containers running, and right now we're at 18,000 containers running on the platform. Well, that's really successful. Yeah. How many developers are working on it? 1,700. About 1,700 right now? Yeah, 1,700 developers on the platform right now. Wow. That's amazing. Yeah, what's really transformed for us is, you know, we're at peak during the day, we're about 10,000 transactions a second on the platform. Heart of everything we do, activations, upgrades, payments, loans, leases, everything coming through comes through this platform. But at the same time, we're doing about 30 CF pushes a day into that environment at the same time, and all that's happening. And it's been actually spectacular for us. That's really amazing. What's been the hard part? Is the whole thing? Of the whole transformation thing? People. People. Okay. Well, yeah. I mean, you get used to doing things a certain way and to change and have that leap of faith or that step, right, is a tough thing for people to go through. And once they did, it just caught on like wildfire. We have a great set of infrastructure people, developers and ops guys that really care about our customers and T-Mobile, and it just took off. Cool. One of the things I like to always understand is when an organization gets to as many applications and containers and as many developers being supported as you have, what's the operations look like? Well, on the platform itself, we have, I want to say, 7 to 10 people that operate that platform at that scale. So we have nine foundations, I think, externally facing. They have three for themselves that they play with. But think about that. We only have 10 people operating a platform of that size where we used to have hundreds, right? Absolutely. But from that perspective, then the operations teams are working on telemetry and truly getting into that DevOps mode, telemetry and making sure that things are working correctly. Blue-green deployments, canary deployments are all enabled by the platform. Is there any... So one of the things that strike me is when you get to a platform operations team that's as small as you just described it, servicing as many developers as you have, it seems like it would be an opportunity for some of that operational experience to make its way into the development teams. Well, it's kind of funny that what was our operation teams before are loving this because they have someone else that operates all the hardware, everything else that's down below and they can focus on just helping those apps run, right? So you get those operations guys that are working really tight with the developers and a lot of good things start coming out of that. A lot of automation starts coming out of that and it just starts feeding on itself. Yeah, that's pretty amazing. Yeah. I mean, one of the key things that generally happens in software development teams, when they're using Cloud Foundry, we tend to like peanut butter and jelly go really well together with agile development techniques. Yeah. Has that been adopted as well? In many ways, agile has come to fruition. We're still pushing for it. We still have a lot of big legacy monoliths out there that like to work in the waterfall state, big drilling systems, SAP systems, sorry, and other things that are out there that we're constantly trying to get them into that agile mode, if you will. Yeah. Well, that makes sense. I mean, it's a process of changing. Yeah. So the teams that do use the agile techniques, maybe do pairing, maybe don't, are they maybe the most prolific releasers, or do you see that maybe the more traditional development also working very well on top of Cloud Foundry? Sorry to say that again. Well, does it require agile development to work well with Cloud Foundry? No, it really does. I mean, when we started out, we weren't, we didn't have really sprint teams and all the other, you know, the strict ceremonies around agile and all that. We just kind of went in and did it, right? The teams kind of formed around that. What agile really brings to us is that prediction, right, the two-week, the thinking around two weeks instead of project-based, you know, six-month cycles and things like that, it really helps us to iterate through stuff very fast. Very cool. So you said back in 2015, you went to the first Cloud Foundry Summit and, you know, you kind of inspired by the community. So maybe I'm going to give you an opportunity here, because I'm sure there are a couple of folks that are contemplating whether they're going to take this journey. What would you tell them? Yeah, ask a lot of questions. This stuff is real. It does work. I mean, we are a pretty good poster child, I think, along with a Comcast and some others that, at scale, this stuff really does work. I would really focus in on the infrastructure platform side of things. We, like I said, we had a great infrastructure platform team. That team evangelized really well with the, train those developers, train those operations guys, put the automation on top that really, really does matter. And then the last thing is make it frictionless. DevOps teams hate friction, and so make it easy for them to get on the platform and all the value will start to come out. Outstanding. Outstanding. Well, Chuck, thank you so much for coming. Thank you, Chip. Appreciate it. Really appreciate you coming to talk to everybody. So that was Chuck. Thanks, guys. See you mobile. Again, small startup.