This is a big list to tackle from zero. Chances are you’re employable if you get through a third or half of this list. You’re probably senior if you can do all of it.
A step by step guide on how to become a DevOps engineer
21–30 of 50 posts
Re: A step by step guide on how to become a DevOps engineer
#22Standard rant: if an individual “is doing DevOps”, then they are in “operations” and just doing what operations has done forever using a fancy name.
No there was never a time in modern history (ie at least since I’ve been around in the mid 90s) that operations at any scale wasn’t using some type of tooling - either DCL for VAX machines, Perl, PowerShell, etc.
Re: A step by step guide on how to become a DevOps engineer
#231. Find out that DevOps Engineer is a made up title by hiring managers to mean "IT Operations Engineer That Knows Modern Tools" but shorter 2. Become an IT Operations Engineer 3. Years later, find out what DevOps actually is 4. Never actually practice DevOps 5. Become a DevOps Consultant
great reply
Re: A step by step guide on how to become a DevOps engineer
#241. Find out that DevOps Engineer is a made up title by hiring managers to mean "IT Operations Engineer That Knows Modern Tools" but shorter 2. Become an IT Operations Engineer 3. Years later, find out what DevOps actually is 4. Never actually practice DevOps 5. Become a DevOps Consultant
Ha! That’s not all that different from my experience. I was going to ask if we’ve collectively given up on arguing against DevOps as a title, role, department, etc.
missed process part. devops is not just automatization
Re: A step by step guide on how to become a DevOps engineer
#251. Find out that DevOps Engineer is a made up title by hiring managers to mean "IT Operations Engineer That Knows Modern Tools" but shorter 2. Become an IT Operations Engineer 3. Years later, find out what DevOps actually is 4. Never actually practice DevOps 5. Become a DevOps Consultant
IT operations engineer? How about sysadmin?
Re: A step by step guide on how to become a DevOps engineer
#26Step 0: Understand that “DevOps” is a really bad name for “Industrial Engineering principles applied to IT.”
Re: A step by step guide on how to become a DevOps engineer
#27ill never get why people punish themselves with this devops shit. you could just learn 1 thing (networking) on a few vendors (cisco, juniper, whatever), pass a few tests and be making good money out the gate. i feel like devops is just a bucket for lost souls who like tech stuff. am i crazy?
It depends on what you want, what you like, and what you're good at. If you just want some IT primitives that are common across many COTS products and then become a vendor tentacle, you can definitely do that and make plenty of money. But for plenty of people that's not enough and just makes them sad.
Re: A step by step guide on how to become a DevOps engineer
#28I'm not sure if this is the exact curriculum I'd pick but I do think it's one of the easier jobs to 'learn' and get a well paying job doing. If you want to get hired at Google (for example), one thing I think that is overlooked is that the SRE-SE interview is actually a lot more sane than the puzzles you see in the software one in terms of practicality, relationship to actual work, and 'learnability'. To have a pretty solid shot you need to learn a scripting language and be able to do practical things with it -like opening files, regex, string manipulation, sets/maps, etc. Next is trouble shooting and linux internals (what happens when you boot a system or run a command at a relatively low level) - this may require dedicated study or just some brushing up depending on your background and general natural 'computer nerdiness' (i.e what OS are you using right now?). The design question needs a bit of preparation - it'd be helpful to read popular distributed systems white papers from the last couple of decades like the DynamoDB paper and understand some 'modern' primitives like RAFT/PAXOS or LevelDB/RocksDB and practice doing some back-of-the-napkin system sizing if you aren't great with mental math.
So it's definitely a lot but at the end of the day it's just knowledge you can self study. A focused course could probably teach it in 6-8 months and give you a pretty solid chance at landing the job vs the algo-puzzle coding path which has a high false negative rate even for talented software engineers. Plus once you have your foot in the door you can always look into a ladder change if you find you don't enjoy the SRE-style work.
Re: A step by step guide on how to become a DevOps engineer
#29Standard rant: if an individual “is doing DevOps”, then they are in “operations” and just doing what operations has done forever using a fancy name. No there was never a time in modern history (ie at least since I’ve been around in the mid 90s) that operations at any scale wasn’t using some type of tooling - either DCL for VAX machines, Perl, PowerShell, etc.
That's both true and a lie. It's true in that people can't agree on what words mean and slap them on anything, and it's a lie that it is ops/sysadmin, because it's not.
Re: A step by step guide on how to become a DevOps engineer
#30It's pretty much shell scripts all the way down folks. Its all shell scripts being used abused wrapped invented and reinvented.
Although I get your point, fundamentally DevOps tools exist because shell scripting is so bad.
Now shell scripts are called from containers as defined at ci-cd.yaml