<?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 Dustin Ewers on Medium]]></title>
        <description><![CDATA[Stories by Dustin Ewers on Medium]]></description>
        <link>https://medium.com/@dustin.ewers?source=rss-e4dde4db1eff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iMxV-UQOqu_JuP-TCgZz7g.jpeg</url>
            <title>Stories by Dustin Ewers on Medium</title>
            <link>https://medium.com/@dustin.ewers?source=rss-e4dde4db1eff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:48:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dustin.ewers/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[Do Your Apps Spark Joy?]]></title>
            <link>https://medium.com/@dustin.ewers/do-your-apps-spark-joy-389a75679a29?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/389a75679a29</guid>
            <category><![CDATA[digital-distraction]]></category>
            <category><![CDATA[konmari]]></category>
            <category><![CDATA[digital-overload]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Wed, 23 Jan 2019 23:10:56 GMT</pubDate>
            <atom:updated>2019-01-23T23:10:56.325Z</atom:updated>
            <content:encoded><![CDATA[<p>Originally posted at my website <a href="https://dustinewers.com/konmari-your-technology/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*e-Md49w8wp5KKSK6.jpg" /></figure><blockquote><a href="https://commons.wikimedia.org/wiki/File:Sportsfile_(Web_Summit)_(22790692681).jpg">Image from Web Summit via Wikimedia Commons</a></blockquote><p>What can this tiny Japanese lady teach you about technology?</p><p>This is Marie Kondo. She’s become a cultural phenomenon with her book <a href="https://amzn.to/2TcWhQg">The Life-Changing Magic of Tidying Up</a> and her Netflix show <a href="https://www.netflix.com/title/80209379">Tidying Up</a>. She created the KonMari method, which is a decluttering strategy where you get rid of anything that doesn’t “spark joy”. You go through each of your belongings and see if it gives you a visceral spark of happiness. If there’s no spark of joy, you thank the item and toss it into the donation bin. The upshot is that you evaluate everything in your life based on whether it makes you happy and helps you achieve your goals. Instead being a slave to your possessions, you have the things you need to live the life you want.</p><p>As software continues to eat the world, there’s been a backlash against technology, especially social networks and mobile apps. The common narrative is that nefarious app developers are using advanced machine learning techniques to turn us all into mindless phone zombies.</p><p>I find this thinking unsophisticated. I acknowledge there are issues surrounding phone addiction, filter bubbles, censorship, and the toxicity of social media. Social media can cause anxiety and depression, but there’s nothing special about the apps on your phone. It’s no different than TV or any other media. This story is as old as history. Whenever a new form of media comes on the scene, there’s a bunch of people who complain about it. It happened with writing, books, radio, TV, and now it’s happening with the Internet and social media.</p><p>Technology is a tool and tools must be used properly. If you cut off your finger with a table saw, it’s not the table saw’s fault. It’s your fault for not using the tool properly. Instead of falling for the hyperbole, make the technology in your life work for you. Apply the KonMari method to your technology life. Go through your devices, apps, and settings and figure out what sparks joy. Instead of being a slave to your technology, make your technology work for you.</p><p>I routinely go through my apps, frequently visited sites, and social networks and get rid of the things that don’t work for me. You should also regularly declutter your technology life. The process is simple, first categorize your technology life. I use categories like social media, infinity pools (ie. YouTube), and communication apps. For each category, work through each app or site in your list.</p><h4>Ask yourself the following questions:</h4><ol><li>Does it make me happy?</li><li>Does it help me achieve my goals?</li><li>Can I modify this technology to make me happier or better achieve my goals?</li></ol><p>From there, either keep it, delete it, or modify it to better fit your goals. When you’re done, you’ll have a more functional tech life. Here’s some of the choices I’ve made. You’re obviously going to have different needs (and therefore make different choices), but you’ll get an idea of what to do.</p><h3>Social Media</h3><p>There are lot of people who think you should immediately nuke any and all social media from your life. At its worst, social media can be a misery inducing time suck. It’s easy to lose hours scrolling on Facebook or Instagram. Not only that, but people tend to post their best moments on social media. They craft posts that portray their life as an amazing fun fest. Your life can’t match up to that hype. If that wasn’t enough, some people use platforms like Facebook and Twitter as emotional dumping grounds. Spewing outrage and vitriol. There’s always some new thing to be angry about. It’s almost never anything important, but the constant cycle of outrage is mentally exhausting.</p><p>However, social media isn’t always a dumpster fire. It’s a great way to keep track of your friends, especially ones that don’t live near you. If your core group of friends are on Facebook, you can also use it to plan events. Another advantage of social media is that you can often have conversations with people you otherwise wouldn’t be able to get access to.</p><p>Go through each of your social networks and evaluate if being on that network helps you. If you’re not getting any value from the network, nuke your profile. If you get value out of the network, but it’s taking too much of your time, consider removing the app from your phone or turning off its notifications. Most social networks have a web interface that works as well as the app and doesn’t hit you with constant notifications.</p><p>Here’s what I found when I evaluated each of the social media networks I was on.</p><h4>Facebook</h4><p>Facebook was a huge time suck for me. I started my account in 2006 back when Facebook was only for college students and would check it several times a day.However, I find it delivering less and less value as time goes on. Several of my friends have left the platform and 95% of what I see doesn’t help me in any way. I recently deactivated my Facebook profile. I may reactivate, but even if I do, I’m still going to go on regular Facebook breaks. At this point, it’s mostly a waste of time, so it gets the boot.</p><h4>Twitter</h4><p>I find Twitter both fascinating and irrepressibly toxic. The toxicity keeps me from spending too much time on the platform, which is almost a feature. I keep my Twitter account because it’s professionally useful to me. I find conferences to speak at and have interesting conversations with other tech people. I make use of blocking and muting to filter out as much outrage as I can, but you can’t get it all. Twitter gets to stay, but I don’t let it notify me and filter a lot.</p><h4>LinkedIn</h4><p>I use LinkedIn professionally. I check their website occasionally, but it’s not something I use very often. It does what it’s supposed to do, and it doesn’t trigger addictive behavior like other networks.</p><h4>Instagram</h4><p>I tried out Instagram a while ago. The platform is more positive than Facebook or Twitter, but it doesn’t help me in any way. I deactivated my Insta account. It was never a big draw for me, so I’m not really going to miss this one.</p><h4>Pinterest</h4><p>I use Pintrest for finding home decorating ideas and woodworking projects. I don’t use it every day, but it’s a good choice for some project inspiration.</p><h4>MySpace</h4><p>Yeah no, just kidding…</p><h3>Infinity Pools</h3><p>Infinity pools are websites that have infinite content. You can spend endless hours reading, watching, or listening. Infinity pools come in two flavors. The first are media apps like Netflix, YouTube, or Spotify. Out of those three, the big time-suck for me is YouTube. Instead of deleting the app, I put it far away from my main apps in a folder. I also trained the YouTube algorithm to filter out entertaining but useless videos. In your main YouTube feed, you can click “Not Interested”. Do this enough times and YouTube will stop showing you useless videos. After doing this, my YouTube feed is mostly educational videos relating to my career and hobbies, which is exactly what I want.</p><p>The other type of infinity pool is news. There’s an infinite stream of news articles on the Internet. I spend a lot of my time reading, but I curate my feed for the best news. I don’t visit time suck sites like Cracked, Buzzfeed, or Mental Floss. I also use RSS feeds to get most of my news. That way, I’m not stuck on someone’s website getting inundated with links. People say RSS is dead, but it’s one of the best ways to get quality news content delivered to you. Another good way to get your news is through newsletters. There are tons of great newsletters that will kindly filter out all the crap, giving you the most important news.</p><p>When dealing with news, it’s important to remember that most news is entertainment, not information. How much of the “news” is just reporters reacting to some nonsense they saw on social media? Spend some time filtering out the trash and you’ll be much happier.</p><h3>Communication Apps</h3><p>I use email and a bunch of chat apps on my phone. Instead of social media, I talk to my friends directly. I turn down the notifications on most of these apps, especially email. No one needs a response to an email immediately. Go through each of your communication apps and think about whether they need to be on your phone and if you need their notifications. Delete what you don’t need and turn down the rest. Chat apps are asynchronous, take advantage of that fact.</p><h3>Things to Add</h3><p>After deleting the apps and accounts that don’t improve your life, consider adding in some apps that will. There are hundreds of apps that can support your goals. Find them and use them. Give helpful apps a prominent place on your home screen. Here’s a few apps that I use to help foster healthy habits and enjoyment.</p><p><a href="https://www.strong.app/"><strong>Strong</strong></a> — Strong is a workout tracker for weightlifters. You can enter your routine and it’ll help you keep track of your weight lifting goals. There are equivalent apps for runners, but I don’t run, so you’ll have to find those yourself.</p><p><a href="https://itunes.apple.com/us/app/zero-fasting-tracker/id1168348542?mt=8"><strong>Zero</strong></a> — Zero is an intermittent fasting tracker. It’s easy to use and free.</p><p><a href="https://www.oakmeditation.com/"><strong>Oak</strong></a> — Oak is a free app that has breathing exercises and guided meditations. My kid is a big fan of the “box breathing” exercise.</p><p><a href="https://itunes.apple.com/us/app/done-a-simple-habit-tracker/id1103961876"><strong>Done</strong></a> — Done is a habit tracking app that helps foster healthy habits.</p><p><a href="https://amzn.to/2RIwbIa"><strong>Audible</strong></a><strong> and </strong><a href="https://overcast.fm/"><strong>Overcast</strong></a> — I listen to audio books and podcasts all the time. It’s an easy way to get more “reading” and learn while doing mundane activities like housework or commuting.</p><p><a href="https://trello.com/"><strong>Trello</strong></a><strong> and </strong><a href="https://www.onenote.com/"><strong>OneNote</strong></a> — I use Trello and OneNote to organize thoughts, projects, and to-do lists. Both of these apps are fantastic and I use them all the time.</p><h3>It’s Time to Declutter Your Tech Life</h3><p>It’s time to take a flamethrower to your digital clutter. Go through your digital life and evaluate the apps, social networks, and sites you use. Think about which ones help your life and which ones don’t. You are not a slave to your technology. Your technology works for you. If that app or service doesn’t “spark joy”, then either modify it so it does or send it to the bit bucket.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=389a75679a29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cheap and Easy Way to Setup a Developer Blog]]></title>
            <link>https://medium.com/that-conference/the-cheap-and-easy-way-to-setup-a-developer-blog-a8423079df8b?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8423079df8b</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[personal-website]]></category>
            <category><![CDATA[static-site]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 13:10:45 GMT</pubDate>
            <atom:updated>2018-08-20T13:10:45.306Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXLcA8gpIzHEIEMi86Ipjw.png" /></figure><p>One of the most important things you can do as a developer is build your own presence on the web. You should have a blog or portfolio site. Having a home on the web gives potential employers a place to find you and allows you to clarify your own thoughts. It’s also a handy way to document the things you’ve learned. I know developers that have searched the web for a solution to a problem only to find their way to a post they made years ago.</p><p>If you’re interested in building out your web presence, there’s a ton of ways to get started. The easiest way to get a blog up is to use an existing platform like Ghost, WordPress, or Medium. If your goal is to get words up on the web, these options will do.</p><p>I find these options lacking.</p><p>Ghost and WordPress are difficult to customize and cost a monthly fee. Managed hosting is 20+ dollars a month. This isn’t a huge amount of money, but who needs another bill?</p><p>I’ve used both Ghost and WordPress, but I haven’t been able to get either one customized the way I like them. You can download a theme, but making your own theme can be a pain. WordPress themes are written in PHP, which is not my favorite language. Ghost‘s theme engine is easier, but you still need to work within the confines of each platform’s available data. You can do amazing things with Ghost and WordPress, but the further you get away from “standard blog”, the harder it gets to make things just how you like.</p><p>Medium and similar services come with more limitations. Medium is a great platform for long form writing, but you’re renting space in someone else’s walled garden. If Medium decides to change its rules or alter its algorithms, you’re out of luck. Your content should be on your own platform. <strong>Own your content.</strong></p><p>For my latest side project, I’ve been exploring a new option: static hosting. With static hosting, you use a generator to build your site as a pile of static assets (html, css, js, etc.). You can host these assets for free or pennies. Because there’s no server side code, static sites are secure and very fast. They also scale well. Most hosted blog services ramp up the costs as your traffic increases. Static sites can serve thousands of users without breaking a sweat. Static sites should be your first choice for any content-heavy web site.</p><p>Another advantage of static hosting is that you can build a workflow that’s like your developer workflow. Most static sites use a collection of Markdown files. Instead of using some clunky online editor, you build your content using your favorite text editor. Once you’re done, you push your files to a Git repo just like any other code base.</p><p>The biggest advantage of a static site for me is the customizability. I use Gatsby, which is a React-based static site generator. Because I’m familiar with React, I can build my website like any other web application. I don’t have to mess with PHP or learn some clunky layout to skin. I build my content site the way I’d build any other site.</p><h3>Let’s Build a Static Site</h3><p>In the rest of this post, you’ll learn how to build your own blog or portfolio site. By the end, you’ll have a site that can handle as many users as the Internet can throw at it for less than 15 bucks a year.</p><h4>We’re going to use:</h4><p><a href="https://www.netlify.com/"><strong>Netlify</strong></a>, for hosting. <br>Netlify is a hosting platform that specializes in static websites. Their static hosting is free. They charge for dynamic features like functions and forms, but you won’t need that if you only want a blog.</p><p>There are other options for static hosting, but Netlify makes it easy to take a static site and deploy it. You can point to a Git repo and deploy automatically from it or you can drop a folder of static files and Netlify will deploy it for you. I tried out <a href="https://dustinewers.com/adventures-building-static-websites/">several different app workflows</a> before landing on Netlify.</p><p><a href="https://about.gitlab.com/"><strong>Gitlab</strong></a>, for a private repo.<br>You could point your site to a Github repo, but Gitlab has free private repos. If you don’t care about keeping your website code private, feel free to use Github.</p><p><a href="https://www.gatsbyjs.org/"><strong>Gatsby</strong></a><strong>, </strong>a static site framework. <br>I use Gatsby because it’s React-based. Component based web frameworks like React work the same way my brain works, so I find Gatsby intuitive. Gatsby is also really fast. Your site loads are nearly instant. It’s a beautiful thing.</p><p>If React and JavaScript are not your cup of tea, there are plenty of other static site generators to choose from. I’ve heard good things about Jekyll and Hugo, but Gatsby is my personal jam. <a href="https://www.staticgen.com/">StaticGen.com</a> has a great listing of different static site generators if you want to explore.</p><h4>Steps to Building Your Own Site</h4><ol><li>Buy a domain. I use <a href="https://www.hover.com/">Hover.com</a>, but you can use whatever domain service you want. You can also buy domains directly from Netlify.</li><li>Sign up for a Gitlab account and <a href="https://gitlab.com/help/gitlab-basics/create-project.md">make a new repo</a>.</li><li>Sign up for Netlify.</li><li>Build your site using Gatsby (or whatever static generator you picked).</li></ol><p>If you haven’t used Gatsby before, check out the <a href="https://next.gatsbyjs.org/tutorial/">Gatsby Tutorial</a>. It’ll guide you through the basics. It assumes you don’t know very much code, so don’t feel intimidated if you’re not comfortable with React or modern JavaScript. I started with the basic Gatsby tutorial and did the first few lessons to get a feel for the library.</p><p>Gatsby has several starter templates to get you going. I recommend using the <a href="https://github.com/Vagr9K/gatsby-advanced-starter">advanced starter</a> or the <a href="https://github.com/Vagr9K/gatsby-material-starter">material starter</a>. Both of these contain all of the things you need for a blog including SEO, comments, social sharing, and RSS. It’ll save you a ton of time. I used the material starter and then customized the heck out of it.</p><p>5. Check your static site code into your repo.</p><p>6. <a href="https://www.netlify.com/blog/2016/02/24/a-step-by-step-guide-gatsby-on-netlify/#connecting-to-netlify">Go to Netlify and start a new project.</a> Hook your Netlify project up to your Gitlab repo. Netlify will then deploy and build your site.</p><p>7. Hook up your domain.</p><p>Go to the settings panel in your project and click on domains. There’s a button to Add Custom Domain. The easiest way to hook up your domain is to let Netlify manage it. You do this by going into your domain management service and pointing the DNS name servers at Netlify. If you aren’t comfortable managing your own DNS records, you can buy a domain through Netlify.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LA05rDHq4e8vvPjkKoVM0Q.png" /><figcaption>Here’s where you need to go to add a domain</figcaption></figure><p>8. Setup HTTPS. Some people think that you don’t need to serve static sites over HTTPS. <a href="https://www.troyhunt.com/heres-why-your-static-website-needs-https/">These people are wrong.</a> Once you have your custom domain hooked up, pop over to the HTTPS tab and setup a free <a href="https://letsencrypt.org/">Let’s Encrypt</a> certificate. It’s easy and prevents bad actors from injecting nastiness onto your nice new site.</p><p>After completing these steps, you’ll have a website that deploys automatically whenever you update your Git repo. One additional feature that I used was branch deploys. With branch deploys, you can automatically deploy a branch in your Git repo to a subdomain. I used this feature to make a QA branch for my site. This is a handy way to test changes without tanking your site.</p><h4>Get Out There and Build Something</h4><p>In this article, you learned about why static sites are a good option for developers and how to build a static site using Gatsby, Netlify, and Gitlab. This stack is great for developers who want a hands-on experience that’s cheap, familiar, and fast. If you’re not a web developer, there are other options you can pursue, but this stack works for me. Go setup a Netlify account and build your own platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8423079df8b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/that-conference/the-cheap-and-easy-way-to-setup-a-developer-blog-a8423079df8b">The Cheap and Easy Way to Setup a Developer Blog</a> was originally published in <a href="https://medium.com/that-conference">THAT Conference</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get the Boring Stuff Right]]></title>
            <link>https://medium.com/that-conference/get-the-boring-stuff-right-9b296705df15?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b296705df15</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[foundation]]></category>
            <category><![CDATA[fundamentals]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Tue, 15 May 2018 15:58:58 GMT</pubDate>
            <atom:updated>2018-05-15T15:58:58.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiQKkGxs0sIcMY4SbUR9-g.jpeg" /></figure><p>Technology is ever-changing. Every year, there’s a pile of shiny new things to learn. Whether it’s the hot new JavaScript framework, a fancy cloud AI technology, or the latest hipster programming language, the fun never stops. While learning new things is fun, it’s impossible to keep up. You’re constantly asking yourself questions like:</p><blockquote>“Which technology stack is going to keep me employed?”</blockquote><blockquote>“Should I check out that hot new JavaScript library?”</blockquote><blockquote>“What about ______ (Virtual Reality / AI / Machine Learning / Big Data / etc…)?”</blockquote><p>As a developer, I love learning new technologies, but I only have a limited amount of time. I want to be effective at my job, pursue things that interest me, and have time left to lift weights, hang out with my wife, and take my kid fishing. I’m always asking myself how I can make the best use of my limited educational bandwidth.</p><p>Over the years I’ve learned that making my users happy is way more fulfilling than using the latest technology to do it. Watching the people who are going to use your software light up when they realize their jobs are going to be a little easier is a magical feeling.</p><p>Users don’t care about your new JavaScript framework. Users don’t care about the newest cloud service. Users don’t even care about that new hipster language all the cool kids are using. Users want to get their work done so they can go home. They want software that isn’t flaky, that performs well, and that isn’t going to leak customer data to the Russians.</p><p>These concerns sound boring. They don’t have the appeal of that new fancy thing you just heard about on the Internet. They don’t have cool sounding code names. However, doing the right stuff the right way is what’s going to have the most impact.</p><p>Additionally, by focusing on some boring, yet key skills, you can side step the technology treadmill. You can still learn shiny new things, but you don’t have to feel obligated to keep up with everything.</p><p>In this post, you’re going to learn how to be more conscious about how to spend your educational time. You’ll learn how to plan your education and how to pick what skills to work on. Afterwards, you will be able to maximize your impact and still have enough time left to go fishing.</p><p>After over a decade of building software, I’ve learned the key to good software is getting the boring stuff right.</p><h4>Start Here: Take Responsibility</h4><p>The most important thing to do is take responsibility for your own education. Too many developers think it’s the job of their employer to keep their skills up to date. That’s a good way to end up stuck in a job you don’t like. I’m not saying that companies shouldn’t pay for training, but that shouldn’t be the only investment you make in your skills.</p><p>Additionally, you should be thinking about what skills you need for the career you want. Your employer may be willing to support training that will enhance your current role, but that may not be where you want to eventually end up. While working for a company that values education is good, it’s <em>your </em>career and you need to manage it.</p><p>Take responsibility for your own destiny.</p><h4>Adopt a Growth Mindset</h4><p>The second important thing is to adopt a growth mindset. There’s a myth in our industry about something we call “the 10x developer”. These magical unicorns outclass us mere mortals with their godlike powers. While there can be vast differences in skills between developers, no one is born a genius-level software developer. We can all get better.</p><p>A growth mindset means that you accept that you don’t know everything. You are a continuous work in progress. This is different from someone who has a fixed mindset, who believes that ability is fixed. These are the people who say things like “you can’t teach height” when talking about developer skills. A fixed mindset makes you weak in the long run. If you need to maintain your fragile self-image of being a guru, you aren’t going to challenge yourself and you aren’t going to improve. The key to a long and happy career in software development is continuous improvement.</p><p>Research by psychologist Carol Dweck has shown that people who believe that their ability can grow are more resilient to adversity and generally outclass their fixed mindset peers. Focus on growth and you’ll continuously get better.</p><p><em>If you want to learn more about the growth mindset, you can check out </em><a href="https://www.amazon.com/Mindset-Psychology-Success-Carol-Dweck/dp/1400062756/"><em>Mindset</em></a><em>, by Carol Dweck or </em><a href="https://www.fs.blog/2015/03/carol-dweck-mindset/"><em>this article</em></a><em> that summarizes her research.</em></p><h4>Make a Plan</h4><p>If you want to make the best use of your time, make a plan. Even if you don’t follow your plan to the letter, making one will increase your effectiveness. We all live busy lives. If we don’t make the time, then it won’t happen.</p><p>The first step in making your plan is to figure out what’s important to you as a developer. Figure out what you want from your career and what skills it’s going to take to get there. Once you understand <em>why </em>you’re in your career, you can use that information to focus your education. Keeping your goal in mind helps you prioritize. Ask yourself questions like the following:</p><ul><li>What kind of career do I want?</li><li>Do I care more about money, stability, or interesting work?</li><li>What level of work-life balance do I want?</li><li>What kind of companies do I want to work for?</li><li>What types of technologies do I find fun or interesting?</li><li>Where do I want my career to go?</li><li>Do I want to move into management or start a business someday?</li><li>Do I want to specialize or be more of a generalist?</li></ul><p>Once you understand what kind of career you want to have, you can suss out what kinds of skills you need to get there. For example, if you value having a stable paycheck with good benefits over interesting work, then finding a job in a medium sized enterprise is for you. These types of companies tend to use older, more established tech stacks. Generally, you want to have a good understanding of their business. In that case, you can avoid anything that’s bleeding edge and wait for things to become more established.</p><p>On the other hand, if you don’t care about work life balance and love being a generalist, try working in a smaller startup company. Small startups tend to be more cutting edge, often employing cloud technologies so they can scale quickly. You’ll also need to wear more hats because there won’t be enough developers for everyone to specialize. In this case, focus on technologies that allow high productivity on small teams, combined with a broad overview of what’s available in the market.</p><p>If you like to go deep into a specific technology, then working for a large company might be your best bet. Larger companies can support more specialized developer roles.</p><p>Take some time to think about what kind of career you want and the types of companies that support that kind of career. With a little research, you should be able to figure out what kinds of companies you want to work for and what skill you’ll need to succeed within them.</p><p>The next thing you need to do is make time to learn. Find a few hours a week that you can devote to learning new things. It’s better to learn in small chunks, so 30–60 minutes a few days a week is a good place to start. Even if you’re busy, you can usually dig up thirty minutes. Small chunks of time add up. 30 minutes times five days a week equals 130 hours a year. You can work through a lot of books or courses in 130 hours.</p><p>Personally, I find that early morning is the best time to work on personal learning. While I am not a morning person, I find that it’s easiest to knock out mentally demanding learning before my workday. I focus on family and fitness after work.</p><p>Your mileage may vary. You may prefer to work out in the morning and learn in the evening. Figure out what works with your energy levels and schedule the time.</p><p>Also, re-purpose other blocks of time for learning. I “read” over 50 books a year on Audible while I’m in my car, cleaning my house, and doing yard work. It’s a good way to make that time more useful. I also removed all of the social media apps on my phone in favor of my RSS feed reader and Instapaper apps. By offloading some my less intensive learning tasks to useless filler time, I can use my dedicated learning time to focus.</p><p>Once you have your block of time, allocate accordingly. If you’re like me, your list of things to learn vastly exceeds your available time. Instead of trying to hit all those things at once, pick one thing at a time and work on it. Define an ending goal and work until you reach it. A good example would be working your way through a course or reading a textbook and then writing a detailed summary. Other excellent goals would be creating a presentation or blog post on your findings (this is what I do), building a small side project, or offering to teach your coworkers. The key is to produce something that makes use of your knowledge. Prioritize your learning so you’re working on the most important topics first.</p><p>Also, think about how you want to allocate your time between evergreen skills and new technologies. Your allocation should be based on your career priorities, it’s more useful to focus on evergreen skills. While looking at new stuff is fun, ultimately, evergreen skills are going help you deliver better software.</p><p>Think of your skills as an investment portfolio. Most portfolios are balanced between risky, yet potentially high paying, investments and more safe investments. In the tech world, your evergreen skills are your safe investments. Investing in your evergreen skills always pays off. Learning shiny new technologies is a more risky investment. You might win, but you may also end up with a useless tech skill. Just like a portfolio, lean towards more safe investments. I’d recommend a 75/25 split in favor of evergreen skills.</p><h4>Picking Skills to Learn</h4><p>Now that you have a plan and some time, you need to figure out what to pursue. There’s new technologies coming out all of the time, but we can only pick a few things to learn or we risk spreading ourselves too thin. There are a few things you can to do to help winnow down your choices.</p><p>First, realize that investing your time in a new technology is like making a bet. You are betting that those skills are going to help you in the long run. If you look at the past, some bets have paid off, like JavaScript or Azure, and some have not, like Silverlight. It’s not always easy to figure out what’s going pay off, which is another reason to spend more time on evergreen skills. While they aren’t going to propel you to a 500k / year AI job, evergreen skills will deliver solid value.</p><p>The next thing you can do is to build your own technology radar. This idea is adapted from the Thoughtworks tech radar. On a regular basis, Thoughtworks employees get together and make recommendations on which technologies and practices to keep an eye on or adopt. They publish this list for the broader community. By enumerating the trends currently impacting their enterprise, you can get a picture of the technology landscape, figure out what works, and make better choices about what to use. This is a great exercise to do in your own company.</p><p>While the Thoughtworks radar has categories related to adopting a technology, your personal radar should have categories related to your own learning. Feel free to include things you want to work on in your own radar that aren’t hot new trends. My personal technology radar has morphed over time into more of an “intellectual radar” where I include soft skills and evergreen skills alongside new technologies.</p><p>I use the following categories:</p><p><strong>Go Deep</strong> <br>These are core career skills that I want to improve upon. For these skills, I’m willing to take courses, build side projects, write blog posts, and generally spend lots of time working on these skills. This can include new skills I want to learn or practices I want to improve. This is a demanding category, so make sure there aren’t too many skills here.</p><p>My “Go Deep” list: Public Speaking, Writing, Cloud architecture, React, ASP.NET Performance and Security</p><p><strong>Follow</strong> <br>These are technologies that are interesting, but I’m not willing to make a huge investment in yet. I’ll read blog posts or go to conference talks on these topics, but I’m not spending a ton of time on them. These topics might be things that I’ll pursue more later or topics that interest me, but aren’t useful for my current goals. This is also the category for things that I have focuses on the in the past, but now I just want to keep tabs on them while I focus on other skills.</p><p>My “Follow” list: Angular, Design, Node.js, Data Analytics, XR, 3d printing, psychology</p><p><strong>Avoid</strong> <br>These are technologies that I’m actively avoiding. This doesn’t mean these are bad technologies. Someone else’s “go deep” can easily be my “avoid”. This category is for things that are interesting, but don’t fit in with my overall career goals. Warren Buffet has an exercise where you list your top 25 career goals, pick the top 5, and then actively avoid the rest of them. This is the same thing, but for technology.</p><p>My “Avoid” list: Native Mobile Development, IOT</p><p>While building your tech radar, think about your career goals, what skills will help you achieve those goals, and prioritize accordingly. I’ll often list my priorities at the top of my radar. Understanding your priorities helps you winnow down your choices. Once you have your radar, you can use it to inform your personal development time.</p><p>Things to think about while picking technologies for your radar:</p><p>Is this a popular technology and is it going to stay that way?</p><p>Can you learn enough about a particular skill to make an impact in the market?</p><p>Can you jump from what you’re doing to this new skill?</p><p>Is this something I’m learning for fun or for my career?</p><p>Commit to refreshing your tech radar every month or every quarter. Don’t copy over the previous radar either. If you didn’t find the time to research everything in your “Go Deep” list, don’t feel obligated to carry over old topics. The goal is to prioritize and then do what you can with your time block. If you didn’t work through your whole list, make a smaller list for next time.</p><h3>Evergreen Skills</h3><p>While evaluating new technologies is fun, you should always make room on your education plan for evergreen skills. There are dozens of things you can work on, but here’s a few suggestions that were derived from my experiences as a developer over the past ten years.</p><h4><strong>Basic Design and UX</strong></h4><p>In my experience, most enterprise projects lack dedicated UX folks. By learning some basic UX principles, you can vastly improve the quality of the software you build. Design isn’t just about making software “look pretty”. Well-designed software is easier for users to learn and makes them more efficient. It also makes you seem more competent and credible.</p><p>For the artistic portion of the design, I recommend cheating. Pick a framework like Bootstrap and customize the color scheme using colors from the company’s logo. Make sure you have enough contrast between your text and your background and you’re 90% of the way there. I’m not much of an artist, but it’s not hard to get to a “good enough” visual design.</p><p>Next, focus on the workflow in your application. How can the user get from one task to another? Does the application guide the user with good messages when they make a mistake? Does the application properly inform the user when something is broken? Learn how to write good error messages and build a responsive workflow.</p><p>Beyond that, learn how to make good forms. Most web applications make heavy use of forms and knowing how to make good ones will pay dividends. If you’d like to learn more, I recommend the following.</p><p><em>Books to check out: </em><a href="https://www.amazon.com/Design-Hackers-Reverse-Engineering-Beauty/dp/1119998956"><em>Design for Hackers</em></a><em>, </em><a href="https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1526008771&amp;sr=1-1&amp;keywords=dont+make+me+thing"><em>Don’t Make Me Think</em></a><em>, </em><a href="https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654/ref=sr_1_1_sspa?s=books&amp;ie=UTF8&amp;qid=1526008823&amp;sr=1-1-spons&amp;keywords=design+of+everyday+things&amp;psc=1"><em>Design of Everyday Things</em></a><em><br>Sites to check out: </em><a href="http://alistapart.com/"><em>A List Apart</em></a><em>, </em><a href="https://www.smashingmagazine.com/"><em>Smashing Magazine</em></a></p><h3><strong>Putting the Fun in Fundamentals</strong></h3><p>Flitting from framework to framework without understanding the fundamentals of tech stack it’s written in is a recipe for pain. Picking up a new JavaScript framework becomes much easier if you have an understanding of standard JavaScript and functional programming. Like anything else, you can go too far down the rabbit hole here. You don’t see the esoteric language features on most projects.</p><h4>Performance</h4><p>Another fundamental concern is understanding how to performance tune your chosen stack. Know what tools you can use to log performance and the general tips and tricks on how to avoid trouble. Understand how the data flows through your application and the common places for bottlenecks to occur.</p><h4>Security</h4><p>As software becomes a deeper part of our lives, security becomes increasingly important. Learn the basics of secure coding and how to prevent the most common security issues for your stack. Learn how to build a threat model to examine your applications data flows and avoid security holes. Know how and what to encrypt to minimize data leakage.</p><h4>Maintainability</h4><p>The final fundamental skill is to learn how to build testable code. Contrary to popular belief, automated testing actually speeds up coding. Not only do you get later benefits, you experience immediate benefits from writing tests. Learn how to write automated tests in the various layers of your stack.</p><h3><strong>Soft Skills</strong></h3><p>Some people like to hate on the term “soft skills”, as if “soft” is a synonym for “bad”. When I think of soft, I think of martial arts. In martial arts, soft and hard techniques are used in different situations. Similarly, in software development, soft and hard skills are both important. There are two big reasons you want to spend a significant amount of time working on soft skills. The first is that soft skills never go out of style. The human brain has been roughly the same configuration for over 50,000 years. While technology and culture change, basic human nature does not. The second reason is that what separates you from some inexpensive basement coder is the ability to work with various stakeholders and handle both the technical and non-technical sides of software development. If you want to be a leader, either in the managerial or the technical sense, you need to be able to deal with people.</p><p>Here’s a few soft skills you should work on.</p><h4><strong><em>Communication Skills</em></strong></h4><p>Software is a communication process. Not only do you communicate with machines, but you also need to communicate with people. Learning how to speak and write clearly is an important skill to have on any team. Learning how to listen and ask good questions will help you get to the bottom of technical issues. Additionally, good questioning skills will help you isolate technical problems as well.</p><p>Besides conveying yourself clearly, the world would be a better place if everyone learned non-violent communication and conflict resolution skills. Even the most chill developers (myself included) can get caught up in disputes that can be easily solved with a conversation. While there’s a whole book related to non-violent communication, the biggest take away is to avoid labeling yourself and others. Instead of “you screwed up because you’re a __________”, reform your critique to something more like “You did _________ and it made me feel _______. Would it be possible for you to ________?” If you avoid using labels and judgments, your discussions are going to be much more productive.</p><h4><strong><em>Critical Thinking is Critical</em></strong></h4><p>The human brain was not meant to perceive truth. It was meant to keep us alive. That doesn’t mean the truth is unimportant, but it does mean we have all sorts of cognitive distortions that kept us alive at the cost of truth. Psychologists split our thinking into two different processes. The first is the rational process that weighs all of the options and makes unbiased choices. The second is a much larger emotional and automatic processing part of the brain. This is the part of our brain that makes most of our choices throughout the day. While we can’t live without either half of our brain, we need to realize our blind spots and seek people who think differently to help overcome them.</p><p>By learning to think more critically, we can weigh arguments and arrive at the truth much faster than relying on our emotional processing and luck to eventually stumble across the truth.</p><p><em>If you’d like to learn more about human fallibility, check out </em><a href="https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555"><em>Thinking Fast and Slow</em></a></p><h4><strong><em>Get Some Zen</em></strong></h4><p>Software development can be a very stressful career, especially during crunch time. Learn how to relieve stress in productive ways. Meditation, philosophies that emphasize resilience like Stoicism and Buddhism, and managing your own ego can greatly reduce you pain. The key is to be able to separate your emotions from your actions. Notice when you’re going off the rails and correct yourself.</p><h4><strong><em>Learning how to Learn</em></strong></h4><p>In addition to spending time learning, spend time improving your learning process. With the pace of change, we constantly have to learn new things. Let’s make sure we spend our time as efficiently as possible by managing our learning process.</p><p>There are lots of available resources on how to learn more effectively. A good one to begin with would be <a href="https://www.amazon.com/Make-Stick-Science-Successful-Learning/dp/0674729013/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1526009166&amp;sr=1-1&amp;keywords=make+it+stick&amp;dpID=41Xea-9egML&amp;preST=_SY344_BO1,204,203,200_QL70_&amp;dpSrc=srch">Make It Stick</a>.</p><h3>Take Responsibility, Prioritize, and Focus</h3><p>Technology is ever changing and it’s up to you to take responsibility for your own education.</p><p>Begin by figuring our what kind of career you want to have and what skills you need to achieve that career. If you need advice or information, there are lots of people in the technical community who are willing to help. Feel to hit up the That Conference Slack channel or your local user group.</p><p>Once you know what you want, dedicate a block of time to your leaning. Make a plan and prioritize your learning based on your goals. Focus on high value evergreen skills. Don’t ignore new technologies, but be conscious about how they fit into your career plan.</p><p>Don’t get caught trying to find the perfect planning tool. You don’t need anything fancy to implement this practice. I use a OneNote notebook, but you can do this with a few sheets of paper.</p><p>Block off some time today. By taking control of your education and focusing on the right skills, you can sidestep the infinite treadmill of new technologies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b296705df15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/that-conference/get-the-boring-stuff-right-9b296705df15">Get the Boring Stuff Right</a> was originally published in <a href="https://medium.com/that-conference">THAT Conference</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To Win At Work: Be A Jack of All Trades, Master of One]]></title>
            <link>https://medium.com/@dustin.ewers/to-win-at-work-be-a-jack-of-all-trades-master-of-one-13f965be5ad6?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f965be5ad6</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Fri, 03 Feb 2017 04:57:39 GMT</pubDate>
            <atom:updated>2017-02-24T13:01:30.661Z</atom:updated>
            <content:encoded><![CDATA[<p>Want to double your chances for success? Learn something new. Diversify yourself.</p><p>The idea of diversifying yourself by learning new skills is a common idea with many names. Scott Adams calls your mix of skills a “<a href="http://www.inc.com/mikael-cho/why-you-dont-have-to-be-great-at-anything-to-build-a-great-company.html">talent stack</a>“. Each skill you add to your talent stack roughly doubles your chance of success. He claims that you’re better off becoming proficient (top 75%) at a variety of skills is better than trying to become world-class (top 99%) at one. <a href="http://blog.dilbert.com/post/155029617616/the-kristina-talent-stack">Here’s an example of a talent stack in action</a>.</p><p>Brett McKay at the Art of Manliness describes <a href="http://www.artofmanliness.com/2013/04/09/to-succeed-in-work-and-life-be-mr-t/">the T-shaped person</a>. A t-shaped person who has both broad and deep knowledge. A jack of all trades, but master of one. You specialize in a few skills and support them with a broad base of general knowledge. For software developers, this means supplementing your developer skills with skills from other fields.</p><p>I like to think about a portfolio of skills. Like a portfolio of stocks, some skills are rising in value, some skills are dropping in value, and some are steady. Like portfolio of stocks, diversification of skills makes you more valuable.</p><p>Regardless of what you call it, diversifying your skills is important.</p><p>There are several reasons to diversify yourself.</p><p>Each skill you learn means you can do more. Each new skills adds to your usefulness as a person.</p><p><strong>Creativity<br> </strong>The basic process of innovation involves the recombining and transformation of ideas. Each new skill you learn gives you a pile of new ideas you can use to fuel your creativity. Many innovations come from taking skills from one field and applying them to another one. The lean movement in software development borrowed from the lean manufacturing method. Thomas Edison was famous for taking ideas from one field and applying them to another.</p><p><strong>Empathy<br> </strong>The more skills you learn, the more people you can communicate with. Teddy Roosevelt was famous for this. He read several books a day. His broad knowledge allowed him to communicate with people from many different backgrounds. In software development, learning the terminology of business makes it easier to write requirements. Continuous communication with the business is one of the key tenets of agile software development. Learning about business makes that continuous communication much more productive.</p><p>Technology moves at a fast pace. Skills that were valuable a few years ago are worthless today. In some ways, technologists are perpetual beginners. Learning a variety of skills, especially non-technical skills, gives you insurance against obsolescence. Non-technical skills are what separate a senior developer from a junior one.</p><p>Now that I’ve convinced you to learn something new, where do you begin? I’ll give you the classic consultant answer… it depends. You need to make up your own criteria. Look for a combination of what interests you and what’s useful to others.</p><p><strong>Here’s a few of my criteria:</strong></p><p>Does this help me create common ground with other people? Examples: common hobbies, sports</p><p>Does this give me a new viewpoint or a new way of looking at problems? Examples: statistics, psychology, economics, design, art</p><p>Is this applicable to my career? Examples: design patterns, business skills, copy writing, communication skills</p><p>Is this something fun that I can use to make people laugh? Examples: history, weird trivia, humor</p><p>Does this increase my objectivity? Examples: argumentation, Stoicism</p><p>I cultivate a variety of skills. My primary career goal is to use software to solve difficult problems. I tend to focus on skills that help me do more.</p><p><strong>Software Development </strong>— Primary skill set</p><p><strong>Business </strong>— I read a lot of business books and study various aspects of marketing and finance. I’m also into small businesses. Most of us are working for businesses. Knowledge of how businesses work and how the business you’re in works is vital to being a good software developer.</p><p><strong>Psychology</strong> — I love psychology. It gives me a whole new lens when dealing with people. I’m into cognitive and organizational psychology. I look for anything that helps me learn faster or understand human behavior.</p><p><strong>Writing</strong> — Being able to write clearly is essential for all professionals. Writing clearly is thinking clearly.</p><p><strong>Public Speaking</strong> — Public speaking is challenging and useful.</p><p><strong>History</strong> — Those who don’t know history are doomed to repeat it. History also gives me interesting anecdotes to tell at dinner parties.</p><p><strong>Philosophy</strong> — I’m a big of stoic philosophy. It’s a great philosophy for dealing with the chaos of modern life. Finding a practical philosophy of life gives your life structure. Religion works here too.</p><p><strong>Design</strong> — A little design knowledge goes a long way. I’m no artist, but I can make a decent looking app without a designer.</p><h3>How?</h3><p>There are lots of different ways to learn new things. Many of these methods are easy to integrate into your life. We all have a limited amount of time, so I like to use learning methods that capitalize on otherwise wasted time. My primary target is the time I spend in the car. Additionally, there’s so many inexpensive ways to learn new skills. Here’s a few of the ways you can learn some new skills.</p><p><strong>Books</strong><br>The easiest one is to read books. Books are cheap and accessible. If you don’t have a lot of time to read, get yourself an Audible subscription. Most books are also available in audio form.</p><p><strong>Courses<br></strong>College courses are nice, but there are better options. The Great Courses publishes classes taught by leading professors. I like to listen to them on my way to work. You can also access college level courses through moocs like EdX, Coursera, and iTunes U. Additionally, Udemy has a wide variety of inexpensive courses (wait for their $10 sales).</p><p><strong>Commonplace</strong><br>In order for your hard-won knowledge to be useful, you need to remember it. One method I use to learn better is to keep a commonplace book. A commonplace book is a collection of notes and quotations from the things you’ve read. This used be a common practice, but it’s coming back as people discover how useful it is. I record notes on anything interesting that I read. I also collect scraps of articles and interesting quotations. I keep these in a OneNote notebook that I can refer to. I also review things I’ve read before and add to my commonplace file. This cycle of note taking and review helps me get more out of what I read.</p><p><strong>Organizations / Clubs</strong><br>There’s a meetup for everything. Go find a group of people you can learn from. It’s often easier to talk to someone than to scour the Internet for resources. I’m looking into more agile groups to expand my business skills.</p><p><strong>Make Stuff</strong><br>This is one of the best ways to pick up new skills. If it’s a “maker” skill, like design or programming, build something. Side projects are a great way to learn something new. If it’s not a “maker” skill, like psychology, make something with the knowledge. Write a blog post or a talk. I never feel like I’m proficient until I use my knowledge to make something.</p><h3>Conclusion</h3><p>If you want to be more successful, learn a new skill. Each new skill makes you a more useful person. If you want to be more creative, diversify yourself. Diverse knowledge gives you more resources to draw from. If you want to win at work, be a jack of all trades, master of one. There are lots of learning resources at your disposal. Put them to work for you.</p><p><em>Originally published at </em><a href="https://dustinewers.com/to-win-at-work-be-a-jack-of-all-trades-master-of-one/"><em>dustinewers.com</em></a><em> on February 3, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f965be5ad6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Deal With Tech Overload: Focus on Value]]></title>
            <link>https://medium.com/@dustin.ewers/how-to-deal-with-tech-overload-focus-on-value-1d5452aa3b4f?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d5452aa3b4f</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 05:56:39 GMT</pubDate>
            <atom:updated>2017-02-24T12:56:01.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8wH7XsCyVYubN4AW." /><figcaption>By walknboston (Flickr: Gavel) [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons</figcaption></figure><p>The technology landscape is exploding with new things to learn. From virtual reality to app enabled refrigerators to the JavaScript flavor of the week, we are drowning in new technologies. Unfortunately, none of these new things are cybernetic brain enhancement. We can only learn so much. What criteria can we use to winnow down the technology avalanche and focus on what is important?</p><p><strong>Usefulness should be your primary criteria.</strong></p><p>Let’s unpack that a bit.</p><p>Software is a tool. We use it to build things of value for people. Either our customers, our users, or ourselves. We build to provide valuable software for people. A lot of developers lose sight of this when they look into new technologies. They fall in love with a technology because it’s shiny, or interesting, or scratches an intellectual itch. It’s the old “golden hammer” antipattern. Find something shiny and use it to build everything, even if it’s not the best tool for the job or doesn’t really improve upon existing technologies. We can do better. By focusing on what’s useful, we can skip the majority of new technologies and keep our sanity.</p><p>To figure out what’s useful, we need to ask a few questions. Write down your own answers as you read through this exercise.</p><h3>Who is your audience?</h3><p>As developers, we serve one or more audiences. Each of these audiences has different needs. It’s your job to figure out which audiences you serve (or want to serve) and what they need. Perhaps you are spending most of your time in a full-time job, but want to start your own business. Perhaps you just work for the man. Figure out which audiences you serve and their relative priority. If you want to serve a new audience, think about what you will need to learn for them as well. Additionally, look for synergies. If you have more than one audience, find overlapping technologies.For example, if you want to build your own business on the side, use a similar tech stack to the one you use at your job.</p><p>Here’s a few audiences you can serve:</p><p><strong>Employer</strong></p><p>Your employer usually works with a specific tech stack in a certain industry. Focus your efforts on their current tech stack, new versions of that stack, and new technologies that would fit well within their current environment. If you work at a .NET shop, don’t waste your time on Java. If you work on a native iOS or Android team, learning Ionic is a bad plan. Find technologies that help business units create more value. If you don’t know how your business operates, add that to your “to learn” list.</p><p>A good example of a useful technology would be Docker. Docker allows for faster and more consistent deployments, which helps improve time to market. This can give a business a real competitive advantage. Another good example would be mastering performance tuning in your particular stack. Lot’s of case studies show performance adds to the bottom line.</p><p><strong>Public Code / OSS</strong></p><p>Open source projects have different goals than enterprise shops. There’s some overlap, but OSS is built differently. If you do OSS, figure out which projects you want to contribute to and focus on their tech stacks. Also think about what value you can bring to the developer community.</p><p><strong>Small Business</strong></p><p>If you run an app business or an ISV (independent software vendor), focus on technologies that create customer value. For example, while functional programming is cool, you’re better off mastering digital marketing or product design instead. Focus on technologies that help you get products in front of customers quickly. This doesn’t always mean new technology. There are a lot of Rails 2, jQuery, and ASP.NET Webforms apps out there still generating significant value for their customers.</p><p><strong>Self</strong></p><p>It’s OK to learn something just for fun. Lots of people write code as a hobby, but make sure you understand that the time you spend building robots or smartwatch apps is hobby time, not professional development time.</p><p>I have three audiences. I work on a team that builds data driven applications using .NET Core, Angular 2, TypeScript, and Spark. I also serve the broader technical community by speaking at conferences and blogging. Eventually, I want to build a small software product and sell it. I achieve synergy by focusing my community efforts on things that I either use in my day-to-day work (like Angular 2) or things that will serve me in business (innovation).</p><h3>What makes you special?</h3><p>What special qualities do you bring to the table? Are you an amazing debugger? Are you a UX genius? Are you good at cutting to the core of team issues? Do you have an underrepresented perspective? Everyone has specific skills that are both unusual and valuable. Focus your development efforts on expanding and complementing what makes you special. For example, if you’re a talented at building user interfaces, spend the time to skill up on Angular 2 or React. If you’re the performance expert, check out that shiny new profiling tool. It’s often better to expand a strength than moderate a weakness.</p><p>I know more about UX and front end development than most of the .NET developers I work with. I’m also good at keeping my cool when things get crazy. People have called me “Spock” before, which I take as a compliment. I also have a variety of non-developer skills, like public speaking and psychology, that allow me to think differently.</p><h3>What do you already know?</h3><p>Take inventory of your current skills. Focus your efforts on technologies that expand what you can do with your current skills. For example, if you know Ember and Angular 2, investing effort in learning React is going to net you diminishing returns. However, investing in Web API, Electron, or Ionic will add new capabilities to your skillset. Realize that specific technologies fade with time, but investing in fundamentals is always a good bet. Who knows what the JavaScript ecosystem is going to look like next year, but knowing the fundamentals of JavaScript, performance optimization, and UX will still be valuable.</p><p>My current skill set revolves around Angular 2, TypeScript, SQL Server, and ASP.NET MVC. I want to learn more about data tools, especially the ones in Visual Studio. The Microsoft ecosystem is gaining some interesting data capabilities that can add a lot of value. I may also do an exploration of Ionic 2 and progressive web applications. Both of those are good ways to use existing skills in a new way. I’m also working on my public speaking and written communication. Communications skills never become obsolete.</p><h3>Practical Application</h3><p>Now that you know what’s useful for your situation, let’s use that knowledge to make your life easier. You likely have a list of technologies that you’re interested in or feel obligated to keep up with. <a href="https://dustinewers.com/building-tech-radars-for-fun-and-profit/">I have a whole radar of them.</a> Take that list and run it through the criteria you figured out. If the technology doesn’t help you add value to one of your audiences, cross it off the list. Rank everything else based on its relative value. Use your criteria to combat “shiny object” syndrome when you encounter a new technology. You’ll likely still have more things on your list than you can learn, but your list should be manageable.</p><p>If you want to survive the constant stream of new technologies with your sanity intact, make your primary technology criteria value.</p><p><em>Originally published at </em><a href="https://dustinewers.com/focus-on-value/"><em>dustinewers.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d5452aa3b4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Tech Radars for Fun and Profit]]></title>
            <link>https://medium.com/@dustin.ewers/building-tech-radars-for-fun-and-profit-c89c46a0dfec?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/c89c46a0dfec</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[information-overload]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Fri, 23 Dec 2016 05:36:42 GMT</pubDate>
            <atom:updated>2017-02-24T12:59:20.019Z</atom:updated>
            <content:encoded><![CDATA[<p>The technology landscape is exploding. New technologies, platforms, and tools are being creating at an ever-increasing rate. VR, AR, and wearables give us new app stores to target and new experiences to create. Conversational UI (Alexa, Bots, Cortana API) is a totally new way to interact with users, and another dozen different platforms you can target. Even the web space is exploding. It feels like there’s a new JavaScript framework roughly every ten minutes.</p><p>All of the new stuff is amazing, but also exhausting. There’s so many new things out there. Finding your focus is hard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*tOAndJhCkDQU0oZV." /></figure><p>Keeping track of all this new stuff is tough, but we have tools to help us. One of those tools is tech radar. A technology radar is a collection of new technologies and how important they are to you or your organization. You enumerate new technologies and assign them a value somewhere between “run away screaming” and “let’s use this for EVERYTHING”.</p><p>The tech radar was created by Thoughtworks. They publish their radar a couple of times a year. It’s a great snapshot of what technologies they are using in their organization. I recommend you check it out.</p><p><a href="https://www.thoughtworks.com/radar">Thoughtworks Tech Radar</a></p><p>While the Thoughtworks tech radar is great, it’s more fun (and useful) to do it yourself. Neil Ford has a fantastic talk about building your own tech radar. Check it out here:</p><p><a href="https://www.youtube.com/watch?v=ZhKthgQ5uLk">https://www.youtube.com/watch?v=ZhKthgQ5uLk</a></p><p>In his talk, Neil mentions two tech radars. One for your company and one for yourself. After viewing this talk, I was hooked by the idea and decided to give it a try. I’ve worked on both styles of tech radar and learned a few things along the way.</p><h3>Organizational Tech Radars</h3><p>An organizational tech radar is a picture of the technologies used in your company along with recommendations for new things you should keep an eye on. Your team sorts technologies into one of four categories.</p><p><strong>Adopt</strong> — Use when appropriate. This is a default best practice.<br> <strong>Trial</strong> — Use on non-critical projects. Good, but not 100% there yet.<br> <strong>Assess</strong> — Keep an eye on this. Use it for POCs and Demos.<br> <strong>Hold</strong> — Avoid using this on new projects.</p><p>To conduct a tech radar, get representatives of the different teams in your organization together and have them discuss some of the new technologies they are using or interested in using. Assign each technology to the proper category and record the highlights of each conversation.</p><p>Shoot for fewer than 30 people per discussion session. Try to get a diverse slice of your organization’s tech users. If your organization has teams outside of generic enterprise app dev, make sure they get a seat at the table. (examples: designers, SharePoint Devs, Salesforce Devs, DBAs, DevOps, mobile devs, etc… )</p><p>I’m involved in two different organizational tech radars. One as the primary organizer and another as an observer. It’s been an educational and useful experience. I’ve gained insight into some of the dynamics behind how technology is used in these two organizations.</p><p>One of the major benefits of doing a tech radar is that you deepen your understanding of how technology is used in your organization. You also gain insight into what different people are thinking. It can highlight blind spots in your own thinking and surface interesting technologies to check out. Another benefit is that it can make your organization more proactive about technology adoption. By knowing what’s available, you can begin to plan earlier. You also gain consensus about which technologies to adopt. It’s a lot easier than trying to campaign for new technologies on your own.</p><p>It’s not all rainbows and puppy dogs though. I ran into several challenges while coordinating my organization’s tech radar. First, I had to make a special effort to represent all the developer communities in my organization. We have a lot of practices and not all of them came to the discussion meetings. Next time, I may hold special meetings for each group.</p><p>The second hurdle I ran into was that everyone was very focused on things to adopt now, as opposed to future technologies. This issue was relatively easy to solve. We created a new category for “obvious best practices” and focused more on the “trial” and “assess” categories. Don’t be afraid to make tech radar your own. You don’t have to copy Thoughtworks verbatim. I found that making a category for things that aren’t new, but part of your default tech stack, cleared up the “adopt” list and kept the radar future forward. It also provides you with a handy list of architectural recommendations for new projects.</p><p>The final challenge was dealing with all the conversations. It was easy to go off on tangents or get caught up in how you feel about a particular technology. It’s tough to keep on track. One way we addressed the issue was by splitting up the meetings into small chunks. It’s easier to schedule and no one gets burned out from a 4 hour meeting from hell.</p><p>Overall, I found this exercise highly beneficial. I learned a lot and picked up a few technologies for my tech radar.</p><h3>Personal Tech Radars</h3><p>If you’re like me, you have “the list”. Sometimes referred to as “the guilt list”, because I never finish it. It’s the pile of technologies you intend to research. If that sounds vague, that’s because it is. “to research” doesn’t really give you a finishing point. I built a personal tech radar to help clear up that ambiguity.</p><p>For me, a personal tech radar is a much less formal affair than the organization radar. It’s also, by necessity, a smaller one. I changed the definition of the categories. Instead of focusing on adoption, my categories focused on how much effort I want to put into learning the technology. Here are my categories and a few examples for each one.</p><p><strong>Adopt</strong> <br>Agitate for use and learn deeply. This is for your core skills.<br>Examples: .NET Core, Angular 2, TypeScript, Azure</p><p><strong>Trial</strong><br>Seek functional knowledge on. Build a demo apps or POCs.<br>Examples: Python, Spark, R, Progressive Web Apps</p><p><strong>Assess</strong><br>Keep an eye on it, but don’t worry about getting deep knowledge.<br>Examples: Hololens, Unity, Xamarin, Chatbots</p><p><strong>Hold<br></strong>Avoid using when possible. Don’t waste a lot of time learning new things about this tech.<br>Examples: Old ASP.NET, Angular 1</p><p>I only had one challenge with my personal tech radar. I’m interested in everything, so I had a lot of trouble keeping my categories small enough to be doable. I consider this a feature, not a bug. Doing this exercise forced me to take a holistic view about what I’m interested in and edit accordingly. I also did some journaling about where I wanted to go in my career, which helped clarify my thinking. For example, I realized that learning data analysis is a better use of my energy than learning native mobile development. I’m still keeping an eye on mobile, but it’s not a top priority for me. Overall, it narrowed my scope and helped me focus.</p><h3>Conclusion</h3><p>If you want to better deal with the ever-growing deluge of new technologies, consider doing a tech radar. Both the organizational and personal flavors offer insights that you can use in your daily developer practice. It’s a great way to end the year.</p><p><em>Originally published at </em><a href="https://dustinewers.com/building-tech-radars-for-fun-and-profit/"><em>dustinewers.com</em></a><em> on December 23, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c89c46a0dfec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Great Reads for Innovators]]></title>
            <link>https://medium.com/@dustin.ewers/great-reads-for-innovators-27892f59ec9f?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/27892f59ec9f</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Thu, 15 Dec 2016 05:08:51 GMT</pubDate>
            <atom:updated>2017-02-24T13:03:29.037Z</atom:updated>
            <content:encoded><![CDATA[<p>As technologists, we are the vanguard of innovation. We’re at the forefront of technological innovation. Even if you’re slagging COBOL in the basement of some bank, you’re still dragging your organization into the future. Ever wonder how that process actually happens? What can you do to be more creative?</p><p>I’m fascinated by this topic, so I put together a talk about it. (<a href="http://dustinewers.com/speaking/">abstract</a> / <a href="https://goo.gl/7MrmLM">slides</a>) It distills what I’ve learned from reading dozens of books on innovation and the history of technology. To save you some time, I put together a list of my favorite innovation related reads. If you’re curious about this topic, these books are a good place to start.</p><h3>Books for Innovators</h3><h3><a href="http://amzn.to/2hHsoIB">Sapiens</a></h3><p>Sapiens is a highly entertaining, unorthodox view of human history. Not only is it informative, it challenges basic assumptions about ideas that most people don’t realize they’re making. It’s a great description of early human history and how we got to the modern age. It’ll really open up your mind.</p><h3><a href="http://amzn.to/2gNgY4v">Geography of Genius</a></h3><p>Innovation is not evenly distributed. There are certain times and places throughout history that have “golden ages” of innovation. Geography of Genius explores a few of these places and tries to find what ties them all together. This book is very interesting and you’ll learn about some places that you don’t see much of in the classroom.</p><h3><a href="http://amzn.to/2hHmLu2">Evolution of Everything</a></h3><p>Unlike what the history books tell us, innovation is more bottom up than top down. Matt Ridley does a fantastic job describing how in Evolution of Everything. He covers a several major innovations including religion, money, and government. This book challenges many deeply held beliefs and illustrates how innovation is an evolutionary process.</p><h3><a href="http://amzn.to/2gNgviN">Smarter Better Faster</a></h3><p>This book offers a more tactical look at creativity. It’s also a great guide to improving other aspects of mental performance. Charles Duhigg does a fantastic job mixing science with fascinating stories.</p><h3><a href="http://amzn.to/2hvKYD7">Deep Work</a></h3><p>Creativity requires concentration. A commodity in short supply in the modern age. In Deep Work, Cal Newport makes a compelling argument for making “deep work” (focused work) one of your primary priorities. I changed several of my habits after reading this one.</p><h3><a href="http://amzn.to/2hHuI2r">Competing Against Luck</a></h3><p>While I enjoyed the Lean Startup, I felt like it treated innovation more like a roulette wheel than a process you can influence. “Just pivot until you make it big or run out of money.” In Competing Against Luck, Clayton Christensen describes a fantastic intellectual power tool for building new products. The “Jobs to Be Done” theory of innovation. If you want to build a product, I highly recommend this one.</p><h3><a href="http://amzn.to/2hQ0nud">The Righteous Mind</a></h3><p>One of the most important things you can do to become more innovative is empathize with and learn from people whom you disagree with. We live in a society that’s increasingly polarized, but this book the antidote. In the Righteous Mind, Jonathan Haidt explains the moral foundations for different political outlooks and makes a strong case for civility in political discourse. This is a must read if you have trouble dealing with people who don’t share your beliefs.</p><h3>Bonus Materials:</h3><p>Here are a few non-book resources to check out:</p><p><a href="http://kk.org/thetechnium/protopia/">Protopia (Kevin Kelly)</a></p><p>Kevin Kelly’s concept of protopia (as opposed to utopia or dystopia) is really enlightening.</p><p>In <a href="http://amzn.to/2hyrFX5">How to Fail at Almost Everything and Still Win Big</a>, cartoonist and business author Scott Adams describes his “success formula”. Each area you master roughly doubles your odds of great success. This is a great case for diversifying yourself. You can either get his book or read this article:</p><p><a href="http://www.forbes.com/sites/carminegallo/2013/10/23/dilbert-creator-scott-adams-reveals-the-simple-formula-that-will-double-your-odds-of-success/">Dilbert Creator Scott Adams Reveals The Simple Formula That Will Double Your Odds Of Success</a></p><p>If you’re looking to diversify yourself, here are two excellent resources:</p><p><a href="https://personalmba.com/best-business-books/">Personal MBA</a></p><p>The Personal MBA is a reading list that’s meant to give you the business skills taught by an MBA program. I’ve read many books on this list and have not been disappointed. It’s also got great selections on personal finance and psychology.</p><p><a href="http://www.thegreatcourses.com/">The Great Courses</a> (<a href="http://amzn.to/2hPUltE">Amazon</a>)</p><p>The Great Courses are a series of college level lectures that you can listen to in your car. Personally, I’m a big fan of their history selection. They also have courses on psychology, philosophy, and business.</p><p><a href="http://news.mit.edu/2013/why-innovation-thrives-in-cities-0604">Why Innovation Thrives in Cities</a></p><p>Innovation is partly a network effect. This article describes why cities with a higher population density have higher per capita rates of innovation.</p><p>Everything is a Remix is a video series about cultural innovation by Kirby Ferguson. I have yet to find a better description of how culture is generated by remixing other cultural elements.</p><p><a href="https://www.youtube.com/watch?v=nJPERZDfyWc">https://www.youtube.com/watch?v=nJPERZDfyWc</a></p><p>This is a TED talk on how Google X (Google’s own skunkworks company) takes risks and creates a culture that fosters psychological safety.</p><p><a href="https://www.ted.com/talks/astro_teller_the_unexpected_benefit_of_celebrating_failure">https://www.ted.com/talks/astro_teller_the_unexpected_benefit_of_celebrating_failure</a></p><h3>Conclusion</h3><p>This list of resources will open your mind and help you become a better innovator. If you think I missed something, feel free to drop it in the comments.</p><p><em>Originally published at </em><a href="https://dustinewers.com/great-reads-for-innovators/"><em>dustinewers.com</em></a><em> on December 15, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27892f59ec9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Tips To Help You Ace Your Next Technical Interview]]></title>
            <link>https://medium.com/dustin-ewers/3-tips-to-help-you-ace-your-next-technical-interview-f6dc244252f7?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6dc244252f7</guid>
            <category><![CDATA[technical-interview]]></category>
            <category><![CDATA[interviewing-tips]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Tue, 11 Aug 2015 12:32:01 GMT</pubDate>
            <atom:updated>2015-08-11T12:32:01.780Z</atom:updated>
            <content:encoded><![CDATA[<p>3 Tips To Help You Ace Your Next Technical Interview</p><p>I used to be a little nervous about doing technical interviews. Even though I spend much of my free time learning about technology, I’m still afraid that I’ll be perceived as an idiot. To combat this feeling, I have developed several practices to improve my interviewing skills.</p><h4>1. Review Your Resume</h4><p>Every interview I’ve been to asks you for examples from your work history. To prepare for these types of questions, review your resume before each interview. For each job on your resume, think about the challenges you faced, what technologies you used, and what you were proud of. Think about stories you can tell from previous jobs to potential employers. Practice telling those stories in your head or in front of a mirror. This exercise <a href="http://en.wikipedia.org/wiki/Priming_(psychology)">primes</a> your brain. When prompted, you will be ready with a story from your work history.</p><h4>2. Practice Answering Standard Technical Questions</h4><p>Depending on the technology stack and what job you are interviewing for, most employers ask a list of standard questions. Each technology stack has a different set of standard questions. You will get a feel for this list as you do more technical interviews. I’m an ASP.NET Developer, therefore I get questions on the following topics:</p><ul><li>Basic OOP (Encapsulation, Inheritance, Polymorphism)</li><li>Abstract Base Classes vs Interfaces</li><li>The ASP.NET Page Lifecycle</li><li>String Concatenation using StringBuilders</li><li>Basic Design Patterns</li><li>Linq</li><li>Generics</li><li>Job Specific C# and ASP.NET Trivia</li><li>Major features in new releases of ASP.NET (async, await, etc…)</li></ul><p>To prepare, you need to research the concept, practice describing the concept, and for more complex questions, come up with relevant examples. For example, when describing OOP concepts, come up with a novel example. Instead of the usual examples of vehicles or animals, try something a little different, like a beer factory or different types of ducks. The key here is to show that you understand the concepts, as opposed to being able to memorize a textbook example.</p><h4>3. Practice Your Public Speaking Skills</h4><p>I learned my public speaking skills by competing in college forensics (speech and debate). It was a great experience that has helped me in many ways. I highly recommend competitive speaking if you have the opportunity. If you are no longer in school, you can join <a href="http://www.toastmasters.org/">Toastmasters</a> or practice with a group of your peers. Meetups are a good way to find groups of people to practice with. You can also give presentations at user groups and conferences. Practicing your public speaking skills on a regular basis will help you eliminate filler words from your vocabulary and help you learn how to handle fears surrounding public speaking. If you can explain a complex technical concept to a group of thirty people, then you should have no problem with three people in a job interview.</p><p>For more on how to be a better software developer, check out <a href="http://www.dustinewers.com/">www.dustinewers.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6dc244252f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dustin-ewers/3-tips-to-help-you-ace-your-next-technical-interview-f6dc244252f7">3 Tips To Help You Ace Your Next Technical Interview</a> was originally published in <a href="https://medium.com/dustin-ewers">Dustin Ewers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Get The Most Out Of Criticism]]></title>
            <link>https://medium.com/dustin-ewers/how-to-get-the-most-out-of-criticism-3915de5ea345?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/3915de5ea345</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Fri, 22 May 2015 05:13:38 GMT</pubDate>
            <atom:updated>2016-04-07T12:18:31.261Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever built something you’re proud of, only to have it torn to shreds when you show it your audience? Get burned in a code review? Rejected after a job interview? I know I have. Today, I’m going to write about some strategies to deal with it.</p><blockquote><em>If someone is able to show me that what I think or do is not right, I will happily change, for I seek the truth, by which no one was ever truly harmed. It is the person who continues in his self-deception and ignorance who is harmed. <br> ― Marcus Aurelius, </em><a href="http://amzn.to/1HlJRY4"><em>Meditations</em></a></blockquote><p>One of the most underestimated soft skills of the modern software developer is the ability to take criticism well. This is an industry where things change so quickly that there’s no way to be perfect. There is always someone who knows more than you and even if they don’t know more than you, you can certainly learn from them.</p><p>Besides being bad at taking criticism, most developers are not good at giving good criticism. Anyone can slag another person’s creative output, but how often can someone say something that helps the person they’re critiquing? Being able to deliver a useful critique is almost as valuable as taking one. Software development is a complex craft and being able to help others is essential.</p><h3>On Dealing With Criticism</h3><blockquote><em>One particularly powerful sting-elimination strategy is to consider the source of an insult. If I respect the source, if I value his opinions, then his critical remarks shouldn’t upset me. <br> — William Irving, </em><a href="http://amzn.to/1Q0pvbJ"><em>A Guide to the Good Life: The Ancient Art of Stoic Joy</em></a></blockquote><p>I’m going to define criticism broadly. To me, criticism includes any comments you receive on your creative work. It includes well meaning advice, sharp attacks, and trolling. It also includes situations when you don’t get picked for the job, get passed over to speak at a conference, or lose a contest. Call it criticism from life. Regardless of the source and intent of the criticism, the following tips apply.</p><p><strong>Don’t take it personally.</strong></p><p>Even if someone meant to harm you, you choose how you respond to criticism. You can choose not to interpret it as insult. At the end of the day, all criticism is information. Treat it like any other data stream. Some data is higher in quality, some data is lower in quality, but it’s all just data.</p><p>The reality is the people who sling insults are not doing it because of you, they’re doing it because of their own issues. You can’t control them, but you can control you.</p><p><strong>Mine for actionable feedback.</strong></p><p>When someone criticizes your work, even if they were trying to hurt you, look for things you can improve on. For example, let’s say your users throw some scathing criticism your way in a product review. While it’s easy to get angry or frustrated, try to figure out the root cause of their pain and use it to improve the product. If you get rejected for a job, try to think of where you went wrong and fix those things in future interviews. Remember, failure is temporary. Learning is everything.</p><p>Sometimes, you are going to get comments that have no useful information. Trolls excel at leaving useless criticism. If you can’t find actionable advice, then disregard the comment. Remember, people being mean is their fault, not yours.</p><p><strong>Consider the source.</strong></p><p>Like in the quotation above, it’s important to consider who is criticizing you. Do you respect them? Are they considered experts this particular area? Do they adhere to the same philosophy as you? Use these considerations to weigh comments. Do you think that Peter Thiel, Elon Musk, Ray Kurzweil and others like them care one shred about what luddites think about them? I doubt it.</p><h3>On Giving Good Criticism</h3><p>Giving good criticism is almost as important as being able to take criticism. Being able to deliver useful feedback to your peers helps them grow. Being able to do it in a way that doesn’t make them hate you is good too. Here are a few tips to help you with that.</p><p><strong>Be mindful of other people’s egos.</strong></p><p>While it’s easy to say that you should make all criticism into dispassionate feedback, actually doing it is hard. I still have a ways to go myself. Because of this, you should make it as easy as possible for the person you are critiquing to turn what you say into useful feedback. An important way to do this is by being mindful of their ego.</p><p>Software development is a tough craft. People invest their time and energy to get good at it and a well timed insult and can trigger all kinds of pain. If you want to see how fragile people’s egos are, Google “imposter syndrome”.</p><p>To help preserve ego, start with compliments. For example, I attended a session last year that had some content issues. When asked how it went, I started off with the good things about the session. I complemented the presenter on their topic selection and presentation style, which were both excellent. Then I made a point about how they tried to do too much for their time slot. This gave the person something they could use without hurting their feelings.</p><p>Remember that negative feedback has more weight than positive feedback. Start off on a positive note and try to achieve at least a 2:1 ratio of positive to negative comments. (if possible)</p><p><strong>Focus on giving actionable advice.</strong></p><p>Telling someone “that sucks” does nothing useful for either party. You don’t get a better product/employee/code and the person being criticized doesn’t learn anything. Additionally, you’ve angered the person you are critiquing, which benefits no one. Instead, focus on making things better. Try saying “This would be better if…” or “These X things would improve your product because of Y reasons”. Using direct, but non personal phrases focuses the attention to where it needs to be. Remember, there are no bad people, just bad ideas.</p><h3>Conclusion</h3><p>The key lesson for this post is to always look for value in criticism. When someone criticizes you, focus on extracting useful information from the experience. Use it to fuel your abilities to the next level. When critiquing others, try to focus on making it easy for them to find value in your comments. Help them get to the next level. Remember, criticism is just data. You choose how to use it.</p><p><em>Originally published at </em><a href="https://dustinewers.com/how-to-get-the-most-out-of-criticism/"><em>dustinewers.com</em></a><em> on May 22, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3915de5ea345" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dustin-ewers/how-to-get-the-most-out-of-criticism-3915de5ea345">How To Get The Most Out Of Criticism</a> was originally published in <a href="https://medium.com/dustin-ewers">Dustin Ewers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Legacy Systems, Legacy Thoughts]]></title>
            <link>https://medium.com/dustin-ewers/legacy-systems-legacy-thoughts-1b69de1ae36e?source=rss-e4dde4db1eff------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b69de1ae36e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Dustin Ewers]]></dc:creator>
            <pubDate>Thu, 26 Feb 2015 18:56:46 GMT</pubDate>
            <atom:updated>2016-04-10T03:28:34.402Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s nothing like replacing a legacy software system to stoke the fires of self-righteousness. You get to pull some poor users out of the dark ages and save them from a system may have been state of the art last decade, but is junk now. (Ignoring the fact that the old system lasted that long because it did what it what the users wanted it to do.) It’s especially fun when the old system is so laughably bad that it was obsolete the day it was written. Unfortunately, these projects come with a few pitfalls.</p><p>The first pitfall is that you can end up building the same legacy system in a new technology. It’s hard to transfer old paradigms into new ones and if you’re not careful, you can end up repeating old mistakes. I worked at a company that was creating an ASP.NET web app built over an existing database. Many of the tables in this database had no keys or relational data. The original system was built on a mainframe using flat files. When that system was upgraded in the 90’s, the flat files were just copied over. There was no regard to modern relational database structuring. When the ASP.NET version came along, the plan was to just copy over each of the old pages, one by one. Management didn’t take modern web and object oriented practices into consideration. Needless to say there was some debate between the developers and management.</p><p>The second pitfall can come while gathering requirements. When gathering requirements for the new system, it’s easy (and often correct) to reference the old system. There are two problems using the old system as the primary reference for requirements. First, the system sometimes does things a certain way because of technical constraints. I once worked on replacing a system that had lots of batch processes. Many of those processes were not needed because modern systems were fast enough to process those records on the fly. Second, many times, old systems don’t reflect the business practices of people who use them. There are lots of instances where users have to do something convoluted to get their old system to behave how they need it to. Watch out for these types of scenarios, fixing them is a good way to score brownie points with your customers.</p><p>The third pitfall happens when the builders of the new system don’t recognize the advantages of the old system. In the system I mentioned in the first point, the legacy system allowed for rapid keyboard entry. The new system, being a web application, did not optimize for keyboard entry. In the beginning, the developers ignored the users because of the “obvious” superiority of the new way of doing things. Eventually, we realized our error and created a keyboard entry optimized set of web controls. The users were much happier. While it may be fun to mock the old system, you should also pay attention to your users and make sure you aren’t creating a system that’s worse than what they started with. Just because it’s pretty and new doesn’t mean it’s good for the customer.</p><p>In summary: <br> 1. Make sure your new system is using new paradigms. Don’t repeat legacy design. <br> 2. Be careful when gathering requirements from the old system. Especially when it comes to implementation details. <br> 3. Don’t make a new system that’s worse than the system you’re replacing.</p><p><em>Originally published at </em><a href="https://dustinewers.com/legacy-systems-legacy-thoughts/"><em>dustinewers.com</em></a><em> on February 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b69de1ae36e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dustin-ewers/legacy-systems-legacy-thoughts-1b69de1ae36e">Legacy Systems, Legacy Thoughts</a> was originally published in <a href="https://medium.com/dustin-ewers">Dustin Ewers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>