4 ms·
You transition to being a "Cloud Engineer", which is basically the same, but in the cloud. You'll be running bash scripts through a terminal emulator in your br
by wodenokoto 8y ago
You transition to being a "Cloud Engineer", which is basically the same, but in the cloud. You'll be running bash scripts through a terminal emulator in your browser, and define settings for managed vm's using yaml. There's a brand new cloud world out there and it looks pretty much the same.
I think the next hot thing after devops and datascientists are gonna be cloud architects and engineers.
- scarface74 8y agoGod no. Don’t tell him this. There are already too many sysadmins that take the on prem, non automated, lift and shift mentality to the cloud, and leave in their wake an infrastructure that costs more than if they had just used bare metal at s colo. If you’re hosting a bunch of VMs “in the cloud” and doing the same stuff you did on prem you’ve just gotten the worse of both worlds - you’re spending more and not getting any of the benefits of letting your cloud vendor do any of the “undifferentiated heavy lifting”. My experience with “cloud architects” who don’t know anything about development is that they are actually a liability.
- vortex_panda 8y agoI'm aware of the "lift and shift" mentality that some people have. I know several people who work at another company that decided to just uplift their on-prem VM-based software stack into AWS. It went very poorly.