 I'm Redamantus Batnag, and I'm going to talk about doodling. I'm from Manila, Philippines, also a hot place. I work on the support team of Engine Yard, and we provide platform services for Ruby, PHP, and dockerized applications. You can find me as Redamantus on GitHub, Twitter, and Google. So, doodling. As programmers, we spend most of our time with text. And so, we also communicate using text. But it's 2015, we can do better. You might think this is not for you because you cannot draw. I have good news for you. You can use emojis. Sometimes the graphic you want isn't available as an emoji. Just draw it anyway, and keep in mind that visual thinking is not art. It does not require art. Simple drawings will do. For example, this is a nice drawing of a cloud, but also complicated. This will do just as well. So, by using combination of simple lines, you can communicate various concepts like cute, fast, and even software architecture. So, just draw anyway, even if you think you can't. But it's still hard to start with a blank page. So, I recommend this framework from DanRome, the vivid grammar graph. You can break down many topics into who, what, how much, where, when, how, and how, and why. The framework is a guide on which visual tool to use for each piece of information. I'll walk you through a complete example. This is the Engine Yard deployment guide. It's pure text. First, let's apply the framework. We start by creating portraits. We highlight the nouns. And we give them better names. And then we create portraits for them. More portraits. We have our portraits. We're going to skip the charts because we're not talking about numbers and deployment. And we create the map. So, maps, a map lets you show how each of the elements relate to each other. Like, this thing is inside that. This is running on top of that. Stuff like that. Like this. On each instance, the contents of blah, blah, blah are copied too. So, there, you show what's inside what relationship using a map. So, those are maps. And next, we create a timeline. So, the whole document is this one. It's step one, step two, step three, step four. So, we create a timeline by drawing this. And then we use that to show the reader on which part of the process he's in. So, let's apply all of that into the document, one section at a time, and we're done. So, let's put it all together. This is the whole document again. And these are the finished documents. Let's go through each page one by one. So, here we used our portraits and we created a map. And the original text is over there on the right. So, next step, next step, if you look at the top, there's the on which part of the timeline you're in. And we're using maps and our portraits. Next step, next step, next step, next step. I won't bore you with the details. Next step. And here's our starting document again, pure text. And here's our finished document. Great success. So, if you want to learn more, you can check out the book where I lifted the framework. That's Daniel on blah, blah, blah, what to do when works don't work. And that's it. Thank you.