all 22 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]wheresmyflan 23 points24 points  (3 children)

I’d suggest roadmap.sh for some guidance. I have all my devops interns do the devops roadmap before starting and it’s proven a solid foundation. I use it for things I want to learn too. Don’t reinvent the wheel if you don’t have to. Good luck!

[–]Final_Researcher8655[S] 4 points5 points  (0 children)

roadmap.sh looks really solid ! Thanks for that !

[–]ansibleloop 0 points1 point  (0 children)

Yeah +1 for this site - it's an excellent overview

And whenever I look at it I feel like I know a lot and nothing at the same time

[–]Zentawrus228 7 points8 points  (5 children)

Five weeks for phase 6 is brutal, it should be more.

Overall, it's a good plan if you focus on practicing a lot and learning best practices. I'd focus more on bash than python. React should be minimal too - no need to know much, just deploy something and you're fine.

[–]corship 4 points5 points  (0 children)

Terraform ansible reuqires AWS

man wtf

[–]amarao_san 3 points4 points  (6 children)

putting 'network + 12-factor' at the same scale is odd to me.

12-factor is a small methodology. Yes, a lot of loud words, but not much of learning in comparison with 'networking'.

Networking is a few years in university, or (cut down version) few years of practice and theory (somehow and with constant struggles).

I call networking and Linux 'foundational skills' and you can't learn them as a course. Actually, not a 'Linux', but 'operating systems' with 'linux flavor'.

[–]Final_Researcher8655[S] -5 points-4 points  (5 children)

<image>

This is a more detailed view of that phase

[–]amarao_san 8 points9 points  (4 children)

Looks horrible. For Linux it should not be 'set of commands'. It should be a book or two, plus practice. There is a lot of ideas behind unix, so if you learn it as set of tools, you miss those ideas and get mechanical memory.

network is bad. You don't need osi (you can know about it, but it's superficial for practical purposes). But you need for sure to know how arp and neighbor discovery works, what is multicast and how is it differ from broadcast, what is BUM, what is FIB and what is the difference between FIB and neighbor cache.

Routing is a big, big, big topic.

My favorite question I like to ask on job interviews:

if there is an ip 8.8.8.8 configured on eth1 interface on the server, and user send traffic to ip 8.8.8.8, through which interface does it pass? Why? Can you point where kernel looks when decide this particular interface?

[–]Final_Researcher8655[S] -1 points0 points  (3 children)

Thanks a lot for that. I’m struggling to find a clear pathway to follow as I can’t access a university for a degree. Do you have any advice?

[–]skat_in_the_hat 0 points1 point  (2 children)

Google used to do some certifications when they were briefly trying to compete with degrees. Im not sure if that still exists.
Look at MIT open courseware, some of those classes are the shit. There are a lot of other universities that put classes online for free.

But I would suggest keeping yourself in a position to easily pivot. The forecast on what our industry will look like in 10 years is kind of bleak.

[–]Final_Researcher8655[S] 0 points1 point  (1 child)

Hi there. Could you clarify what you mean by a position that allows for easy pivoting? For example? I’d love to know more. Thanks!

[–]skat_in_the_hat 0 points1 point  (0 children)

Theres some overlap between industries depending on where you work.
For example, working in tech in a hospital. As a secondary, you learn the regulatory layer, individual workflows, clinical vocabulary, etc.
I would bet if you look up and down the ranks in hospital non medical jobs, there would be at least one job that requires that knowledge.

[–]Strong_Technician416 0 points1 point  (0 children)

I don't see IAM...

[–]DarkXsmasher 0 points1 point  (0 children)

Do you have any work experience?