 Do you use snippets? No, when you say snippets I think of like little chunks of code I get from like a gist or something like that. Pretty close. You don't use snippets in like sublime text or... No, I'm looking at them right now and I have them. I don't know what they are. I'm deducting a point from my Yelp review. How can I have a Yelp score? I'm not a place. People can visit you, you're totally a place. I feel like there's going to be one review and it's just you. And it's going to be anonymous. It's just like worst person ever. These are your words. Not mine. What are snippets? The snippets are basically reusable chunks of code that you use in your daily workflow. Stuff that you find yourself writing out a lot that would probably benefit from automating a tiny bit. So things like ES6 classes where you've got to have the class keyword, name of the thing, brackets, curly brackets, whatever. And then like that's just boilerplate. That's always going to be the case. So you could just have a snippet, add that in and then just what you've got to do is change the class name. Yeah, and it's kind of neat because you can create your own snippets, you can go and customize them. There's whole packages of snippets depending on like the libraries you're using. So you can just like import someone else's snippets. This is kind of neat. There's a bunch of snippets that I find myself using pretty often. The first set are the sort of JavaScript and node snippets from Xenor Rocha. And this is kind of a really neat step because it covers everything from little expansions for adding event listeners to your DOM nodes, creating elements, creating like fragments. If you're working on prototypes, it'll give you a nice little expansion for that. And it'll also like highlight the relevant piece of code that you're probably going to want to change, like the name of the object. The name of the class, the prototype, and the function. Nice. Yeah, which is kind of useful. And also it does like other things like scaffolding out your IIFs or ifs. Ifs. Ifs. Whatever ifs. They're like, yeah, immediately invoked functional expressions. You're just, you're raising more questions than you're answering. You're just saying words. There's a blog post by Ben Allman. You can go check out. It covers all of this stuff. Okay. It has a great Yelp review. That's all I'm saying. From you. From me. What other snippet packages do you have? So you've been using ES6 a bunch lately, right? Yeah. What do you like in ES6? What are you using? It's mostly classes. I've started getting into fat arrow functions and promises I've been using for a little while, just because of service workers and all the other stuff like that. Those are the main things. Okay. So there's a really decent package called ES6 toolkit that includes snippets for promises, classes. For classes, it's really neat because it'll give you, again, a little scaffold out the whole class with a constructor and also highlight the section of code that you probably want to change first, which is kind of nice. It also does fat arrows, generators, week maps, sets. So those things are not played with. Sounds like this might actually be a nice way of learning about the new ES6 features. Yeah, I think so. I think they've also got, have you used the object literal shorthands in ES6? So the basic idea there is that you don't have to type out as much code. Like we reduce the boilerplate for functions and things. It also supports that and modules, too. It's kind of neat. There's ES6 toolkit. Another set that I find myself using pretty often is the Polymer and Web Component snippet package by Rob Dodson. And that's useful because it helps you when you're writing not just apps but also like your own elements. So let's say you're creating a demo page for your app. It's got an expansion that'll write out all of the boilerplate code for your meta tags. It'll include the Web Component polyfills. And then you can just go and start creating your own elements. And when you're doing that, there's a few things you always end up doing, like writing HTML imports. And he's written, Rob Dodson's written like this little shorthand, H.I., for, let's say, OK, well, H.I., do me the entire line that I require for writing an import or write me out all of the boilerplate code I need for my element. I must admit that is the one, like, criticism I have of Polymer. Like, I like the notion of just being able to pull in some component just using it on my page. It's all the stuff around it. Like, you have to add it to your Bower. You have to add it to the actual HTML of your page. And you've got to add in the HTML of import. And it's just like, those steps are a point where I'm like, I just want this thing to exist. Can you just make magic happen? So anything that simplifies that, I think, is really nice. If only you had a friend slash colleague that wrote something, a Polymer starter kit that could potentially help you there. Then drop. So for people using other libraries, and there's a ton of other libraries out there, there's things like frameworks like Ember, things like Angular, Angular 2, and so on, React. There's actually a really good set of packages that you can check out for those as well. The React one's, I think, pretty popular. Works well with Dabble. So, yeah. Nice. Check them out. So next time there's a new hot framework on the side, there'll just be a brand new package for snippets, and then boom. Yes.