<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Services on Entropic Drift</title><link>https://entropicdrift.com/services/</link><description>Recent content in Services 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><atom:link href="https://entropicdrift.com/services/index.xml" rel="self" type="application/rss+xml"/><item><title>Technical Debt Triage</title><link>https://entropicdrift.com/services/technical-debt/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>glen@entropicdrift.com (Glen Baker)</author><guid>https://entropicdrift.com/services/technical-debt/</guid><description>&lt;p>Your team knows there is technical debt. The expensive question is what to fix first.&lt;/p>
&lt;p>I help engineering teams turn vague refactoring concerns into a ranked, reviewed, low-risk improvement plan. The work starts with evidence, filters out noise, and ends with focused pull requests your team can safely review and merge.&lt;/p></description></item></channel></rss>