 the Toby to build some of our projects. One of our biggest projects is CanGS. I should have preloaded this. Oh, Wi-Fi is really fast right now. Awesome. This is one of our biggest projects. It's an open source project to help you build your applications. We gave a small talk about it yesterday. If you're interested about this, feel free to grab me and pull me aside after this session. We can talk about this ad nauseam. But when you're building a large open source project, it gets tricky to maintain it. You have different contributors spread out all over the world, volunteer contributors, et cetera. So you want to automate a few things. I'm going to talk about grunts and how we use it at Potoby. So a Potoby case study is probably a poor title. We're not actually going to do any analytics behind how we use grunt. We're just going to deep dive into what the code actually looks like and how we run it at Potoby. So for those that are not familiar with grunt, really quick, this is the awesome logo. Grunt is a project originally written by Ben Alman, still maintained at Boku. Ben Alman's an employee at Boku. To automate tasks, I need to do these things all the time to achieve some results in my project. I need to run the tests. I need to make a distributable. Grunt is one of the projects that helps us achieve this. If you're familiar with Ant, Make, Rake, Sake, Maven, Gulp, Jake, Bake, I mean I could keep going on and on and on with all the different build systems there are. But grunt is pretty nice. It's specific to or caters to JavaScript engineers at the time when we were putting together our open source projects, it was very, very prominent. A few of the other new ones hadn't been invented yet. We picked up grunt, we liked how it worked, so that's the reason we're using it. If you're here for yesterday's talk, I'm going to echo that same sentiment. Don't go back to your companies or your teams and say, we need to rebuild everything with grunt. Don't use it because I'm even telling you to use it. I'm going to say I'm a fan and I think it's a good idea, but educate yourself about the tools and what options you have and then make the choice based on your education, not on me saying pretty words. So what does a task runner even do for us? Why is this even important? Well, with CanGS, it's very, very complex. So CanGS is an MV architecture framework that helps you build rich applications, rich experiences, but because we want to provide that tool to as many people as possible, we make many difference, oh, is it loose?