Live data from Hacker News

A step by step guide on how to become a DevOps engineer

github.com

11–20 of 50 posts

Re: A step by step guide on how to become a DevOps engineer

#11
ill 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?

Re: A step by step guide on how to become a DevOps engineer

#12
1. 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

Re: A step by step guide on how to become a DevOps engineer

#13
post #11

ill 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?

You are not crazy - you can definitly specialise. Though I think this is a good way to find out areas you may be interested in

Re: A step by step guide on how to become a DevOps engineer

#15
Having worked as DevOps, I would really start a guide with a qualification of the pro's and con's of DevOps to evaluate if DevOps is the right path.

The sad truth is that DevOps is a cost center which comes with all types of organizational disrespect, including lower pay and harder political battles.

Re: A step by step guide on how to become a DevOps engineer

#16
post #4

As someone that has never worked at a startup before, this seems to be the list of skills a startup might find reasonable for a 'DevOps Engineer'. Every other place I've interviewed or have worked has DevOps Engineer and Site Reliability Engineer being distinctly different roles (SRE focusing on monitoring and logging and DevOps engineer focusing on pipeline and build). There are also other places like where I am now…

devops or sre might as well be a euphemism for sysadmin that can write a little python

[deleted]

Re: A step by step guide on how to become a DevOps engineer

#17

1. Identify a plethora of tools that are gaining steam 2. Start implementing tools into existing workflows 3. Pad resume with new buzz words 4. Leave for a more lucrative gig while midflight with current projects 5. Rinse and repeat

Dammit I was just going to post #5.

Re: A step by step guide on how to become a DevOps engineer

#19
post #4

As someone that has never worked at a startup before, this seems to be the list of skills a startup might find reasonable for a 'DevOps Engineer'. Every other place I've interviewed or have worked has DevOps Engineer and Site Reliability Engineer being distinctly different roles (SRE focusing on monitoring and logging and DevOps engineer focusing on pipeline and build). There are also other places like where I am now…

devops or sre might as well be a euphemism for sysadmin that can write a little python

If a SRE only knows one language I'd be skeptical. Most SREs I know know multiple languages. That goes for SRE-SWEs and SRE-SEs.

Re: A step by step guide on how to become a DevOps engineer

#20

1. 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.
Post reply on HN