<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cognitive-Debt on Left 4 More</title><link>https://left4more.com/tags/cognitive-debt/</link><description>Recent content in Cognitive-Debt on Left 4 More</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Tue, 02 Jun 2026 02:17:20 +1000</lastBuildDate><atom:link href="https://left4more.com/tags/cognitive-debt/index.xml" rel="self" type="application/rss+xml"/><item><title>Cognitive Debt: The Bill We're Running Up Without Noticing</title><link>https://left4more.com/posts/cognitive-debt-the-bill-were-running-up-without-no/</link><pubDate>Tue, 02 Jun 2026 02:17:20 +1000</pubDate><guid>https://left4more.com/posts/cognitive-debt-the-bill-were-running-up-without-no/</guid><description>&lt;p>There&amp;rsquo;s a concept doing the rounds at the moment called cognitive debt, and it&amp;rsquo;s been sitting in the back of my head for a few days now.&lt;/p>
&lt;p>The idea is straightforward. Tech debt is what happens when you cut corners on code quality to ship faster, and then spend the next year paying for it in maintenance hell. Cognitive debt is what happens when you outsource the thinking itself. You ship the thing, it works, but you don&amp;rsquo;t actually understand why it works. The understanding got deferred along with the effort.&lt;/p></description></item></channel></rss>