<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on Entropic Drift</title><link>https://entropicdrift.com/tags/performance/</link><description>Recent content in Performance on Entropic Drift</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>glen@entropicdrift.com (Glen Baker)</managingEditor><webMaster>glen@entropicdrift.com (Glen Baker)</webMaster><copyright>© 2026 Glen Baker</copyright><lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://entropicdrift.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Debtmap 0.16.7: Faster Code Debt Analysis for Real Repositories</title><link>https://entropicdrift.com/blog/debtmap-0167-performance/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><author>glen@entropicdrift.com (Glen Baker)</author><guid>https://entropicdrift.com/blog/debtmap-0167-performance/</guid><description>&lt;p>Static analysis tools usually get judged by what they find. That is fair, but incomplete.&lt;/p>
&lt;p>If a tool takes too long to run, it stops being part of the development loop. Developers stop using it locally. Teams stop running it on every pull request. Eventually it becomes a scheduled report that people read only when something is already painful.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://entropicdrift.com/blog/debtmap-0167-performance/feature.png"/></item></channel></rss>