JS, what do you think is going to happen next? What are your thoughts on, like, kind of how the DevOps world is changing and evolving? It's interesting. Patrick just shared a tweet of, like, all the DevOps flavors of the industry and it's just, like, it's scary because it almost looks like the CNCF landscape. You know what I mean? There's so many words describing similar things or different things, and we just, like, keep expanding the levels of concern in all these different jobs.
I think, like, so if I look at, like, ten or whatever, 2009, 11, almost twelve years ago when the whole DevOps movement started, like, sometimes I ask myself a question, like, did we make the world better? And I think we did, right? And we continue doing that, but, like, continuing, like, if you think about the job of the operator versus the job of the operator today, I think the operators work on way more interesting challenges, which, like, you know, instead of clicking buttons and doing the same thing over and over again and worrying about, I don't know, backup tapes and stuff like that, we now, like, have operators implementing kind of, you know, basically writing code, which is, like, it's terrible for me to say that writing code is the coolest thing, but, again, like, we basically solve more interesting challenges. It's also, like, the world has moved on, right? Like, 10 years ago you could have an outage for the entire Saturday while you're moving your app to a new version, and today, like, there's no business in the world for which it would be acceptable to just, like, be like, oh, we're off for maintenance for an entire day. Like, that just doesn't work anymore, right? So you have to kind of adjust your technology to everybody's expectations, essentially.
I think in terms of coming to the frontend, I don't know. I think the expectation should be that people should be able to work on delivering business value as opposed to worrying about implementation details. And that's where, like, maybe we should come full circle and be in a sense where, like, you can click a button and then you'll get a container or whatever it is or a function or you don't even care about implementation details, right? I get a container of this, you know, type, and I can run my app in production and all I worry about is code, right? And that's just, like, I feel like that's the ideal state for, you know, developers to be able to be effective with their job.
Yeah. In the context of that, right, that's often been the promise of, like, kind of past platforms like OpenShift that talk about, like, kind of from ID to production. So it's interesting how they kind of, yeah, we are coming full circle around to that kind of a model again. Yeah, there's, you know, like one last just question to wrap up your talk is what are the checkpoints you set to make sure your pipelines are working as expected? Is there any, like, quick tips on that just to make sure that people have themselves covered? Yeah, I mean, there's multiple, basically, checks that you can show and, like, if you have the technology configured properly, you will have gates so you can actually, so continuous delivery doesn't mean you always automatically go into production, right? So ideally, you have a checkpoint after you're checking your code and you have a checkpoint after you build it, you have a checkpoint after you run tests and you can have multiple of those because you can have multiple types of tests, essentially. For these types of pipelines, you have a checkpoint when you're checking the image into the container registry. And then basically, the checkpoint where you check it out and then, deployment is a whole other thing where like once it's deployed, you have to also take care of monitoring and stuff like that. And then usually now, it's a lot of times when you're checking into source control, but you definitely need to run security checks, right? And again, security checks can be at multiple stages as well, right? So you can run site code analysis, and then you can run security as part of your tests. And then you obviously mentor security once it's deployed. So there's a whole lot of different things. I think, basically, you kind of go and chip edit at, you know, leverage the things that are free and easy to implement first, and then like that already puts you ahead of a lot of companies. And then kind of start looking at different tools that can allow you to make sure your applications are secure and functioning well. I think security is one of the things that is often missed when people are worried about speed of deployment so much.
I couldn't agree more. Thank you so much, Sasha. It's always a pleasure and honor to have you. Join Sasha in her speaker room immediately after her talk and on the Spatial chat. We'll get to chat with her and network. So thank you so much for joining us, as always, stellar talk. Big thanks. I'll see you soon. Take care.