<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jonathan Reinink on Medium]]></title>
        <description><![CDATA[Stories by Jonathan Reinink on Medium]]></description>
        <link>https://medium.com/@reinink?source=rss-d288b9293102------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*przJAsI1BG086nic.jpeg</url>
            <title>Stories by Jonathan Reinink on Medium</title>
            <link>https://medium.com/@reinink?source=rss-d288b9293102------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:06:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@reinink/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating awesome technical talk slides]]></title>
            <link>https://medium.com/@reinink/creating-awesome-technical-talk-slides-cec26c23e79b?source=rss-d288b9293102------2</link>
            <guid isPermaLink="false">https://medium.com/p/cec26c23e79b</guid>
            <dc:creator><![CDATA[Jonathan Reinink]]></dc:creator>
            <pubDate>Mon, 25 May 2015 13:14:26 GMT</pubDate>
            <atom:updated>2015-05-25T13:21:16.100Z</atom:updated>
            <content:encoded><![CDATA[<p>A few people have asked me how I create my <a href="https://speakerdeck.com/reinink">technical talk slides</a>. What follows is my approach, as well as some recommendations I have for other speakers. Please bear in mind that I’m very new to speaking.</p><h3>Start strong</h3><p>Make sure your first slide is gorgeous. This is the slide that appears for the 10–15 minutes before your talk starts. People may walk by the room and see it. It may even convince them to walk in. Your first slide is your first impression, before you even start talking, so make sure it’s a good one! How exactly? Try to polish it as best as you can, which I understand can be challenging for non-designer, technical types. I like to use strong colours, a muted background photo, and a great big massive title.</p><h3>Choose a couple strong colours</h3><p>This is such a simple thing, but colours can really help pull your whole presentation together. Pick one or two complementary colours, and stick with them. Avoid straying from these colours at all costs. I normally head over to <a href="https://color.adobe.com/explore/most-popular/">Kuler</a> and pick something popular. What’s great with Kuler is that colours are organized into sets, with five colours in each set that all work well together.</p><h3>Consider upgrading the default font</h3><p>If you’re using Arial, you may be missing an opportunity to add a little design flare to your slides with minimal effort. Personally, I’m a huge fan of <a href="http://www.typography.com/fonts/gotham/overview/">Gotham</a>, specifically the bold weight. Some other favourites are <a href="https://typekit.com/fonts/proxima-nova">Proxima Nova</a>, <a href="https://typekit.com/fonts/museo-sans">Museo Sans</a> and <a href="https://typekit.com/fonts/open-sans">Open Sans</a>. And don’t forget about your code snippets either. Make sure you’re using a mono-spaced font. I absolutely love <a href="https://typekit.com/fonts/source-code-pro">Source Code Pro</a>, by Adobe. I use it in my editor, so why not also use it in my slides?</p><h3>Make code snippets incredibly legible</h3><p>This can be a tricky one, especially if you’re using a 4:3 ratio. Things get very tight very quick. Well, take the challenge to make code more legible, it’s a technical talk after-all! Your ultimate goal should be to make the code’s font size as large as it can be. I’m happy in Keynote when I get my font size up to 60 points. This can take some effort. Shorten variable names. Maybe even split up lines of code into multiple lines. Quite often the challenge isn’t vertical spacing, but horizontal. Never let lines of code wrap, it’s much too confusing. And increase the line spacing. In Keynote I normally use 1.2 instead of the default 1, but sometimes I even bump it up higher.</p><p>Finally, make sure you’re using syntax highlighting. It makes code MUCH more legible. I personally use <a href="https://github.com/n1k0/SublimeHighlight">SublimeHighlight</a> in Sublime Text, which allows me to copy and paste code from Sublime Text to Keynote with code highlighting.</p><h3>Don’t design your slides for SlideShare</h3><p>Keep your slide content extremely short. As a speaker you may like using bulleted lists to help you work through your slides. You may even like having all your content in your slides for later, when you put them on SlideShare. Don’t do this! You should be designing your slides for the people in the room with you. Your slides are meant to compliment you as you speak, not be a replacement for you.</p><h3>Break your slides apart</h3><p>Try to keep your slides to one thought per slide. Don’t be afraid to break slides apart. I’d rather have five slides, than one slide with five bullets. I find this easier for listeners to follow. They won’t feel compelled to read the whole thing quickly, just in case you happen to switch to the next slide before they can finish. Short slides allow them to concentrate on what you’re saying, which is the real good stuff, right?</p><p>I like having three things on my average slide. A small visual, such as an icon. A large title, and maybe a subtitle that expands on whatever the main title is saying. The title should really sum up whatever you’re trying to say during each slide. It should make a point. This is especially useful for people reading your slides online later on.</p><h3>Use text-align: center;</h3><p>This may seem minor, but it goes a long way to making your slides look better. Think of each of your slides as a poster. While they combine to make your entire presentation, they should each stand on their own as well. When attendees tweet a photo of you during your talk, will it reflect well on you?</p><p>Too often I see content on a massive screen jammed to the top left edges of a slide. Centre this content! And while you’re at it, make it bigger as well. You want to fill as much as the screen as possible.</p><h3>Add some icons to help tell a visual story</h3><p>I like adding a few little visuals to my talks. I find that simple visuals can go a long way to help explaining whatever point I’m trying to make. A great resource for this is <a href="https://thenounproject.com/">The Noun Project</a>. It’s a collection of extremely simple graphics/icons, for about anything you can think of. I’ll often download the SVG version, set it to the colour I’ve chosen earlier, and drop it into my presentation. But be careful to not overuse these, and try to make them as applicable as possible. (I may be guilty of this rule sometimes.)</p><h3>Keep the silliness to a minimum</h3><p>We’re programmers, so naturally we like to share cat pictures and animated gifs in our talks. And that’s good in some ways, as it taps into the market we’re speaking to. But be careful how much you do this. It’s more important that you come across as a professional than a comedian. Don’t get me wrong, comedy is a key element of any successful talk, but try to do that in what you say, not in what you show.</p><h3>Your slides are a reflection of you</h3><p>Finally, remember that your slides are reflection of you, or at least of the effort you put into your talk. Good slides lend credibility, and will help capture your attendees attention. Yes, I understand you’re not a designer, but that doesn’t mean you can’t make great looking slides. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cec26c23e79b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>