<?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 Kevin Tran on Medium]]></title>
        <description><![CDATA[Stories by Kevin Tran on Medium]]></description>
        <link>https://medium.com/@kevin.tc?source=rss-153dee87c8e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PU-Du0TaxL48mk5P.</url>
            <title>Stories by Kevin Tran on Medium</title>
            <link>https://medium.com/@kevin.tc?source=rss-153dee87c8e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:30:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevin.tc/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[Managing Technical Debt and Continuous Improvement at Inato]]></title>
            <link>https://medium.com/inato/managing-technical-debt-and-continuous-improvement-at-inato-105b44bd4efe?source=rss-153dee87c8e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/105b44bd4efe</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Kevin Tran]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 07:02:05 GMT</pubDate>
            <atom:updated>2025-04-17T07:02:05.293Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding Technical Debt</h3><p><strong>Technical debt</strong> is a common term in software development. It describes the cost of maintaining and updating systems that were built with less-than-ideal design or architecture. It usually happens when developers take shortcuts to deliver something quickly, knowing it’ll need to be cleaned up later. That tradeoff often makes sense, shipping fast is sometimes necessary. If technical debt isn’t managed, it can slow us down, cause bugs, and make engineers sweat more than they should. (ᵕ — ᴗ — )</p><p>It’s almost impossible to avoid technical debt completely. Predicting future needs is hard, and the pressure to deliver quickly often wins over writing perfect code. The trouble is, if debt keeps piling up, it leads to higher maintenance costs, lower productivity, and a drop in software quality. But when it’s handled well, it can actually help teams stay focused and move fast without losing sight of long-term goals.</p><p>At Inato, we don’t pretend we can get rid of technical debt entirely. Instead, we focus on keeping it under control while constantly improving our codebase and infrastructure.</p><p>Here’s how we balance building new features with maintaining a healthy codebase, without losing our sanity. (｡&gt;﹏&lt;)</p><p>For us, managing tech debt isn’t just about fixing code. It’s about investing in the long-term health of the product and making life better for our engineers too. #DevXmatters</p><h3>Our Two-Pronged Approach</h3><p>We tackle technical improvements with two key strategies:</p><h3>1. Weekly Tech Sessions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bKiE3Baqf-YaJ8LP" /></figure><p>Every Friday afternoon, our product engineers hit pause on feature work to focus on technical improvements. These sessions are:</p><ul><li><strong>Cross-team:</strong> Engineers from different squads join forces to make meaningful changes that benefit everyone.</li><li><strong>Collaborative:</strong> We encourage pair programming and mob programming to spread knowledge and avoid silos.</li><li><strong>Time-boxed:</strong> We scope tasks to fit within a half-day, so no one is left staring at an unfinished refactor come Monday.</li></ul><p>Why do this? Well, besides keeping our codebase healthier, it also ensures tech debt doesn’t get swept under the rug until it becomes a full-blown crisis.</p><p>It has already evolved and we mostly focus on work related to our <a href="https://medium.com/inato/building-an-engineering-roadmap-and-strategy-a66433b7ab0f">Engineering Roadmap</a> during these <em>Tech sessions</em>.</p><h3>2. Cooldown Periods for Larger Initiatives</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fcbjSBH232nQFFvG" /></figure><p>For bigger technical improvements that can’t be wrapped up in an afternoon, we schedule cooldown periods between development cycles (we use the <a href="https://basecamp.com/shapeup">Shape Up</a> methodology). During these periods:</p><ul><li>Engineers spend <strong>80% of their time</strong> on planned engineering-roadmap items.</li><li>The remaining <strong>20% is for bugs, experiments, or unplanned technical fixes</strong>.</li></ul><p>This way, we make space for necessary improvements without derailing product development.</p><h3>What Makes a Good Technical Item?</h3><p>Not all tech tasks are created equal. We focus on those that:</p><ul><li>Improve code quality, stability, or developer experience</li><li>Help scale our systems efficiently</li><li>Enhance infrastructure or deployment processes</li><li>Align with our engineering roadmap (because stray refactors are fun but not always useful)</li></ul><h3>Protecting Dedicated Technical Time</h3><p>One of the biggest challenges? Keeping this time protected. As engineering managers, we make sure tech sessions and cooldown periods don’t get hijacked by urgent product requests or last-minute fire drills. The key is treating this work as non-negotiable, because a well-maintained codebase saves us from future headaches.</p><p>This requires ongoing communication within the company to clearly demonstrate the value of our technical work to all stakeholders. At the end of each cool-down, a debrief is shared.</p><h3>Results and Continuous Evolution</h3><p>Since rolling out this approach, we’ve seen:</p><ul><li>More consistent focus on technical debt &amp; larger initiatives on engineering improvements</li><li>Better cross-team collaboration</li><li>Stronger knowledge sharing</li><li>A cleaner codebase with fewer recurring issues</li></ul><p>We also face a couple trade-offs:</p><ul><li>It pushes context switching from delivery</li><li>It can be challenging to fit a topic in an afternoon</li><li>We still have a few maintenance tasks to take care of even though we do our best to automate them (dependencies upkeep using Renovate, infrastructure version updates, etc).</li></ul><p>Of course, we’re always tweaking the process as our team and product grow. What works today might need adjusting tomorrow, and that’s okay.</p><p>We already adjusted our process since the creation of the tech sessions ritual almost 2 years ago. More on that in a later blog post.</p><h3>Take away</h3><p>Managing technical debt isn’t about perfection, it’s about making steady improvements over time. By setting aside dedicated time for this work and fostering a culture of collaboration, we keep our codebase in good shape while continuing to ship features that matter.</p><p>At the end of the day, our goal is simple:</p><ul><li>build great software without letting tech debt slow us down.</li><li>make our developer experience delightful. (˶ᵔ ᵕ ᵔ˶)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=105b44bd4efe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inato/managing-technical-debt-and-continuous-improvement-at-inato-105b44bd4efe">Managing Technical Debt and Continuous Improvement at Inato</a> was originally published in <a href="https://medium.com/inato">inato</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>