Don’t downplay your technical credibility because that is one of the main reasons you were discovered in the first place. All too often, the current modus operandi for a marketing or sales conversation is about 'business value.' While there is certainly nothing incorrect with that approach, we recommend not losing yourself in the generalities of solving business problems that you forget who you are.
These six things from your current enterprise probably won’t (or shouldn’t) work in your new Kubernetes architecture.
The State of DevOps 2019 was published in August, right in the middle of summer break. If you are like us, you debated whether or not to read it immediately.
Agile, cloud-based applications rely on many automation tools—some of which integrate with each other nicely, others less so. At the same time, everything involved with creating, maintaining and operating a cloud-based application is evolving rapidly. It’s difficult for companies with limited IT budgets to keep up. In this fast-moving environment, companies struggle to plan for five, ten or fifteen years in the future, especially when it’s impossible to predict what the tools or infrastructure of the future will look like.
But planning for the future, whether it’s one or ten years down the road, is something all companies need to think about, even as they rush to clean up existing technical debt.