Coder on Changelog Master Feed

Okay. Let's do this. Well, friends, this episode is brought to you by our friends at coder.com secure environments where developers and agents work in parallel. And I'm joined by Nikki Pike, field CTO for Coder. Nikki, what is a field CTO? So I get that question a lot, and it's, you know, half the people understand it, half the people don't. So a field CTO, I describe it very simply as we're DevRel for the c suite. So we provide a bridge between the customer voice, between the the c suite and the the managers and the leadership teams of our customers back into our product, and then we go through and we help enable our teams to to have the same message to make sure that the message is correct and that we're building on something that people actually want, not just something that we think they want. Okay. So we're taking the laptop away from the developer. Not really though. We're putting them in a cloud development environment, a secure environment where they can work with their agents. In parallel, these are blessed environments. What's wrong with the laptop? The laptop is the is the trap here. And not only because the fact that it could be stolen, you could lose it, it breaks, and you're out of work while you're waiting for a new one, but there's also just the consistency that you got there. We all know developers. Developers are gonna be looking for some of the latest and greatest. And if you're not really controlling how they get out there, that's where you get this. It works on my machine. It doesn't work on in production. It doesn't work anywhere else because you don't have that consistency. You don't have that ability to really standardize what that environment looks like. And this is a problem not only for new people coming in. You know, the onboarding statement is average, I think, is like four to five weeks for a new employee to really get their their local laptop set up and ready to start doing their first time of code. And, you know, the time to first commit is a metric that almost everybody knows. And the reason they can't do that is because there's a lot of tribal knowledge out there. They gotta go talk to other developers. What are we using? Where do we get our dependencies? Are we getting them from public? Are we getting them from private repositories? But there's also the security and the supply chain aspect of this. When you have local machines out there, look at, like, the Shai Halaad, you know, that virus that went out not long ago. This was a compromise of the NPM public repositories. They went and downloaded things. NPM did what it did. Next thing you know, you you're compromised. But when you use something like what we're doing with cloud development environments, then you can mandate and you can put restrictions on there to say, hey. You can only go get your packages from our private repo. Those packages are expected to have been thoroughly vetted. We know that they're clean. Now does this stop everything like Shay Hled? No. If that compromised package gets into your private repo, you can still have that, but it really reduces the surface area of the attack, and it also reduces the blast area of the compromise should it happen. Because if your laptop gets compromised and you have to kill the laptop for whatever reason, that's weeks out of work while you're either fixing that or you're getting a new laptop in. The cloud development environments allows you to kill that, start back up fresh, and you're back and running in in in five minutes. You don't have to wait all that time. Well, friends, the first step is to go to coder.com, install Coder, self hosted environments for your teams to enjoy, to standardize around, and it's open source. So you can try it out today. Once again, coder.com.