<?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 Wesley Ho on Medium]]></title>
        <description><![CDATA[Stories by Wesley Ho on Medium]]></description>
        <link>https://medium.com/@wesleyho_14036?source=rss-ebdf502e6398------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qty8jsjeQPSccyQb.</url>
            <title>Stories by Wesley Ho on Medium</title>
            <link>https://medium.com/@wesleyho_14036?source=rss-ebdf502e6398------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 15:01:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wesleyho_14036/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[Public Speaking — For & As a Developer]]></title>
            <link>https://medium.com/@wesleyho_14036/public-speaking-for-as-a-developer-cecdc83cdfa6?source=rss-ebdf502e6398------2</link>
            <guid isPermaLink="false">https://medium.com/p/cecdc83cdfa6</guid>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html-css]]></category>
            <category><![CDATA[presentations]]></category>
            <dc:creator><![CDATA[Wesley Ho]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 21:49:37 GMT</pubDate>
            <atom:updated>2018-04-30T01:07:07.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hMD6wDl5nQIcBD3a." /><figcaption>Photo by <a href="https://unsplash.com/@jasonrosewell?utm_source=medium&amp;utm_medium=referral">Jason Rosewell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As an up-and-coming developer I’ve come to notice that public speaking isn’t exactly most developers’ strong suit, and quite frankly I’m sure you’re thinking — <em>why should it be?</em> Personally my presentation skills have had a great influence in many different types of work and social opportunities. Whether it was selling my strengths in a web development bootcamp interview, job interviews, and even speaking with friends of friends that might be able to help you. But what’s also interesting is that this challenge actually goes both ways. As someone who started off with a background in Business and Psychology from<a href="https://www.wlu.ca/"> Wilfrid Laurier</a>, I was well-versed in presenting prepared speeches to the public, but I can still find interesting challenges in presenting as a developer.</p><p>First lets talk about my presentation model —</p><ol><li>The (::before) — prepare your speech well. Don’t memorize scripts but <strong>memorize<em> </em></strong>the<em> key words,</em> and <strong>practice </strong>the<em> transitional words</em>. For example, imagine you’re planning to sell an apple. Your key words may be <strong>“Fresh”</strong>, <strong>“Organic”</strong>, <strong>“Local”</strong>, <strong>“Price-Wise”</strong>, and <strong>“Healthy”</strong>. Some examples of transitional words are “<strong>allowing us”</strong>, “<strong>in order to</strong>”, “<strong>for this reason</strong>”, <strong>“because of”</strong> and so on. The final product should be something similar to — “These organic apples are locally grown <strong>in order to</strong> provide the most fresh and healthy products to our consumers. We know our consumers can be price-wise<strong> </strong>and<strong> for this reason</strong>, we’ve developed a distribution method similar to Walmart’s just-in-time approach. <strong>Because of </strong>this approach, we’re able to drive down a portion of our costs and <strong>allowing us </strong>to deliver the best apples there is to your door.</li><li>The &lt;body&gt; — every physical thing <strong><em>matters</em></strong>. First thing I personally worked on before I became comfortable with presentations were my hands. Truth be told, when I first started I had no idea what to do with them. <em>Should I fiddle? Should I wave more? Should I toss it in the air like I just don’t care? </em>And my answer was keep them open, above, and in front of your stomach. It was professional, and psychologically it portrayed openness and inclusivity. Posture and actions are <strong><em>tells</em></strong> you don’t want people to misread. Keep your back straight, head up, and make sure your movements are purposeful. You can present like a Ted speaker but if your posture is like a pretzel, no one will take your message seriously. Last but not least, <strong>BREATHE.</strong> When you get nervous before you’re in front of everyone, take 5 minutes ahead of time to practice breathing slowly. It is the single most effective thing that helps me calm the nerves.</li><li>The (::after) — I’m rarely truly and completely satisfied with my practice runs. I always have to review and reiterate things I know I need to say, as well as the different ways I could’ve said it. Reflect on these and you’ll soon find that you’re a lot less conscious about your speech, and more conscious to your audience’s response.</li><li>The HTML — if you’ve done step 3 really well, you’ll realize that the speech comes more automatically to you. Now you’re job is to make sure the audience is digesting what you’re talking about. I’ve always lived by this motto when it comes to presentation, “Make your information as <strong><em>easily consumable</em></strong> as you can.” Same way we approach our code, keep it dry.</li><li>The CSS — Now we tread into the territory of how we speak, when to slow down, how to adjust our vocal pitch, and when to exaggerate an important message just like styling your webpage. One thing I’ve always done is sectioning my speech. Think of it as the way you would write your html. You need a section tag, a div tag, and then the actual content that sits in it. Then you might have a span tag for specific words to really emphasize it’s importance. Another thing I always found important was to never speak too fast. It comes off as nervous and again to reiterate, “Make your information as <strong><em>easily consumable</em></strong> as you can”. From my personal experience I’ve also found that ending my most important sentences in a lower vocal tone, positively portrays my authority on a subject matter. Beyond all that I’ve mentioned, now you just have to experiment, record yourself, reflect, and eventually you’ll see yourself presenting the way you want. Loop my friends, loop the practice();.</li></ol><p>The challenges of technical presentations can be quite interesting. Right off the bat I realized that I now need to account a fair amount of time for demos. In business most of the time your statistics and strategy speaks for itself, and the other part is simply how you sold the pitch. Not saying demos are not included in the business world, but not as often as showing your code. Now there is sightly less significance on how I sold it, but instead, how I showed it. Also there is a lot more weight to the information we speak as someone who wants to become a professional in a technical space. Credibility becomes even more important and we have to consider how we portray the information. The prep time for a presentation can also take longer because the material can also get more complicated.</p><p>Regardless of all these challenges, presentation skills are universal and incredibly important. I hope this article shows you a different perspective and help you shy away less from public speech.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cecdc83cdfa6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>