<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on My Blog</title><link>https://blog.uptick.be/tags/reliability/</link><description>Recent content in Reliability on My Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 21 Oct 2026 19:10:00 +0000</lastBuildDate><atom:link href="https://blog.uptick.be/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>Pin your versions</title><link>https://blog.uptick.be/posts/pin-your-versions/</link><pubDate>Wed, 21 Oct 2026 19:10:00 +0000</pubDate><guid>https://blog.uptick.be/posts/pin-your-versions/</guid><description>&lt;p&gt;&amp;ldquo;It works on my machine&amp;rdquo; has a close relative: &amp;ldquo;it worked last month.&amp;rdquo; The usual cause is a tool that updated itself.&lt;/p&gt;</description></item><item><title>In praise of boring infrastructure</title><link>https://blog.uptick.be/posts/boring-infrastructure/</link><pubDate>Fri, 09 Oct 2026 08:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/boring-infrastructure/</guid><description>&lt;p&gt;The best infrastructure is the kind you forget about. A blog should survive months of neglect and still be there when you come back.&lt;/p&gt;</description></item><item><title>Rolling back safely</title><link>https://blog.uptick.be/posts/rolling-back-safely/</link><pubDate>Tue, 06 Oct 2026 17:30:00 +0000</pubDate><guid>https://blog.uptick.be/posts/rolling-back-safely/</guid><description>&lt;p&gt;Sooner or later a change goes live that should not have. What matters then is how fast you can undo it, and whether undoing it is safe.&lt;/p&gt;</description></item></channel></rss>