<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependencies on t0ul</title><link>https://t0ul.com/tags/dependencies/</link><description>Recent content in Dependencies on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/dependencies/index.xml" rel="self" type="application/rss+xml"/><item><title>Why engineers don't patch</title><link>https://t0ul.com/blog/why-engineers-dont-patch/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/why-engineers-dont-patch/</guid><description>&lt;p&gt;&lt;em&gt;Part of a short series on the patch loop: who patches, who does not, and what it would take to close the gap. The research behind these posts is my own, and every number links to its source.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="intro"&gt;Intro&lt;/h2&gt;
&lt;p&gt;I started from an uncharitable place. It seemed crazy to me that engineers will not do the one thing they are paid to do, which is write code and check that it works, because that is all patching is. You bump a version, you run the tests, you ship. So why does half the industry sit on vulnerable dependencies for a year?&lt;/p&gt;</description></item></channel></rss>