Many of us in technology regularly experiment with new tools and technology. We often do this to adopt new skills when we need to solve a problem or we have inherited some code that needs enhancement. The cloud is in many ways no different than things we've done before, but the way we do them, or maybe the way the cloud handles some things, means that we need to change how we view a task or perform our jobs.
Migrating to the cloud is something that many of us have had to tackle at some point. I've seen a good amount of lift-and-shift, including many companies who just mandated moves to the cloud without much planning. As mentioned in this article, that was cloud migration 1.0. Really, I think this was something that's been going on for years, and continues to occur today. Lots of management are seduced by the promises of the cloud to make their organization's IT systems better, so they move everything without thinking.
Then many run into cloud migration 2.0, or maybe that's coming. I see plenty of customers with things in the cloud they complain about much in the same way they did on-premises. Nothing has changed with regards to how their systems work, and they are likely spending more money on the same services they had on-premises. With the same people. They didn't plan well, didn't provision well, and they haven't changed anything but their costs.
Cloud migration 3.0 is what many tech professionals would like to see. Evaluate apps, decide which benefit from the cloud, and leave the rest alone. Leave them on-premises in a familiar environment. That's hybrid, but that's fine.
What many tech professionals worry about are their jobs, so they don't often consider where the cloud can provide benefits from some apps. The flexibility and scalability are undeniable. You just need to ensure that you understand where the cloud fits, where cloud-native can benefit your org, and then make sensible recommendations.
No matter how your organization approaches the cloud, likely you'll have engineers from the provider or third-party consultants involved. Do what I do with people I've hired: ask a lot of questions. You'll learn something, flex your knowledge, and even if you never work in the cloud yourself, you'll be better prepared to make recommendations and evaluate future choices.