 Okay, so what you don't know is all of my slides are white. So we're just gonna sit here for five minutes and stare at each other awkwardly Invisible Inc. Yes. So my name is Tom Duffield and I work for Chef and I'm going to give you ten quick tips that you can use to improve your Chef workflow Full full disclosure. I did not write this talk. I'm giving it for someone else So if you have complaints directed towards them So the first one is use the ChefDK The ChefDK is an all-in-one bundle that you can install on your workstation to get started using Chef It runs on pretty much every operating system under the sun for them or every desktop operating system under the sun and What it does is it avoids the what I like to call the bundle file from hell So if you've ever tried to set up a workstation, you know You have like a gem file that's like a million lines long and at least 50 of those are caused unhappiness So specifically with the Windows workstation You want to install Choclity, ConnieMU and PS ReadLine So for those of you who don't know Choclity is a package manager for Windows much like Homebrew or Apt or Yum ConnieMU is a console emulator that you can use as an alternative to like your native console and Want PS ReadLine also get a good text editor friends. Don't let friends use notepad or Microsoft Word Not good I've seen that so a server spec for those of you who are doing testing using Chef spec or test kitchen having a spec underscore helper file allows you to kind of Manage all of your shared settings and that kind of cleans up your tests So if you have some if you have a consistent value that's going to be across all of your tests Rather than putting that in every single test you can put it in your spec helper. You can also put fixtures in your data path mixlib shell out so if you are if you use back tips back ticks in your recipes use this instead Shell underscore out and shell underscore out bang are now part of the core chef DSL as part of Chef 12 Which means you can run shell shell our command outputs grab the output from that and use that so no more back ticks please Okay, so the other thing make sure that you record while you learn so either take notes or even better if you're screen sharing or Get like a screen recorder and as you're learning or as you're teaching someone Record that so that you can go back and use it or as you ideally bring on people to your team because you're expanding They can reference those screencasts rather than you having to explain it over again For the hundredth time because hopefully your team is growing really fast Prebaked VMs or containers. So what this means is rather than Starting like spinning up a cloud instance and stalling everything from scratch Take that create a image that has all of the heavy lifting already done. So like all of the binaries downloaded all of the All the things installed all those time-consuming bits and just do them ahead of time and then start it up and run chef again When you want to launch it for real and just do that last mile configuration Trouble shooting with price. So if you've ever Seen an output of a chef run and you're like, hmm, that's interesting. Why did it do that? I've never seen it do that before you can use pry Which is a ruby gem that allows you to essentially stop a chef run like in the middle of it And you can look around and like run Ruby commands and stuff to actually figure out why it's all of a sudden executing Java code or something Using run state to store data. So if there's data that you want to store temporarily in your Node state, but you don't actually want that data to go to your chef server You can store it in the run state and this allows you to just like if you want to Create some data in one recipe and then reference it in another But you don't want that data to live forever in the cloud you can Just put it in the run state and there's a little URL to help you do that So course everything instead of checking for now This one's a little interesting. It's a little opinionated. I don't know if I personally agree with it But it's on the slide. So I have to read it and this is essentially Oh, it's on the sides anymore. Cool. Um And this one is by Matt Stratton and that is pimp out your text editor Which basically means make sure that it's not Notepad Project drawers plugins themes all that stuff is really important You stare at this thing for six to seven hours a day. Make sure that you enjoy staring at it So that's it for me. Once again, my name is Tom Duffield if you want to complain about these Tips you can find me at the chef booth and I will sit there and listen and then forward them all to Sean Carolyn who wrote this thing