I feel like I'm drowning in acronyms. Between Kubernetes, Lambda, SageMaker, and EC2, how do you decide what to learn first? Is the sheer volume of services the most challenging part of cloud computing, or should I just focus on one specific niche?
3 answers
The "analysis paralysis" is a huge hurdle. To master <cloud computing>, you have to accept that you will never know every single service offered by a provider. The trick is to learn the core "Big Three": Compute, Storage, and Networking. Once you understand how a virtual machine connects to a disk and a network, everything else—like containers or serverless—is just an evolution of those concepts. Don't try to learn everything at once. Pick a certification path, like a Solutions Architect Associate, to give your learning some much-needed structure and boundaries.
Do you feel that the certifications in cloud computing actually prepare you for real-world scenarios, or are they just good for the resume?
I found that learning the CLI (Command Line Interface) was harder than the services themselves. It makes <cloud computing> much more powerful, though.
I agree. Moving away from the GUI is a major milestone. Once you master the CLI, your productivity in the cloud environment will easily triple.
Steven, certifications provide the map, but the "hardest part" is actually driving the car. A cert will teach you what a service is, but only a hands-on project will teach you why it breaks and how to fix it. I always tell juniors to build a personal website using cloud-native tools alongside their studies to get real experience.