<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Python on katzir.xyz</title><link>https://katzir.xyz/tags/python/</link><description>Recent content in Python on katzir.xyz</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 15:09:20 -0400</lastBuildDate><atom:link href="https://katzir.xyz/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Library as Infrastructure</title><link>https://katzir.xyz/posts/intro/</link><pubDate>Thu, 07 May 2026 15:09:20 -0400</pubDate><guid>https://katzir.xyz/posts/intro/</guid><description>&lt;p&gt;Sometimes sysadmin work can seem relatively thankless&amp;ndash;you can be three layers deep in a log file, tracing why a resource-sharing request silently failed at 2am, even while you realize that &lt;!-- raw HTML omitted --&gt;nobody noticed&lt;!-- raw HTML omitted --&gt;. That&amp;rsquo;s not because the service doesn&amp;rsquo;t matter, but because when infrastructure works, it&amp;rsquo;s invisible. When it breaks, it&amp;rsquo;s a crisis. Just as most of us don&amp;rsquo;t regularly think of the pipes carrying water in and out of home unless something goes awry, digital infrastructure is invisible to most people most of the time. To use a tired phrase, that&amp;rsquo;s a feature, not a bug.&lt;/p&gt;</description></item></channel></rss>