 Hi, my name is Brad Bazemore. I'm the lead product manager at Red Hat for Red Hat Developer Hub. Today, I wanted to show you Developer Hub from the perspective of a developer. Before I was a PM, I was a developer, and there was a lot of pains and a lot of things that I was frustrated with all the time. And I think the biggest one, the thing that I want to talk about today is what happens when you need to get started. So let's say you've been tasked to start a new project, create a new microservice to do something, maybe handle a new API, maybe work with a new database, whatever it may be. One of the biggest frustrations that happens right away is just getting it up and running. You got to go find permissions over on this side, file a ticket here. Does anybody know where this actually lives? Hey, I wasn't able to elevate this. I need to get this to management. But management doesn't even know how to reach out to, do we use Argo for this? Or are we supposed to use something different? Hey, what version of Quarkus are we running on? Is there a repo and on and on and on and on it goes? If you're lucky, your company has this handled for you. But too often, even if it is handled, it's fragile and frustrating. So I want to show you how Red Hat Developer Hub tries to make that a little bit easier. So if you didn't know, Developer Hub is built on backstage. And one of the core philosophies of backstage is what's called software templates or golden path templates. And the idea is that, quite frankly, if we make it really easy and self-service for a developer to follow best practices, they're going to follow best practices. It's going to unblock them and help them move faster. So let's go back to that example of needing to spin up a new Quarkus service. Let's see what that might look like. Well, with Developer Hub, I'll simply click Create. Here, I'll be taken to the available golden path templates. Now, for me, I know that we want to use Argo and Tecto. So we'll use the one here at the bottom. Click Choose. Great. Now I've just got some basic information to fill out. And unlike a classic ticket system, it's not going to take me forever to figure out because this was designed just for me. So I've got some good defaults here. These make sense. And for the image registry, I'm going to say OpenShift. And for the application repository, we'll use GitLab. And that's correct. All right, that looks good to me. Let's get started. Once I hit Create, the golden path template will take care of the rest. It will execute and get everything started up following the processes that generally the developer engineering or DevOps team has set up. That's the best practices for doing this. It's going to build everything I need, create the repository, set up the code and add it to the catalog. So if we click here in the catalog, there's my Quarkus app. Click on this. And now you can see everything I need is there. We've started to pull images for Kubernetes. So that'll take a second as Argo CD kicks into gear. And we have OpenShift topology in here once the application gets spun up. But this is getting spun up correctly the way it needs to be. So sure enough, here we go. Application got started. Now we already found a problem right away. The Quarkus app isn't being deployed right. And that's my bad. I shouldn't have used the OpenShift registry. I should have used Quay. But if tech time was set up, we'd have that here. Kubernetes, we can see that information. And clicking right here, taken straight to the source code that's already been set up. So now I have a blank Quarkus service following my company's brass practices deployed into our server systems ready to go. Just as simple as that. This is just one of the many ways that Red Hat Developer Hub makes the life of developers easier so that I can do what I'm supposed to do, which is just develop. If you want to learn more, you can email rhdh-interests at redhat.com or go to developers.redhat.com. Thank you.