I'm 24, and 'cloud' to me is 'a vps somewhere', I don't grok the difference, I've worked in elastic compute environments before, but that's definitely not what you're buying with things like EC2, and I simply don't see the value in it.
other things like the 'DevOps' title; seems to mean either a sysadmin who can do configuration management, or a developer who can configure apache.
everywhere I go, I feel like I should have a large set of development skills, but I've been in operations for 5 years now, and I'm regarded as being a very good ops person.
I'm a 24 year old sysadmin, and I feel like I'm being left behind.
this is not an industry you can grow old in, unless you become a manager or specialise.
It is a VPS somewhere, ultimately. It's a VPS somewhere but it may be two of them or more. It may not be exactly where you think "somewhere" is, but it is somewhere. You don't know exactly what is running the VPS (or the bunch of them, somewhere), and what it runs, but it's running, it's a VPS, and it's somewhere.
We'll charge you 50% more to enjoy this uncertainty and to be able to use the word "cloud" alongside "synergy", "blue-sky thinking", "out of the box" and a few others when you describe your stack.
(On a less cynical note: with the "cloud" you're essentially paying to replace the known, common possible points of failure with unknown, usually rare points of failure, and some redundancy. Uncertainty can be a feature.)
Devops is an attitude more than a particular practice.
So far as AWS, I'm an AWS maniac and I would say it is a bit complicated. You have a huge number of choices and if you pick the wrong ones you will pay in more ways then one.
I've gotten to the top of the learning curve fortunately because I read AWS docs over and over when I work out at the gym, but I've got little interest in working with other cloud platforms because I don't want to climb that hill again.
>because I read AWS docs over and over when I work out at the gym
Now that's... dedication. How does the "working out" part go though? There is no way I could see myself reading AWS docs repeatedly while lifting, it actually sounds kindof dangerous. Edit: you and I have the same alma mater and have probably worked out in the same gym! Go Big Red.
ah yes, teagle hall IIRC. i don't recall anyone browsing documentation in the squat rack (on the admittedly rare occasion I went to the gym in college), but that was more than a decade ago so maybe this is part of the 'brogrammer' thing :)
For various reasons I've been doing a lot of cardio for the last year. I just started lifting weights again and it's true that I don't read docs while lifting.
DevOps in my area means you do everything except clean the bathrooms for 1/2 the salary of whoever you are replacing, and work at least 10-12hrs per day because unlikely you can fit in customer support, chef/ansible/puppet deployment, databases, front and back end development, testing and debugging, presentations and piles of internal paperwork and emails in 8 hours.
I'm 24, and 'cloud' to me is 'a vps somewhere', I don't grok the difference, I've worked in elastic compute environments before, but that's definitely not what you're buying with things like EC2, and I simply don't see the value in it.
other things like the 'DevOps' title; seems to mean either a sysadmin who can do configuration management, or a developer who can configure apache.
everywhere I go, I feel like I should have a large set of development skills, but I've been in operations for 5 years now, and I'm regarded as being a very good ops person.
I'm a 24 year old sysadmin, and I feel like I'm being left behind.
this is not an industry you can grow old in, unless you become a manager or specialise.
at least... that's what I fear.