Next steps: Am I a DevOp now?

- Welcome back. We hope that this course has helped orient you to the core concepts of DevOps and giving you a grounding in its most important areas, so you can start learning by doing. - The largest impediment to implementing DevOps is simply not starting. You know, we've given you resources that you can use to learn more but there's no better way to understand than to just do it. - Hashtag just do it. - The beauty of most of these new technologies is they are free or cheap entry-level availability great documentation and online tutorials. - For example, you can sign up for a free tier Amazon web services account installed the AWS command line tools and Docker on your PC or Mac, pull down a Docker image with Terraform on it and another with Jenkins or some other tool on it and begin experimenting. - That's right. You can learn and get from an online tutorial. You can fork someone else's code and just start hacking on it. Any technical person can take these building blocks and pretty quickly create a demo where from source control you spin up a server and put a running Jenkins server on it. You you're doing CI, first on your own computer, and then in the cloud. - In most shops, when people first hear about continuous delivery or infrastructure as code or these reliability engineering approaches their initial response is always Oh, but that can't work here. Our devs or our testers or our SS admins would never do this. - But my company is a very unique and special organization. - I know it is. - You know, I've heard a lot of those same objections myself. - But this is the same learning curve every single one of the many organizations succeeding with DevOps has gone through. We've both been through it many times. - Yeah. Most of these techniques, they're not difficult. Of course he can check in your admin scripts into source control. You know, of course you can commit code changes quickly instead of saving them up in large batches. It's not rocket science. It's simply that for many years, the advice that we've given in the industry on these topics, it's been completely opposite to what DevOps has found to work. - There's no university course on DevOps. And while there are some DevOps certifications they aren't well-regarded by practitioners. And that makes sense because DevOps, isn't really a specific job role. It's a way of thinking about your job and about collaborating with others. - Yeah, you can practice DevOps has any kind of technical professional with any tech stack in any type of organization. - And don't worry. You don't have to know it all. There's a lot of space between being a full stack engineer that knows everything and a specialist who just has deep knowledge in one thing. - You know, in fact, that's one of the desirable types of engineers in DevOps. In DevOp shops we refer to this as the T-shaped individual. It's someone who has deep knowledge in one area, but knows enough about the breadth of the other technical areas to understand how they interact with the whole. - In my organization, we have engineers of varying specialties, operations development, QA. They work in the same juror project and the same source control system and collaborate and chat. Individuals write code and some mix of Java, JavaScript Python, Bash, puppet manifests, and more. Operations engineers and QA engineers create managed services that both they and the developers use to create systems build code, run tests, package, and deploy applications and monitor and manage running services. - That sounds like you got a good mix there. You know and mine, we're all titles engineers with some specializing in front end web experience and design some in operations others focused in the data stacks. I'm doing product work. You know we all use get with the trunk based development flow along with the centralized ticketing system. Our main language is Go Lang, but there's plenty of JavaScript, Bash and Docker going around. If you do chat ops we collect a lot of metrics organization-wide and we really try to embrace continuous delivery. We built a in-house self-service deployment tool called Deployer. Every person is required to deploy their own changes to production, and they all have to own it. - That's great. DevOps shops don't look exactly the same because every set of people and every business's goals are different. There's no one right way. And there's no being a true or pure DevOp. - Yeah, all you need to do is understand the underlying principles of DevOps and try out those practices till you find out what helps you and your organization succeed. - And in the end, there are also benefits to you the individual engineer. In our experience and backed up by surveys like the DevOps report DevOps makes it work much more pleasant. - Yeah, it really does. I mean, it means more collaboration fewer outages, shorter releases. You see your work go live more quickly and you can take pride because it turns out being higher quality. - So welcome to the world of DevOps. James and I have worked both ways in our careers and to be honest, life is too short. - Yeah, it really is. - Neither one of us would want to work in the old way again. - All right. Well, we hope to see you at a DevOps days or on Twitter or somewhere else, sharing your own experiences and the learnings you've had when you're implementing DevOps. - We hope you've enjoyed DevOps Fundamentals. Thanks for joining us.