You don't know what sudo is anymore.
You're shipping production three abstraction layers deep thinking the cloud is a place. It's not a place. It's a building in Virginia that smells like burnt dust and has a bizarre buzzing noise that nobody can explain but everyone ignores.
I'm not above it. My AWS setup is a wrapper making it easier to use a server. That's it. That's the magic. We're all running wrappers on wrappers on wrappers. Serverless on containers on VMs on hypervisors on silicon that still gets hot and fails because physics doesn't care about your uptime SLA.
But I've touched the metal. I've been the guy SSHing into a Dell rack at 3am because a RAID array decided to have feelings. EnergyExemplar days baby.
Most people deploying containers today have never done any of that. Never will. They think serverless means no server instead of not my problem until it is. They think Kubernetes is infrastructure instead of a personality test you're failing.
But yes AWS has an SLA so we're fine. That's the spirit.
The abstraction of the abstraction is fine though. Forgetting there's something underneath it is how you end up surprised when the magic stops working and you can't even begin to ask why.
Sometimes I miss when SFTP was the CI/CD pipeline. 2007 felt like 1997. Figure out how systems work. Use them. Ship. Done.
Now we have yaml files longer than the code they deploy.
❤️
Jake
sudo rm -rf *