 Larry, thanks for calling me back. I want to talk to you about GitLab, but right now, all my developers are using github.com, and they really feel the power and the convenience of it. Considering going to GitHub Enterprise, because we feel it'd be something just like an internally hosted github.com. And part of this is we'd like to consider it as a way of saving time for a learning curve for our developers. What can GitLab do for me? Yeah, so, John, that's a point is well taken. Going from github.com to GitHub Enterprise. Certainly, on one hand, does reduce the amount of retooling that might be necessary. But to go from ideas to production is more than just version control. That said, let me ask you, what does the ecosystem currently look like from workflow from ideas to production? That's a great question. We're using JIRA as our issue tracker, and we're using Jenkins as our CI tool. OK. So when we talk about going from ideas to production, as you can see, it's more than just github. And in your case, it's github. It's JIRA. It's Jenkins. And there's probably an incendiary amount of other tools and processes that are necessary. A big challenge, and I don't know, John, if you're confronted with this. But what we hear from our customers is there's a tremendous amount of complexity in having our customers have to stitch together an ecosystem of disparate tools to comprise and to become that workflow. And when we talk about stitching, we're talking about configuring. We're talking about integrating. We're talking about administrating. We're talking about securing and testing and maintaining over time. These are some of these products Jenkins specifically can, the plugins become quite heavy and can actually become quite brittle. Now, is this an issue for your organization? That's actually a great point, Larry. We actually have a dedicated administrator just for our Jenkins server. And you're right, keeping it updated with all the updated plugins, JDK versions and all that, it is becoming an issue. There's no question. One of the trends that we see and in fact, Forster recently wrote about is the paradigm shift towards away from these centrally managed and Jenkins environments towards, more towards a self-service model, empowering the development community so they can get more done. So on one hand, we're gonna bring more functionality to bear, but the beauty here is it's all contained within a single code base. It's a single database. It's a single UI and as a result, on one hand, there'll be incremental learning, but over time, that learning is going to be minimal in line of the value and accelerated delivery that ultimately that you would get from a single platform because at this point you've removed complexity. So I guess my question for you is, is this an issue for you today or is the environment quite secure and quite consistent? No, that's another good point as well, is securing all these environments for our users is definitely being a challenge for us. A single integrated platform is something that sounds very interesting to us. So then let me just get back to your question. You're concerned about the retooling that would be necessary and that is the learning, okay? And understood, both platforms are based on get. So that learning would be minimal, but you're getting a lot of new functionality as well and you're reducing the amount of time that it takes to stitch together the environment. So let me summarize. What GitLab ultimately will give you, John, is a single code base, a single environment, a single platform to go from idea to production. And as a result of that reduction in complexity will truly reduce cost and it will accelerate value delivery and predictable. So that's really what you're gonna get at the end of the day. What do you think of that? I think that sounds great. We should talk further about it. Okay, sounds good. Thanks, Larry.