Devops is when you make the one competent person on your team build all the software and do all the operations work so you can play ping pong in the lobby.
you do such a great job of explaining Agile in simple non-techno jargon. I use your videos to bring people who are new to Agile up to speed. Thank You!
PLEASE correct me if I am wrong: So basically a DevOb does the job of a) an engineer to develop software b) the job of an server admin to provide necessary tools and infastructure and c) the one who administrates all this together to make every process faster. In short its 3 Jobs (3 different kind of skillsets) but in one person, payed 1 salery.
Well at one point a server admin might be physically positioning the server in a rack, hooking up the wires, installing the operating system, and then clicking through the GUI to set things up. With the cloud, most of this work is done with a few lines of code. Also in the past a software engineer might be writing complicated algorithms and code that, once again with the cloud, are just a matter of calling services or using a simple framework to do the heavy lifting. As far as someone else who comes in that knows about code and the servers and tells developers and server administrators how to make things work faster but doesn't have the skills of the developer or server administrator, that isn't a role I've ever seen since it is just someone who has skills in the other two areas. In practice, the teams I've seen that have really embraced DevOps tend to have everyone good at writing functional code and everyone good at writing infrastructure as code. However, there are still people with even higher expertise in specific areas. So one person may write functional code in Java, but be the go to person whenever there is a tricky thing to do with CDK. Someone else may write lots of IaC, but may really understand the nuances of how high-performance algorithms work on the Java Virtual Machine. There are always going to be people who say, "I write Java code, but I don't want to learn the skill of writing IaC to handle configuring the resources and deploying that code." I imagine they will be able to find work, but they are going to find those types of jobs pay less than someone with a broader skillset that is organized around the ability to deliver code all the way to the point that the user can benefit from it. Just like full stack developers tend to make a higher salary than someone who refuses to write any code for a server. Also, as we move to higher levels of abstraction in both system setup and in writing code, they do start to merge together more. Sorting algorithms are good academic exercises, but most engineers don't need to write that level of code in their jobs. They are doing much more simple wiring code together and, with serverless applications, deploying them in small pieces to infrastructure and wiring then together (like Lambdas on AWS or Functions on Azure). This means that programming is basically merged with the infrastructure deployment. I don't know that it takes any more brain-brawn. So much of what people used to have to do isn't required anymore. Dev and Ops all become one thing and the amount of functionality a single person can deliver (if they have invested in learning the skills) is tremendous. This is one of the reasons that good software engineers make such a high salary--they can deliver a huge amount of value leveraging technology.
@@MarkShead Ahhhh ok, didnt expect such a long answer. Tank you for that. A few things I would like to point out if I may: 1) "With the cloud, most of this work is done with a few lines of code." I personally think that cloud computing is not the answer for everything. Just imagine Curiosity doing that... Also as the past has shown clouds break too often. The only positive example I can think of is the "Folding@Home" 2) Even if, someone who operates the cloud HAS to implement the algorithm. Now the company either pays his employes once to write the algorithm, or pays A MONTHLY FEE to cloud service for ever. 3) "but may really understand the nuances of how high-performance algorithms work on the Java Virtual Machine." Sorry did you just use Java, Virtual Machine and high-performance in one sentence? 4) "So much of what people used to have to do isn't required anymore" OH yes it is if you want humanity to go any further. Or do you think we already reached the pinnacle of algorithms and only need to combine existing ones? Newsflash The algorithms used in companies AND most cloude computing are old!! An unknown but very high percentage of companys for example still relay on PID-Control (Which is apropriate in some cases) But there are many much more powerfull control algorithms out there. But no one bothers to even implement them outside of some research since it costs money to develop new things. Better employ some DevObs who can do everything a little.
It does not have to be implemented in a cloud. That is just one implementation. And you don't usually have one person doing it all. You have a number of people, experts in their field, doing thing, paying attention to what the next thing is, each person having the ability to script what needs to be done. In the end, the implementation can be fully accomplished with a button click, that is, if makes money-sense to spend the time fully automating it.
Thanks for taking the time to make the video. In my case, I couldn't follow it. Half of the video was unnecessary since they were definitions we can find everywhere, and the other half was not clear/simple to understand. I come to youtube when what I read on the web(wikipedia) is not clear enough. So, coming here to have someone reading or giving more definitions is not a good start (for me). I see it was useful for others, so, maybe this video is for people who is more familiar with the day to day work in an IT environment. I am just a regular guy. Thanks again and wish you all the best.
I appreciate your comment. It is good to get feedback on how well it answered your questions. Basically DevOps is taking the automation we know how to build from development and applying that to the operations side of things. Was there anything specifically that you had questions about?
@@MarkShead Thanks for the answer. I work in sales ops of an IT company and I see often the term devops. I don't need to know what it is to do my job but I like to educate myself and try to understand rather than just ignoring the terminology. That's why this videos explaining different aspects of the tech business are so appreciated and relevant to me.
![⭐ฮิตในTikTok!! ( หมูเด้ง MooDeng ) Ver. แดนซ์โจ๊ะๆ ReMix BY [ ดีเจกิต รีมิกซ์ ]](http://i.ytimg.com/vi/3krsyfWUeHU/mqdefault.jpg)
Devops is when you make the one competent person on your team build all the software and do all the operations work so you can play ping pong in the lobby.
And that person moves to fast to document anything.
you do such a great job of explaining Agile in simple non-techno jargon. I use your videos to bring people who are new to Agile up to speed. Thank You!
PLEASE correct me if I am wrong: So basically a DevOb does the job of a) an engineer to develop software b) the job of an server admin to provide necessary tools and infastructure and c) the one who administrates all this together to make every process faster. In short its 3 Jobs (3 different kind of skillsets) but in one person, payed 1 salery.
Well at one point a server admin might be physically positioning the server in a rack, hooking up the wires, installing the operating system, and then clicking through the GUI to set things up. With the cloud, most of this work is done with a few lines of code. Also in the past a software engineer might be writing complicated algorithms and code that, once again with the cloud, are just a matter of calling services or using a simple framework to do the heavy lifting. As far as someone else who comes in that knows about code and the servers and tells developers and server administrators how to make things work faster but doesn't have the skills of the developer or server administrator, that isn't a role I've ever seen since it is just someone who has skills in the other two areas.
In practice, the teams I've seen that have really embraced DevOps tend to have everyone good at writing functional code and everyone good at writing infrastructure as code. However, there are still people with even higher expertise in specific areas. So one person may write functional code in Java, but be the go to person whenever there is a tricky thing to do with CDK. Someone else may write lots of IaC, but may really understand the nuances of how high-performance algorithms work on the Java Virtual Machine.
There are always going to be people who say, "I write Java code, but I don't want to learn the skill of writing IaC to handle configuring the resources and deploying that code." I imagine they will be able to find work, but they are going to find those types of jobs pay less than someone with a broader skillset that is organized around the ability to deliver code all the way to the point that the user can benefit from it. Just like full stack developers tend to make a higher salary than someone who refuses to write any code for a server.
Also, as we move to higher levels of abstraction in both system setup and in writing code, they do start to merge together more. Sorting algorithms are good academic exercises, but most engineers don't need to write that level of code in their jobs. They are doing much more simple wiring code together and, with serverless applications, deploying them in small pieces to infrastructure and wiring then together (like Lambdas on AWS or Functions on Azure). This means that programming is basically merged with the infrastructure deployment. I don't know that it takes any more brain-brawn. So much of what people used to have to do isn't required anymore. Dev and Ops all become one thing and the amount of functionality a single person can deliver (if they have invested in learning the skills) is tremendous. This is one of the reasons that good software engineers make such a high salary--they can deliver a huge amount of value leveraging technology.
@@MarkShead Ahhhh ok, didnt expect such a long answer. Tank you for that. A few things I would like to point out if I may:
1) "With the cloud, most of this work is done with a few lines of code."
I personally think that cloud computing is not the answer for everything. Just imagine Curiosity doing that... Also as the past has shown clouds break too often. The only positive example I can think of is the "Folding@Home"
2) Even if, someone who operates the cloud HAS to implement the algorithm. Now the company either pays his employes once to write the algorithm, or pays A MONTHLY FEE to cloud service for ever.
3) "but may really understand the nuances of how high-performance algorithms work on the Java Virtual Machine." Sorry did you just use Java, Virtual Machine and high-performance in one sentence?
4) "So much of what people used to have to do isn't required anymore" OH yes it is if you want humanity to go any further. Or do you think we already reached the pinnacle of algorithms and only need to combine existing ones? Newsflash The algorithms used in companies AND most cloude computing are old!! An unknown but very high percentage of companys for example still relay on PID-Control (Which is apropriate in some cases) But there are many much more powerfull control algorithms out there. But no one bothers to even implement them outside of some research since it costs money to develop new things. Better employ some DevObs who can do everything a little.
It does not have to be implemented in a cloud. That is just one implementation. And you don't usually have one person doing it all. You have a number of people, experts in their field, doing thing, paying attention to what the next thing is, each person having the ability to script what needs to be done. In the end, the implementation can be fully accomplished with a button click, that is, if makes money-sense to spend the time fully automating it.
Really good and clear explanation! Thank you!
Thanks for taking the time to make the video. In my case, I couldn't follow it. Half of the video was unnecessary since they were definitions we can find everywhere, and the other half was not clear/simple to understand. I come to youtube when what I read on the web(wikipedia) is not clear enough. So, coming here to have someone reading or giving more definitions is not a good start (for me). I see it was useful for others, so, maybe this video is for people who is more familiar with the day to day work in an IT environment. I am just a regular guy. Thanks again and wish you all the best.
I appreciate your comment. It is good to get feedback on how well it answered your questions. Basically DevOps is taking the automation we know how to build from development and applying that to the operations side of things. Was there anything specifically that you had questions about?
@@MarkShead Thanks for the answer. I work in sales ops of an IT company and I see often the term devops. I don't need to know what it is to do my job but I like to educate myself and try to understand rather than just ignoring the terminology. That's why this videos explaining different aspects of the tech business are so appreciated and relevant to me.
0:29 Wooooo !! Super Hero Landing
Yeah, it's really hard on your knees
Yes. That is why we only do it with cartoon me. :)
Good explanation of DevOps!
GOOD VIDEO
In other words.... those who party together......get things done.
You are always super :)
Good
Please send me the book i sent my mail by your form
You should have gotten and email to get it in whatever format you prefer from LeanPub.com. Did it not come?
your avatar still looks nothing like you you are NOT Asian or 19. but good vid
I also don't fly around in a helicopter or a jet-powered hang glider. :)