<?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 philtor on Medium]]></title>
        <description><![CDATA[Stories by philtor on Medium]]></description>
        <link>https://medium.com/@philtor?source=rss-adc2c8f5c18e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zv0G4xactxEWByVF.png</url>
            <title>Stories by philtor on Medium</title>
            <link>https://medium.com/@philtor?source=rss-adc2c8f5c18e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:02:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@philtor/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[What’s the most important attribute you need to successfully develop software?]]></title>
            <link>https://medium.com/@philtor/whats-the-most-important-attribute-you-need-to-successfully-develop-software-e92d09504c68?source=rss-adc2c8f5c18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e92d09504c68</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[philtor]]></dc:creator>
            <pubDate>Sun, 11 Jun 2017 21:26:26 GMT</pubDate>
            <atom:updated>2017-06-12T22:32:39.047Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been programming professionally for over 25 years now and I got to thinking the other day (in the shower of course, where all the best thinking happens) about what the most important attribute a developer needs to be successful at software development.</p><p>Intelligence? Sure, but there are a lot of ways to define intelligence these days beyond IQ. It’s an important factor but I suspect we tend to over-value it’s place by turning interviews into a series of grueling Mensa questions.</p><p>Knowledge? Yeah, it definitely helps. Knowing your tools, APIs, libraries — all important, but looking back, I don’t think it’s the <em>most </em>important attribute. Education can be lumped under this category as well. Some of the best developers I’ve worked with didn’t have a formal CS education. They were often self-taught. The existence of good, self-taught developers seems to indicate that this is not the most important factor.</p><p>Imagination? Yes, very, very important. I’d probably put it at #2 or #3.</p><p>In thinking back over various projects &amp; problems I’ve worked on I’d have to say that in my experience the most important attribute is <em>perseverance</em>. A tenacious determination to get to the bottom of what’s causing a bug. Trudging on through the design process until you come up with a good design. Never giving up even in the face of poor (or even non-existent) documentation. I think I have to rate perseverance at or very near the top of important attributes.</p><p>But if I were to now offer you 3 easy steps to develop more perseverance you would probably stop reading and suspect (rightly) that it’s not that easy.</p><p>I’m sure many of us have had a run-in with a bug that almost made us want to throw in the towel. Bugs that lead you several days into the debugger wilderness. After several days seemingly chasing ghosts and wrong theories you start to wonder if perhaps you made the right career choice. Bugs that made you wonder if maybe it was time to quit the software game and start a food cart or build a house out of pallets in the woods and just retire early living off your meager savings subsisting on roots and berries and what you can catch until social security kicks in. Bugs that made you lose <em>hope</em>.</p><p>Hope or hopefulness. Not exactly an attribute as much as a mental state. You need hope to persevere. You need to believe that the bug-from-hell is fixable. You need to believe that there was some kind of rhyme or reason to the inscrutable code base you inherited and now have to maintain. When hope is lost you give up trying to fix that bug-from-hell because you become convinced it’s unfixable. Losing hope will bring most of your work to a halt and leave you drifting. And let’s be honest, it’s pretty easy in this biz to lose hope and give up.</p><p>So what do you do when you find that you’re losing hope of finding a solution to a design problem or bug?</p><p>First off, walk away. No, not to building a house in the woods, more of a temporary time-out. Go for a walk in those woods. Do something else to take your mind off of the problem and get perspective. You’ll be surprised how not directly focusing on the problem at hand will lead you to think of solutions you hadn’t considered before. Taking a nap can also achieve similar results. Don’t try to fight the quicksand.</p><p>Talking to colleagues about the problem can also help. And if you’re the colleague being asked for help, don’t forget that maybe it’s more than technical help being sought — offer some hope as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e92d09504c68" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>