 hands are down. Everyone whose phone has been going off day, please turn it off, you know, let's all be honest here. And volume on your computer, come on, we're all grown-ups. Turn down your volume. Before we get started, Evan Conner here. We want to show off the new, we came up with this at RubyConf, New Orleans. This is the sort of secret handshake, sort of Ruby Nerd Greed. We do it in slow motion. It goes, fist bump, phone call. Try it out with your neighbors. Act like you're at a Catholic Mass and piece me within you, or whatever. Okay, so this was a lightning talk that I originally gave at GoGorugo up in San Francisco a few months ago. And the short version is, there's all my slides. I was on the portion of working with some really bright people over the years and learning lots of stuff from them. And one of these lessons that I've learned was from Aaron Patterson, who you might know as Tenderlove, which was up at GoGorugo, sort of riffing on the previous year about how to, you know, give a good talk. And it comes down to three things. A provocative title, sexy pictures, and Ruby codes. So here's my talk in three slides. I insult everyone with the title. And there is a sexy picture of Aaron Patterson himself. Thank you for that. And there's Rubinius' incency valve method. So we're all done. We can go home, right? All right. So, the real talk here. I'm Shane Becker. I go by Vegan Straight Edge on the Internet. That's what my face looks like. I make websites for fun and for profit, sometimes for myself, sometimes for the man. And a quick sidebar here. I live in LA, like most stories, was about a girl. I moved here for the prospect of this girl who turned out to be batshit and sing. She's here now. She's a zombie. So the prospect of a job and a girl. And the girl didn't work out, but that's all right. And the job didn't initially work out. And a few months later it did, but that's in no short measure because of Kobe. So thank you for that. I'm still here largely because of that job and so on. So thank you, Kobe. I literally had to stalk him. I waited outside the elevator until his smoke break and pinned him down for an interview. Seriously. I've made some stuff for the open sources. I used to live in Seattle, part of Seattle RV that Mitch is now sometimes ex. Down here, Evan and I have started LA RV. You've probably heard of this today. It is every Tuesday from 7am to 10am at Blank Spaces, which is Midwillshire, Miracle Mile. That's the website. It's the opposite of the name like Giles showed. Who has plans on Tuesday night? Who has plans that isn't going to this? Okay. So everyone, come to this. It's super simple. We just hang out. We talk. We don't talk. We code or not code. We talk or not talk for hours. So the real short version of my talk is bad slides are so bad that they literally crash space shops. Okay. So when you're up here or when you have the opportunity to be up here, remember what it's like to be out there. Take the time to design for the audience. So your slides suck is maybe not the most positive title. So we'll call them making better slides. And these aren't rules, of course, because I'm an anarchist. It's just there are so many bad slides in the world. You've all seen them. Let's be honest some today. And think of this as a strongly worded letter. So in the sake of brevity or efficiency, imagine that everything I say, because I'm going to say some, you know, hard fast sort of declarations about design good and bad. So imagine everything is said like this. My humble opinion, I think it would be better if, you know, really like sort of polite about it. You did this instead of that. But what do I know? So just imagine I'm saying it like that when I say this is horrible. And also I should say that all these slides and people that I'm referencing in this talk and that I might reference from today, I respect you as people. I think you do interesting stuff. I care about what you're talking about, which is why I want the slides to be better. Because bad slides make me want to not pay attention. So the first question is always, am I making it visually for speaking? Or am I really making some sort of documentation that should be a website? If you end up with slides that have paragraphs, that's probably not a slide. If you have so many bullet points like this, that should probably not be slides at all. Or if it is slides, it should maybe be multiple slides. This one slide here can make me be five or six slides. I'll cover that. So the number one thing you could do to make your slides better for this experience is to use big text. And to make up for Brian, not using the F-bombs, really fucking big text, right? So here's, so the pattern I want to use is red background, which by the way, good job on the brightness of the projector to lightness ratio in this room. So you can actually see colors in slides. A lot of hotel conferences are just totally washed out. So the red background is a bad example. The green background is a good example. So this is Brian Ford's talk from RubyConf. This was his title slide. It's tiny. So I suggest you do it really big. It's pretty simple. Here's a slide from a talk about activity streams. So again, you know, a lot of unused space there and from, you know, this is a pretty small room but when you get into conferences, 300 people big, the back row is twice as far away. This becomes kind of small. So again, just bump it up. Here's some good big, clean, simple slides. Here's one of you who knows. And what helps with big text is less text. So when I see bullet points like this, I'm already reading the fourth one while you're still talking about the first one. So I'm not thinking about what you want me to be thinking about. Like this. Plus, I probably won't read that because the text is too small and I'm bored already. You've seen slides like this. This is actually, this was an awesome talk. This was at any event part of Seattle last year. And Microsoft is actually doing pretty cool things about it. And they actually kind of care about doing it right by the web, finally. But, you know, this whole thing could be a topic here and they just crammed it all. Yeah, you know, this guy, Matt Blaise, he, this was his whole deck. He's, you know, the, you could read it later or whatever. Basically, the conference required a PowerPoint deck from up front. So he made a title slide, this and then a final slide. Again, you know, just lots of noise. That's like, you know, four title slides is what that should be. Some good examples of instead of taking, instead of having a list of bullet points, you could take your heading, make that one slide and style that difference, you know, either a different background color or, you know, italicized or different type, whatever. And then each bullet or each item in your list could be a separate slide. And then, again, here's a numbered version of a list. That's obvious that those are different slides, right? This is a one big slide. That would be nine slides. So here's Jeffrey Zelman, who does the thing or two about design. So he does, say, be a one, two, three. When you have less text, it also provides interesting design opportunities. So you can do stuff like this. It doesn't apply just to type. You know, if you have less or fewer objects or items or things on your slide, you know, have this clarity and simplicity that provides you interesting designiness. The contrast issue is not, let's see. Oh, yeah, there we go. So even in, you know, pretty good setup like this, pardon me, you know, some colors don't work well together. It's even worse, you know, like I said, when the lights are brighter, it's not, you know, dust or whatever, and you don't have a bright projector. A lot of times that projector is, you know, another 30 feet back. It's, you know, spraying its light through the lit room. It's diffuse, whatever. So what I recommend to people is you turn your brightness all the way down on your laptop. And if you could make out your slide, you're doing all right. For bonus points, if you go outside in the sun and you can still see what's going on, you know, you're probably all right in these conditions. So this is a pretty slide, but in low light conditions, it actually kind of folds apart. Was anyone at RubyConf in San Francisco a couple years ago? So this was Ryan Davis and Aaron Patterson's horribly terrible bad ideas. This one was about fooby, right? So you can't actually tell there, but the bright circle is like this, you know, puke yellow kind of color, and it says PHP inside of there. And they managed to put PHP inside of Ruby. So Dave Thomas also had this problem at RubyConf this year. He was talking about Jitter Balance and was showing some high charts that were blue and red. But in the lighting conditions, you just really couldn't see the breakdown. So basically each pie chart was just a solid circle. So this actually looks fine in this room. A lot of rooms it doesn't. I'll touch upon this more later, but using a black background is pretty dangerous in projector kind of settings. So a simple switch just using a white background and black text helps the contrast a lot there. This one works because while it's white on black, it's big and bold enough that, you know, doesn't fall apart too much. Sorry, classic. And of course, black and white is always the safest bet. Alright? So everyone knows that Ruby doesn't scale and Rails doesn't scale. So slides about Ruby and Rails by transit property also don't scale. So if you run your text all the way to the edge of the screen, it'll likely get cut off depending on the projector, you know, accuracy So use what is called the title safe area. If anyone's been involved with filling out our animation, it's still working. The, let's see, like the red would be all the way at the edge of the monitor screen or whatever. The yellow would be what's called the action safe area. So any important action and your characters or whatever would happen there. But any type that you need people to actually feel safely read. And this was even more of an issue when we had before flash screens, we had CRTs that would curve the edge and you would lose a lot of pixels over there. So avoid the edges. And here is an exaggerated example. Aside from being small text, the stuff at the top and the bottom gets cut off. So like big text, by the way, I didn't know that Giles was going to be doing the biggie references. And I had one in there too. It says spinning cheese. So like big text, use big pictures. The Boston Globe understood the value of big pictures so much that they dedicated a whole photo blog to really awesome pictures full screen. It's like 960 pixels wide or so. So if you're going to use screenshots of a website, like Mitch did this earlier with the Vayner stuff, use them full screen. Or if you're going to show an image of a laptop or whatever, make it big. There's a male chunk of screenshots. And if the movements or placements of your content doesn't matter, don't move your content. Don't make it hard for me to pay attention. So this talk was otherwise awesome. Every bit of type was in the top left corner. So you always look there for the headings. But I think just because this photo didn't work well with the top left because that's where their face was, he moved it down to the bottom left. Boo. Ryan Davis is such an awesome dude. But his talk at Go Ruko had these not awesome slides. Just stuff everywhere. I imagine a teenager's bedroom would look at these. To compound the problem, all of these sort of animated into place and they weren't sort of top left. So it was like TDD, rake, incremental search. It's all over the place. So keep it sane basically. So here's some labels or headings are always in the same place. More example, top left. Easy to read. These are sort of right on the edge of good in my mind because some of these are really long, like this bottom right. Sorry for the bottom example there. It's such a long heading that in order to make all of these the same size of type, you had to make them all smaller. So if he could shorten that one and maybe the top right he could make the whole font size bigger. And again here's the one earlier from the washing machine picture. This is how the rest of his presentation was. So the titles in the top left one. So all of my slides, like all of my section headings have been black and white. And a lot of times the presentation will be that way. Every slide will be Latinx white background or vice versa. So in order to sort of mix it up for me visually, to keep me interested in the audience, use different background colors, different color combinations. You can use sections in your talk. So right now we're talking about active record and all the active record slides are in green. And then now we're talking about testing. So all the testing slides are red or whatever. So you can break up the sections of your talk into different colors so we can tell when we've moved on to something else. So this is just one of the defaults keynote templates. Pretty boring. You've seen decks like this where every single slide is like this. That gets old fast. Here's a couple more from Jeff Selden. You know where the, on the left is the sort of like section heading. And on the right is how each slide in that section. Here's Evan Phoenix from, you know, that thing RubyConf. When he was talking about developers, hard to tell there, but they are green. And then when he was talking about Rubinius, they're kind of purple. And then these are purple. Yeah, so there's like one, two, you know, right after each other. So, you know, stuff kind of stays in place. You can tell by the color that you can't see that, you know, they're all the same section. So who did this earlier? I want to say maybe Shiles. Do you want to hear Shiles? There you go. I feel like there was a table. You mean, whatever. Sony how? Forget I said Shiles. I'll bring him up. So humans are really good at sort of visual pattern recognition. You know, that we can tell the difference between the silhouette of a tree or rock and the woolen mammoth, our saber-toothed tiger, is evidence that we're good at pattern recognition. You know, we're still alive. So we're good at tables that are simple, right. You know, two by two or maybe three by three. But when we get into big tables, I can recognize the pattern there. You know, like what's going on with like the temperatures of planets and whatever. So instead of this kind of seven by eight, I'll just like a similar person. So instead of this big table of seven by eight, you know, maybe you could have seven or eight charts, right. So I don't know, I forget which column this was, but yellow is clearly down to the left. Or I'm sorry, down to the left. Whatever that means in this case. So it's easier to see the patterns when you're talking about how good as a phylioth are the different languages. You know, er, er, er, er. So this was the slide of Govindra Govindra that inspired this idea. And Blake spent most of his talk on this one slide. This was like the guts of his talk. And while he was still talking about Ruby and Erling, I was down here in Pearl and, you know, JVM, not listening to a word he had to say. Plus it's just like, it's hard to recognize the patterns and it's like, also his C1 to 10 stuff was hilarious. So, you know, make your stuff charts if it's, you know, numerical stuff comparing things. I'm so technical. Numerical stuff comparing things. Here's another one from Ryan and Aaron's talk about bad ideas. You know, theirs were intentionally poorly designed. That was part of their stick. But I've seen real slides like this that weren't ironic. So even if it doesn't have, what is it like, borders on the columns and rows, it's still tabular data. Can you show that to me in the chart? The one case where it is sort of same-ish to show numbers like this. I mean, this is probably too small, but sort of an actual, like, statistics is when you immediately follow them by a chart illustrating you know, it's like, but I sort of glazed over like this. I see a lot of zeros and my brain is a little dyslexic. Is this good or bad? What direction this goes? It's up to the right. So here's another good chart. You know, we have these four lines of stuff over time. And while I'm talking, you know, I want to illustrate this, the green one. It has a very different growth curve. So we can do this sort of highlighting thing. So we sort of gray back everything else and just focus on that. Typically the actual numbers don't matter. You know, if it's like 1.2 or 1.7 doesn't matter to me, I want to know the pattern, right? So be fuzzy about your charts when you can. You know, that sort of helps the noisiness of your slide. Just show me, like, oh, you know, in 2006 and a half, the growth went sort of really up and not so much to the right. So if you know me, I want to say that. So whatever you use, I don't care, just use a good one. You know, make it clear and, you know, clean, bold, easy to read. I like Helvetica bold, tightly corrected if possible. My name. I've got some paintings for you. Who was that? Okay, let's talk about some paintings. I have a t-shirt that says Helvetica. Museo is the current hotness. You've surely seen it on websites, especially Museo's lab. The maker of the, this font provides a couple free weights, free versions of each of them. Brian used Comic-Sarif up at Spiobarucco. Today he used Cooper Black and there's also a t-shirt for that. It's like, no. Both of those t-shirts are from subtraction.com, which is Coy Bend who used to run the New York Times website, or the design of the New York Times website. I'm not affiliated with those products at all. So don't use Time Pirates, or whatever this is, or this. Definitely not that. I realize I haven't said fucking. I'm so fucking sorry. So don't use Comic-Sarif, right, I'm sorry, Comic Sans, do use Comic Sans. Don't use Comic Sans, email Brian did today. That was for you. That was for you. But that is all Coby Small for misspelling your name. I'm not actually, I'm actually not a big fan of the Sarif fonts in general, but especially for slides when contrast and lighting are issues, because all the thins, all the details of Sarif fonts get lost easily, and then you end up with a curve in a little foot and that can be a combination of letters. And do us all a favor and don't use the default fonts and keynotes. It's Lucid and Graven's. Lucid and Sam's? Gil Sands. Gil Sands? Yeah, it's Gil Sands. Is it? Yeah. Okay, either way. You win. Please don't use it. We've seen it in, we've seen it in almost every presentation today, right? So mix it up, please. I want to say that overwhelmingly, despite it being good and I've been pretty impressed in the macro, things are better than normal. This guy, Jesse D. He made a slide deck which is free on the slide chair somewhere called Steelless Presentation. It's really good. We overlap a lot in our opinions about presentation design. He suggests using a family of fonts, right? So this is Neutrophase and there is like a light and a medium and a bold and a so you don't have to try to use Georgia and Helvetica for some contrast. You can use the varying weights at the same place. Museo provides a lot of weights as well. Some presenters even have a whole slide about their fonts. I think Tom Coase is awesome. I think Tom Coase makes some of the best slides I've ever seen. That's an older slide as well. Brian Ford even hand wrote all these sort of honor of why. That's really cool as long as you can read them, right? I think that's pretty readable, clear. This room is the kind of room where this one is especially important because if you're sitting in the back of the room or behind someone with a big head or someone who's very tall like Evan, you can't see the stuff on the bottom of the slides, right? So unless you're in a room that has like a theater scene or a theater or whatever or there's a very tall stage with an even higher this thing, is that called a screen? All the stuff on the bottom is lost, right? So don't put stuff on the bottom. Again, here's some older Tom Coase slides where big screenshots, but the labels for those screenshots were all on the bottom right so it would get lost in this setting. This is from Steelier Presentation. I think Steelier Presentation is a bad example to use for bad examples because he made it for you to look out on your computer, right? So presentations that you look out on your computer are not the same as presentations that you present on the screen, right? So while these headings are very big and bold half of each headings, you know, sort of below the fold, if you will all of the headings below the fold of this one and the most important thing on this next slide is in the least awesome spot, right? For the people behind the second row there's a bit of text that says important wins over everything else including inline styles which is like the point of this whole slide is to illustrate which of these two rules wins. I wanted to do more of this today and actually take pictures of slides as they were happening to reference them but it just wasn't really happening so this is... sorry for only picking on you, I guess but... I don't mind. So that talk was awesome, by the way but there were a handful of slides where the punchline of the slide was down here, right? I was doing a lot of this and it sort of gets tiring after a while. Don't do stuff, don't do it. Here's a couple of Evan's slides from RubyConf, you know, code samples of just the top. We'll cover code samples in more in a minute. Uh, Yehuda did the same thing. Title slides are important because when you... well, when you're about to talk and the room is sort of shuffling in and they're flipping the lights to get people to sit down you know, you sort of set the mood with all the candlelight and some sweet, you know, yacht rock and your title slide and then when you save your slides to PDF and put it on slide share, this is going to be the thumbnail when Confreaks makes the video of the slide this will be the thumbnail, right? So if you have, you know, your company logo and your copyright and all that crap on up adds 200 by 100 it's just gobbling so make this slide you know, clear and impactful actually my title slide is not the best thing in the world I'll show you some better examples here so I would not say this is awesome this, I would turn into maybe like six or seven slides, walk through them you know, like at the beginning when I said I would have said I'm Marco I work, you know, at this place which is here, you know, I make this thing here's the URLs, I would walk through you know here's a good one, you know what am I talking about and what is the sort of focus of that thing here's Tom's what's it called title slide, so it's very has a visual hierarchy the title is the important thing you can also tell who's talking about it but that's secondary and he also uses a few sort of design elements on the title slide that he references later this one's a sort of good exception to that, like don't put too much stuff on the front, or on the first slide because when you save this as a thumbnail, the bits down below that aren't really important are sort of lost that's okay, but the thing in the middle is still readable at 82 if I want to but from this one slide we can tell that Chris Messino talked about activity streams at South by Southwest in Austin on March 13th so everyone's done a pretty good job of this today I think part of the speaking experience is about the speaker if this was just about Vagrant, then I could just go to the Vagrant website, but sharing this sort of moment with Mitch as he talks about it, and learning things from him, and there's a little bit of performance, but also there's the sort of opportunities that come from speaking both good or bad or sometimes it's about a job, sometimes it's like other collaborators or friends or whatever so if I just saw this presentation or downloaded it later, and there's no clear way to get a hold of Mitch I'm just like, oh there's a Vagrant thing, I don't know how to Google, I will never find this guy so make sure you sign your work I remember watching the Bob Ross painting show on PBS when I was a kid, and he would do these awesome paintings, imagine if that one was on like development by the way such a nice way it's a nice friendly White House so at the end he would work his way through the painting and always like the last couple of minutes, he would sign his work, and he always made a thing about you've got to sign your work, and he always did unfortunately his signature was on the bottom right, so people in the back it's down there on the bottom left well I'm in a helicopter looking in the mirror so it's my race so he would only sign his work so you paint a cabin in the wilderness in wintertime sign your work don't do it like this because that's just the bad side anyhow but it's there's doing that I want to be the cranky old professor professor so this was a pretty good one it's like picture of the dude his real name and contact information that is relevant that we actually use we don't use his buzz that's weird he works for Google so he made me have to do it but you know his Twitter's on there here's a great one you're seeing sort of buzzwords this really helps this dude's personal brand you know so after this awesome talk it's clear what his face looks like when you run into him in the bar you can buy him a drink or juice or whatever and his name is sort of titled and then corner there's something like Twitter and you can sign your work however you want there's sexy Aaron Patterson again or maybe just do your Twitter you're not going to hurt my feelings either way but did anyone start following me after I put my Twitter name on the screen yeah awesome that's the first time that that hasn't happened every time I presented and I gave my you know Twitter handle my phone started buzzing while I was speaking so put your Twitter name up there put your blog up there or whatever get home of course works in these kind of situations but like give me some way to get a hold of you until I follow your progress so we're all the nerds and the nerds like the codes right here and this is where I'll mention Giles Giles had a few code examples and did you do your whole did you construct your whole presentation on the iPad or did you just deliver it on iPad like 90% so it was so I've done that and there are definitely things that are harder to do in the iPads like take a screenshot crop it so there's some limitations there overwhelming these fine screens but code samples are one of the places it sort of falls down so like everything else use high contrast and this room is really I mean it's awesome but as far as my examples about contrast codes this room doesn't apply so actually there were a couple that were hard to read that were I use a dark background in my terminal I use a dark background in a text editor most of you do too I'm guessing do the opposite for your presentation which a quick presenter sidebar if you're ever in a situation that doesn't have good contrast like this you run into a slide that you can't read like the red text on the black background and that's important to your talk and you can't sort of like out of the bowl around it what you can do is at least in OS 10 there's command option control 8 will invert your colors so you're like oh crap people can't see this you hop out of a keynote grab a presentation you do shotgun 8 and then to now it's inverted colors what's your mic it'll touch your mic siblings what's that where did you work today siblings so here's a good example of bad contrast right this was the rubio rails ropes course at rails com which I wasn't there but the slide deck looked really great had lots of great information but I think they presented it on a projector screen so they probably had some contrast issues also aside from contrast it's good to use say like a big font size and less code so show the least amount of code to illustrate your point if you can't show less than this then maybe you can walk through this code in three chunks this is the method I'm talking about it's 30 lines and so I'm going to talk about this conditional up top and then walk through it in a few slides but do it like this white background bold text is that 10 or 5 10? cool some more code samples here like everything else make your text as big as possible like line wrapping make it bold make it high contrast I think I feel like I've seen this today where my stay is on one slide and it adds one piece at a time I think that's cool it helps our focus what is important to look at here's a chart where we're going to look at active record 2.3 and then 3.0 everything else is the same this is a cool trick that I picked up from some other people where you're going to go through this section where you're going to talk about a couple pieces but they're related so links and forms that's the next big piece of my talk and for now I'm just going to talk about links and now I'm going to talk about forms so you give it some context but you focus on what's important this was this crazy diagram about sort of like activity model stuff so he showed the whole thing and then he walked through all the different states graying back everything else so you can focus on the thing that he was talking about this is the part of the song where there's a build up and by build up I mean where you start with a little bit you add a little bit more and you keep building your thing so rather than just starting with this is what activity streams look like in pieces, that's a good way to help understanding it's like small iterations and after the build up is always the breakdown so sometimes you start with a lot of stuff so whatever that is an atom with the activity streams extensions and we just added a lot of stuff it's the yellow and white but really what we're trying to illustrate here is that's what we added and it really says a person posted a note, all that was the same thing so you sort of you put some stuff there and you sort of either gray it out or knock it down that slide wasn't supposed to be there that's from an old version of stuff and like I said these aren't rules, if you want to act like the rules that's cool but rules are for breaking so there are exceptions to all of these I'm going to let the snowman and for more stuff that I make I made a screencast version of this if any of the speakers today want to volunteer their slides for then I will gladly take them and use them as good and bad examples in a future version of the screencast of this talk so I've talked with some of you about this before and I think this is the right room to talk about it I quietly launched this site the idea is sort of like our friend Jeff Grozenbach with the peep codes screencast is sort of like that with the twist of them being five to ten minutes sort of info snacks either a very high level overview of something like say Vagrant or a very focused deep dive into like how does Eval work in Rubinias that was just an arbitrary example so if you are in this room or you know someone who is not in this room that would be a good contributor to this come talk to me and we will make a little screencast together I will sell them you will get most of the money I will get a little bit of money that's all so I'd like Saturday does that six minutes conclude Q&A or show four okay what's the resolution that you use for your slides 1024 1028 because fortunately most predictors now are worth a damn okay that's cool because that's what I used but I wasn't I was paranoid that I would come in and they just wouldn't work for screencast though I used 8x6 by the way I bought your to the extent that my slides sucked they were partially your fault because I bought your screencast last week sounds like an operator error I have the bulk of addresses let me tell everyone about Rhonda he is part of L.A.R.B. in L.A. Ruby and today I learned that he has some historical relationship with the Grateful Dead and that explains so much well my costume is about the code man I really I just really wanted to hear your comment Yehuda did such an amazing job of illustrating the execution path for a particular method and we didn't really get into that when we were talking about the codes and talking about that because that was great and Cobra Ruko does like how to talk yeah so what Rhonda is talking about is Yehuda was showing the built-in caching stale refresh of stuff in Rails 3 or it's coming in 3.1 maybe whatever it was so he was like this stuff is already there you can use it now but it's not as convenient so he was like this is what you have to write to check to see if the page needs a new version right so you load this request and has anything new happened on this block post no we can just serve it with the cached version you can already do that now but you have to check on you have to check on it yourself so in 3.1 I think they're adding a way to basically say if this is stale do this otherwise do that so it's like 8 or 10 lines with sort of long conditionals turn into 5 lines with if stale else so the way he did that was like here's the one line you'll get all your your blog post and all its comments and that's it well we want to do that every time if we don't need to so then he wrote this then we also have to check this what is it the c-tag c-tag is the codes so you go check the c-tag too and it's like ok so that's sort of long and verbose and you always have to do the same thing what if there was a little competing method so he sort of built it up and then tore it back down that's kind of what I was trying to illustrate with the build up and the breakdown but you heard his examples real good so he wrote this method built it up and then tore it down and it was like a great length anyone else you know like animaniacs and like tiny toes I love rock for rabbit um animation can be used wonderfully that guy Tenderloin he used the sort of the more you know with the little like he used that wonderfully so it all depends I wouldn't say that I loved Jim's animating like numbers on the screen yes I feel like something that people are hamstrung by a lot especially when you're doing something that's training oriented they try to cram a lot of information on the slides because they know they're going to be printed people are going to take these home with them and they don't want to give them 200 slides each with one word per page especially when you've got like slides where things appear it's really annoying when you get like six different copies of the slide with things here so I mean had you any tips for knowing it's going to be printed as well as for that um yes I do have some tips the first one is to try to convince people to not print every damn thing in the world the second is if you know for sure that someone's going to be printed there's always the speaker notes feeling in Kino, I'm guessing PowerPoint has it too so you can say like testing and then put like the big blob down below that's why it needs to read you can encourage people to print like two slides per page that'll help you can also the let's say screencasty.tv I wanted to come out like scre you could actually do that as an anime at least in Kino, I don't know about that PowerPoint thing but you can do it as an animation on one slide so that when it's printed you see the last sort of version of that slide after all the animation so you could if you can do the sort of changes on one slide it says one tip in this life this morning create a normal version create a version that you're going to give away and then save that version your content's good and then go back through and do all your because viewing it at a computer is different than me speaking or saying so that's the big thing is this a visual aid or is this a shareable document they don't overlap very well I would say do a blog post about your topic and include a link to SlideShare or embed the little player you know what else I mean