<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Quality on Seaway Labs</title><link>https://seawaylabs.ca/tags/code-quality/</link><description>Recent content in Code Quality on Seaway Labs</description><generator>Hugo</generator><language>en-ca</language><copyright>© [Seaway Labs] 2026</copyright><lastBuildDate>Wed, 12 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://seawaylabs.ca/tags/code-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>The Real Cost of a Poorly Documented Codebase</title><link>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</link><pubDate>Wed, 12 Feb 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</guid><description>&lt;p&gt;Technical debt has a perception problem. It gets discussed as a future concern — something to address when the product is bigger, the team is larger, there is finally a quiet quarter. There is never a quiet quarter.&lt;/p&gt;
&lt;p&gt;The debt is accruing right now, in the absence of documentation, in the architectural decisions that exist only in the memory of whoever made them, in the code that has never been explained to anyone. The cost is not deferred. It is distributed invisibly across every hour your team spends working in the codebase.&lt;/p&gt;</description></item></channel></rss>