<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Technical-Debt on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/technical-debt/</link>
		<description>Recent content in Technical-Debt on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 03 Mar 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/technical-debt/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Technical Debt: Not All Debt Is Bad</title>
				<link>https://dplabs.tech/blog/technical-debt-not-all-bad/</link>
				<pubDate>Mon, 03 Mar 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/technical-debt-not-all-bad/</guid>
				<description>&lt;p&gt;Ward Cunningham introduced the technical debt metaphor to explain to non-technical stakeholders why code needed to be refactored. The analogy to financial debt was deliberate: sometimes you borrow money to move faster, and the interest compounds over time until the debt needs to be paid.&lt;/p&gt;&#xA;&lt;p&gt;Over time, the metaphor has been stretched to cover every imperfect thing in a codebase. This is not useful. Not all debt is the same. Not all debt should be paid down.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
