It's time to rethink how you've been developing...

Cloud-native apps need cloud-native development
We've seen a tremendous change in the way applications get deployed over the last five years. From huge monoliths deployed on self-hosted infrastructure, almost everyone seems to be moving towards a microservices-based architecture deployed on Kubernetes clusters. And for a good reason too!
Cloud and Kubernetes significantly simplified the deployment process and reduced the headache of managing deployment-related tasks. But while we've been busy rushing towards modern deployment practices, I think we forgot to stop and take a look at how we've been developing all this time.
Our traditional ways of development were okay for the traditional deployment methods. But, a change in deployment practices does demand a rethinking of development practices - and it's for the better too! We've all always agreed that it makes sense for the development environment to be as close to production as possible. With Kubernetes in the picture, we're seeing teams struggle to fulfill this. The problem is significantly heightened by the fact that while the pace of deployment has increased, the ability of development environments to keep up has remained unchanged.
Some teams are just not able to provide their developers access to production-like environments during the development phase. These teams then struggle with bugs that often come in notice only after shipping changes and are hard to debug. What makes these bugs particularly hard to fix is the fact that they don't get spotted during development in the first place!
