How to move from Ops to DevOps, Step by Step

preview_player
Показать описание
0:00 Intro
0:40 Ops vs DevOps
1:22 Code-first mentality
2:15 DevOps outputs
2:53 Start where you are
3:59 Systems thinking
4:18 DevOps Skills
4:29 Learn to Program
4:39 Git
4:48 Linux and Networking
5:00 Learn AWS, Azure, or GCP
5:14 Windows DevOps Quickstart
5:37 Learn a CI Tool
6:11 Learn the Dev Environment
7:05 Distributed Systems
7:46 Object-Oriented Programming
8:15 Actually Getting a Job
8:45 Cover Letters
9:39 Troubleshooting a Job Search
10:27 Working with a Recruiter
11:13 Hashicorp Tools
11:52 Packer
12:24 Terraform
12:51 Vault
13:38 You might not need a new job
15:14 Summary
15:59 Horrific Outtake

Рекомендации по теме
Комментарии
Автор

Software and concepts mentioned in the video
-Terraform
-Ansible
-Puppet
-Python
-Git
-Linux
-AWS
-Azure
-Google Cloud
-WSL
-Boto
-Jenkins
-CircleCi
-Cap theorem
-Consensus algorithm
-State management
-Semaphores
-Locking mechanisms
-Sandi Metz - Practical Object-Oriented Design (POODR)
-Hashicorp tools
-Packer
-Vault

crazzzik
Автор

I enjoyed + agree with the information you shared! THANK is SO much to the field of computers, applications, development, design, roles within, functions, niches, and so on and so on. I do a little bit of each niche every day. (I won't call it "tech" since that's the "BUZZ" word in 2021) The cloud (AWS, Google cloud, Azure) computing concept is one of my favs. I absolutely love what I do building my business, computers, designs, website, and such from day to day and it has proven to be rewarding on a daily basis. It's so true how you project the point that: "If you want it tomorrow you got to strategically act today!" Best of luck to you on YOUR journey friend!

WatchDouglasB
Автор

Spent most of my life as a network system admin, but I've now been exposed to working with developers; supporting Docker/Perl/PHP/Python, and working with SALT for system configuration and management, as well as a LOT of Apache configurations.

legovirgo
Автор

I also will recommend to learn Consul, because it was in my test task for job application

asyau
Автор

How to move from dev to devops ? I've several years of professional experience and familiar with GIT, OOP, CI tools, a few Linux concepts.

Charles-pmso
Автор

Hey, I have a question, I'm an SDET who develops testing franework tools to write automated tests based on that framework (software automation development), it involves coding and its challenging, it also involves DevOps, and the dev side in devops is interesting, I wanted to ask, from your experience in Devops and in tech, if I want in the future to make the switch to DevOps, can I still do a lot of coding and do most of my work via code such as in python? I know that each DevOps role is different from company to company, but Im referring to a DevOps role that involves more dev than ops since im more into coding and DevOps is the future and cloud but I do wanna keep coding and I think it would be a huge advantage as a DevOps but i don't wanna get into Ops and be more on the dev side of things, docker, ci cd and writing code and etc, love to here what's your perspective on this, because I am interested in moving in the future into DevOps but I don't wanna give up coding, and I did not much like frontend development so Automation plays the middle man between all, Thanks!

jackweaver
Автор

How to move from Ops to DevOps : Learn !

gangadharpavan
Автор

I think of DevOps as being a roboticist that builds a data center ops engineer.

RichardBronosky
Автор

I have a question, My university offers a placement with a company to become a "DevOps" engineer. Which is better in terms of salary and future prospects? starting a role in DevOps or starting a role in purely Dev/Software Engineering?

jalalsaadat
Автор

I would be down to work as a DevOps.

I have been initiated to almost 70% of the concepts the guy is talking about.
But the fact to I hear about all of them in just 15min gives me a profound feeling of exhaustion...

It's seems like the road is still very long until I'll be able to actually use all of those tools within day of work.

martinc.
Автор

Do you have any advice for someone in a help desk role? Currently I'm studying aws - I just got my solutions architect cert. I plan on learning python in depth with "Automate the boring stuff with python" Udemy course. Any additional advice?

shanebagel
Автор

Dave, did you mean to give me a heart attack at the very end of this amazing playlist? Was it the plan all along?

burtonserg
Автор

How to: First be one hell of an ops guy. If you're a low quality ops guy you will not be a quality devops guy. You have to have gotten to a minimum breadth of knowledge with a concurrent depth requirement. You should be able to be quickly competent in any new thing or you'll find the learning curve inescapably too steep.

meccastreisand
Автор

Using Vault and Terraform, but i have still hard time to understand why would i use Consul if there is Istio available. Moreover after latest Istio updates of merging components, etc. Every time i use HashiCorp i hear the strange voices in my head.. something like "... vendorrrr lookiiinnn.. " and every time i get goose bumps. :)
One thing which appears to me is like... as more as you automate the system as more... complicated everything becomes. Let's say you want to run simple Go service. In the simple world, you ... just run it! :) Simple Systemd unit file and basically job done (oversimplefied). But once you introduce all the DevOps "trends & idioms" the very same simple project becomes the monster. Instead of simple `go build` you now need to explain for somebody how that all monster works. First you need to install Ansible, then Terraform, then Vault, then Jenkins, then dump the secrets into the Vault, do the unsealing magic, then run Ansible, then Terraform, then trigger the Jenkins and whoala! The very same go service is running! :) :)
My point is that... in some sense DevOps is one way ticket to the bureaucracy. You end up with the web of interconnected and interdependent tools. And once implemented, this is mostly the only way of getting things done and live. If some tool in the middle of the pipeline broke, then ... well ... everything stops. If you used Terraform to provision the DNS you can't anymore to go and to modify that resource directly in CloudFlare because you will f***k up the Terraform state. Or if you used chained remote state files to provision, then you must decommission the resources in the exactly opposite order. You loose any flexibility as everything is scripted. So, for those who are interested in the learning just development... don't rush to follow "best and trendy practices" until you really understand the value of automating stuff for your own environment. If all you want to do is to develop WordPress themes, then probably you don't need a full blown CI/CD to get job done. DevOps comes at cost. It will slow down the simple scale development. But things like Ansible and Terraform is really worth to learn at any level. At least you can automate your workstation setup.

Oswee
Автор

Do the same rules apply if you're in desktop support trying to pivot into DevOps?

khalinmcgirt
Автор

great tutorials! thx a lot ...
btw ... did u recon ...
... your webpage / wordpress is broken 😞

reinhardstaudinger
Автор

What u used to work on ops environment ??

sarojdash
Автор

Do you still do mock DevOps interview??

George-mklp
Автор

"Recruiters are not all bad" XD

thcdenton
Автор

Oh No: 1:28 America first!! America first, 🤪😝🤔🥴🥳🤮

sashajaoallerdingsinsasse