2 years of working with cloud infrastructure taught me something I didn't understand when I started:
Cloud Engineering is rarely about one service.
It is about how everything connects.
An application might involve:
→ AWS infrastructure
→ Terraform
→ IAM
→ VPC networking
→ CI/CD pipelines
→ Containers
→ Databases
→ CloudFront
→ DNS
→ Monitoring & logging
→ Security controls
And when something breaks, the answer isn't always obvious.
A deployment can succeed while the application is still unreachable.
A security group can look correct while the routing is wrong.
A Terraform change can be small but impact multiple resources.
A pipeline can be green while the application deployment isn't actually healthy.
That's where experience starts making a difference.
Over the last 2 years, I've learned to look beyond:
"Does it work?"
and start asking:
"Why does it work, what happens when it fails, and how do we make it better?"
Still building. Still breaking things. Still learning.
But definitely not the same engineer I was 2 years ago.
Top comments (0)