 So apparently we have 15 seconds to enjoy my handsomeness. Let me know how that goes. So I love you, Boyd. All right, so I'm Clinton Wolfe. I'm going to be talking about different terms that we use in the DevOps community. I know I'm on. I'm with you, buddy. You burned my time. No. Anyway, so not only do I do this, so I'm a consultant, but also in my spare time, I maintain a website called devopsdictionary.com. It's a wiki, go there, contribute. But let's talk about words. Goat. You may have heard this term in reference to people. There's a great podcast called The Goat Farm. Go listen to it. It's great. But a goat is something that is multifunctional, tends to ignore boundaries within an organization. It's a good thing. If you ever want to call someone this with an adjective, you can use the word capreen. Isn't that great? Could you please be more capreen in your work? Be more goat-like. All right, pets and cattle. So pets and cattle, you may have heard this in reference to servers. So a server that is a pet is one that you lovingly maintain. If there's a problem on it, you go in and you fix it. You try to have it be long-lived, big uptime, that sort of thing. Cattle, no, no, no. Easy to create, easy to destroy. You have a lot of automation around it, that sort of thing. If you have hundreds and hundreds of these things, it's not practical to treat them as pets, treat them as cattle. It's a whole mindset thing. And when you move to the cloud, good. Off we go. Canaries. Canaries. Canaries comes from deployment testing. The idea here is that when you do a deployment, you would deploy to a small group of servers and see how it goes. And if it goes well, then you deploy to the rest. The term comes from the old-time miners who would bring in an actual live canary into coal mines and the little bird's tiny lungs. It would die if it encountered any methane or bad mine gas or anything like that. It would die first. And so you knew that all the humans had to get out. Coffee ops. So this doesn't actually mean drinking a whole bunch of coffee and doing your work. That's normal anyway. We don't need a word for that. Instead, coffee ops refers to a social movement. It's a meetup that was founded by Jennifer Davis, a name you'll probably hear a lot. She's a force of nature in the DevOps community. There is one in Santa Clara. There is one in Seattle. There's a few others. If you don't have one locally, I highly encourage you to start one. They are wonderful, just people getting together and talking over coffee about DevOps. Hug ops. This is a meme that you may have seen, especially in the chef community and some others. But the idea here is that whenever something bad happens, be it a professional badness or a personal badness or anything like that, we should share empathy for each other and treat each other like human beings. If you find out that somebody's dog just died, maybe don't just ream them over some problem that they don't ream them over anything at work anyway. We should be blameless about these things. But hug ops means we should treat each other like human beings and be good to each other because stress causes errors, stress makes everybody horrible. Chat ops. Chat ops is where you integrate all of your tools with your chat system. So it could be Slack or something like that. You might be able to issue commands to your build system, say go build this thing and then it responds back five minutes later with the build was awesome or the build was terrible and it's all your fault and here's this and that sort of thing. You can get graphs out of it, that sort of thing. Really the integrations are up to you. Lots of people are having a wonderful experience with this. The biggest impact of it is that you have all of your tools actions and your people actions in one channel in one log. Snowflake. So snowflake, what does this mean? If you go into a machine and you make a manual change to fix something on a machine that is normally under automation, you have just snowflake to that machine and you are a bad person. You should in theory go back and change the automation to make it work this way. But if you have a hundred machines and one is different, that one special machine is called a special unique snowflake. I don't know if it's a fight club reference or not but it seems to be to me. Anyway, antifragile very quickly. Antifragile is the property of a system that somehow gets more resilient the more you damage it. I think it's a fascinating concept and I'm not smart enough to come up with an example. So this is only a 15 second slide and we're going to move on. Cams. Cams. Now I had this great spiel about this one and then I realized John was going to be our keynote speaker and he talked about it. So good for him. So I'm not really going to talk about Cams. Instead, I'm going to talk about yak shaving. Where did the term yak shaving come from? It came from a 1993 episode of Rennan Stimpy. Obviously, from there it went in the year 2000 to the MIT media lab where it became known as anytime that you are working on a problem and you keep having to recursively solve another problem in order to solve your original problem. The one that comes to my mind is trying to install Noko Gehry. There's lots of other things like it. Yes, you keep going into a new dependency and it's new and horrible and horrible. Yeah, so this is why things like omnibus were created. All right, that's it. There's a link on the screen there if you want to get something that actually has like attributions to all these terms. Also go to devobstictionary.com, sign up, start contributing. Somebody needs to contribute besides me and my coworkers. Thank you.