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

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.

I enjoyed + agree with the information you shared! THANK YOU........There 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!

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

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.

How to move from Ops to DevOps : Learn !

@AUBCodeII

3 жыл бұрын

How to move from devops to ops: unlearn?

@napalm3899

3 жыл бұрын

Learn! TAKE THE INITIATIVE! Take the initiative to learn! Stop waiting around for others to do things for you or come up with ideas for you. I work with a lot of people that can't seem to do ANY of the above and it's one of the most frustrating work experiences I've ever had.

Very informative. Thanks!

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

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.

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

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.

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.

@christo0o

3 жыл бұрын

See it the other way, I am currently a devops engineer. Some of the "seasoned" developers are also having a hard (if not harder) time transitioning into devops, due mainly to the fact that they do not know any of the OPS stuff that we take for granted. For example: cloud networking, basic to medium system administration stuff, troubleshooting w/o code, hardware/software config ..etc.

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?

@dachimshvidobadze2286

2 жыл бұрын

Wondering how it worked out in the end. You have probably already made the choice, are you happy with it?

@jalalsaadat3198

2 жыл бұрын

@@dachimshvidobadze2286 yup, selected DevOps and definitely happy with the decision.

Useful thanks

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!

@tutoriaLinux

8 күн бұрын

I'm sorry it's taken me so long to respond. I think you're exactly on the right track -- DevOps is a very fluid term which was never supposed to be a job title (even though it is, now). Even in roles that are called things like "devops engineer," there will be a huge range/difference between jobs, where some are mostly ops and a bit of scripting, and others are basically pure software development but you also have a small terraform/aws infra to take care of, or occasionally deal with datadog monitoring/alerts. You're positioned perfectly, just start applying!

Your site is great.

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

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?

@tutoriaLinux

2 жыл бұрын

I think you’re on the right path! Keep sharpening your skills and start applying to new jobs (devops, swe, whatever you’re targeting) before you think you’re ready. The industry is in desperate need of talent right now, so there’s never been a better time. If you’re not consistently getting interviews, work with a local tech recruiter and use them for all they’re worth (resume editing, interview prep and feedback, etc.).

What u used to work on ops environment ??

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

@reinhardstaudinger2256

3 жыл бұрын

ah! working again -> THX!

Do you still do mock DevOps interview??

@tutoriaLinux

2 жыл бұрын

Yep, hit me up at dave@devopsinterview.me

@George-mk7lp

2 жыл бұрын

sent you email

😀

"Recruiters are not all bad" XD

So we have to know programming, git, linux, networking, aws, a CI tool, a dev environment, distributed systems, and oop even though people spend years of their lives just working on and mastering just ONE of those things as a career. What are you shitting me? In order to make a successful transition over to DevOps we cant just be good at one or two, who again people spend years or decades of their lives master one, but we have to be good at 10 different IT topics? This sounds like the process of going from a seasoned ops person to entry level devops should take a minimum of 5-7 years if you don't forget a SINGLE thing along the way and 10+ years if you do forget things along the way which everybody does. Maybe you should structure your videos so they're more practical and relatable for people. Hey just to top it off also learn packer, terraform, and vault! How about instead of adding just 3 more things, why dont we become proficient in IT at EVERY SINGLE PROFESSION THERE IS. Now thats a sure way to get the job. Lets literally turn our minds to a computer and learn every single thing out there. What a fucking joke.

@TheApothecaryAus

3 жыл бұрын

DevOps / Modern Infrastructure is v. different to your old windows sysadmin, master AD/GPO/Exchange/SCCM/VMware/Citrix and then you are an IT god. You'll find most "DevOps" engineers have 10 years of understanding the fundamentals of an environment before looking to automate, it's like a prestige class if you will however the traditional roles are no longer available to get into so you'll effectively need a Degree before being able to start as a Jr within Infrastructure, much like a Software Engineer.

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