<?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 Adrian Gilliam on Medium]]></title>
        <description><![CDATA[Stories by Adrian Gilliam on Medium]]></description>
        <link>https://medium.com/@adriangilliam?source=rss-c3e3d7e3612a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ssxwkeqJzJVfdYadNOp66Q.png</url>
            <title>Stories by Adrian Gilliam on Medium</title>
            <link>https://medium.com/@adriangilliam?source=rss-c3e3d7e3612a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:11:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adriangilliam/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[Deadlines & Technical Debt: Navigating the Certain]]></title>
            <link>https://medium.com/@adriangilliam/deadlines-technical-debt-navigating-the-certain-785e9862a672?source=rss-c3e3d7e3612a------2</link>
            <guid isPermaLink="false">https://medium.com/p/785e9862a672</guid>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Adrian Gilliam]]></dc:creator>
            <pubDate>Mon, 11 Mar 2024 18:00:10 GMT</pubDate>
            <atom:updated>2024-03-13T20:18:02.810Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pxTfWcqJBOfXNxvt" /><figcaption>DALL·E’s take on the famous <a href="https://en.wikipedia.org/wiki/Death_and_taxes_(idiom)">“death &amp; taxes” line.</a></figcaption></figure><blockquote>In this industry, nothing can be said to be certain except deadlines &amp; technical debt</blockquote><p>Okay, maybe that’s an overstatement, but, when it comes to software engineering, almost every organization struggles to balance the <a href="https://www.villanovau.com/articles/project-management/iron-triangle-project-management/">iron triangle</a> of project management. Just like financial debt, technical debt can be a great tool to move quickly at critical times, and can also be a huge liability if managed irresponsibly. Taking on a little bit of technical debt to bring on a large enterprise customer is very different than building a feature that will eventually require an entire re-write just for a demo. However, the term <em>technical debt</em> generally ends up getting managed the same in either scenario. Furthermore, technical debt can make shipping trivial features into colossal efforts, which reduces the faith of stakeholders in your engineering team.</p><p>I’ve found success in taking the technical debt metaphor a step further and being quite literal about it:</p><ul><li>Shipping <em>x feature</em> faster is going to be a small, consistent burden, but enables us to bring on a new customer/unblocks several other teams/ship a critical feature? That’s a technical debt mortgage with low interest &amp; a predictable cost going forward that you’re using as leverage to get more assets for your team/business.</li><li>Cutting corners to hit an arbitrary deadline, just to immediately face the consequences of slower new feature development? That’s a technical debt credit card with high interest. If you pay it down quickly things might be fine, but this can quickly spiral if left unchecked. Similarly, ask yourself if you can compromise on time or scope to minimize the amount of technical debt incurred.</li><li>Leaving a solo engineer to work on a feature over the weekend because “we just gotta get this done”? That’s a technical debt payday loan with triple digit interest that should be a last resort before it starts bleeding over into burnout and attrition.</li></ul><p>These are just vague examples, but it illustrates the point of not treating technical debt as a one-size-fits-all approach. The size of your business may change how the technical debt is incurred and managed. A startup will need to move a lot faster, but incur less debt on legacy code to deal with. If you’re unsure whether your business can last through the quarter, or even the week, it may be a rational decision to move as fast as possible for your customers and take on riskier debt. On the other side, large enterprises rarely need to take on high interest technical debt for the sake of the business. In large organizations, deadlines often, but not always, stem from 2 core reasons:</p><ul><li>Leadership has set a nice round date (typically the 1st, 15th, or last day of the month) that they would like to hit a milestone by.</li><li>A career milestone (i.e. performance evaluation or promotion case) is depending on this project/feature shipping in time so it can be incorporated into a review.</li></ul><p>It’s critical that organizations carefully think about their incentive structures for individual contributors so they do what’s best for the business, and not necessarily one of the above. An <a href="https://medium.com/swlh/well-that-escalated-quickly-building-better-products-with-escalation-feb259d733c9">efficient escalation path</a> can help bubble up concerns &amp; build a factual basis for why or why not to go into technical debt. One of the key factors in determining whether the liability is worth it is going back to the core of what you’re trying to achieve and thinking about the payback period of your investment. It’s difficult to prescribe what the best payback period might be, but, for most organizations, a quarter is a good floor to test if your debt is worth the cost. In other words, if you need to pay down the debt, with interest, in the span of a quarter, you’re better off taking a more methodical approach and not incurring the technical debt at all.</p><p>Lastly, it’s ideal to avoid this situation altogether with better estimation, but I’ll leave that for a separate post. In the meanwhile, <a href="https://www.amazon.com/Software-Estimation-Demystifying-Developer-Practices/dp/0735605351">this book might help</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=785e9862a672" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retirement and you]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adriangilliam/retirement-and-you-9eded4b369e3?source=rss-c3e3d7e3612a------2"><img src="https://cdn-images-1.medium.com/max/1050/1*C5vtWjaRq9h3EAr0PVfbTw.jpeg" width="1050"></a></p><p class="medium-feed-snippet">Investing a coffee a day, keeps the (retirement) anxiety away</p><p class="medium-feed-link"><a href="https://medium.com/@adriangilliam/retirement-and-you-9eded4b369e3?source=rss-c3e3d7e3612a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adriangilliam/retirement-and-you-9eded4b369e3?source=rss-c3e3d7e3612a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eded4b369e3</guid>
            <category><![CDATA[generation-z]]></category>
            <category><![CDATA[millennials]]></category>
            <category><![CDATA[retirement]]></category>
            <category><![CDATA[personal-finance]]></category>
            <dc:creator><![CDATA[Adrian Gilliam]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 02:37:49 GMT</pubDate>
            <atom:updated>2020-06-23T03:06:47.872Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Finish “Starting”]]></title>
            <link>https://medium.com/@adriangilliam/how-to-finish-starting-6066039e055d?source=rss-c3e3d7e3612a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6066039e055d</guid>
            <category><![CDATA[producivity]]></category>
            <category><![CDATA[starting]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Adrian Gilliam]]></dc:creator>
            <pubDate>Wed, 14 Feb 2018 22:51:48 GMT</pubDate>
            <atom:updated>2018-02-14T22:51:48.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fpyqN-j_OLwM4xZ7l4zkIg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/CxDTMOGnQwU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chris Knight</a> on <a href="https://unsplash.com/search/photos/starting?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Another day, another draft. A month and a half into the new year and there had been several failed attempts to start writing again. Every single prompt I gave myself felt so cliche or too meta. Every time I would start writing I felt the pain of highlighting sentences and backspacing them because I knew they didn’t bring across the message I was hoping for.</p><p>I could bring myself to start writing in the same way a person can bring themselves to the gym on January 1st. It wasn’t starting to start that was the problem, it was the finishing. It was the going to the gym consistently for the entire month of January. It was planning a healthy diet and going through with it. It was planning to get a healthy amount of sleep for more than Saturday night to start your Sunday right; but keep it the whole week. Excuse after excuse would pop up into my head about why I shouldn’t finish my articles. Anything ranging from “oh it’s too embarrassing to expose myself to the whole world” to “well nobody is going to read it so what’s the point?”</p><p>There were countless articles on Medium (or whatever your literary opium of choice is) about how to begin. I knew so well how to begin. Beginning was the sprint when you run at a 5k and you think you’re on top of the world. All these articles were akin to “to run a 5k you must pick up one leg then the other over the course of 5 kilometers, and don’t stop”. These instructions seemed simple enough right? Yet, it isn’t about running the 5k one time with your friends, it’s about building a consistent running schedule brick by brick. Finishing your beginning means learning how to run when none of your friends want to go out, how to run when it’s cold and rainy outside, how to run when you’ve had the worst day and you want to crawl into the corners of your bed and never get up. For me, it was learning how to write without caring what anyone else thought, learning how to accept “good enough” instead of perfect, learning to focus on the message instead of the medium. Doing this wasn’t the destination, it was just how I learned to finish starting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6066039e055d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>