Cris (00:00)
Founders should understand the importance of cloud operations. that it’s not something to be put off until later. When done properly from day one, it becomes an accelerator. That doesn’t mean that it’s not possible to over engineer upfront. And there’s a balancing act that needs to be respected. So it’s helpful to work with providers and partners that understand how to build just the right infrastructure and just the right operability into that infrastructure,
so that it becomes something that speeds development. It becomes an accelerator and not an impediment. Chasing security too early, chasing high availability sooner than your customers are expecting it. These are things that can be a distraction. Making sure that you have excellent backups and a deployment procedure that can be rolled back from so that if you have a release that goes out and is negatively impacting your customers, you can quickly recover. That’s really important.
We have a lot of founders who didn’t prioritize cloud ops and they came to us with every time we need to do a rollback, takes half a day. That’s not acceptable to especially customers that are early adopters. They took a risk because they had a really compelling need. And if you’re down, you’re not solving that need for them. If you’re down and not solving that need for them, either they’re heavily impacted or they’re having the realization that they don’t need you as much as they thought they did. Neither of those is a good look
in your early stages. CloudOps needs to be respected, and it needs to be integrated into the earliest phases of the product, but it also needs to be done in a way that’s not over engineered.