<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Naveen's Substack: Bytes & Biceps: Code]]></title><description><![CDATA[Everything about Code]]></description><link>https://blog.naveensrinivasan.com/s/code</link><image><url>https://substackcdn.com/image/fetch/$s_!qBm5!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1d9952a6-6fef-48a2-87fd-60ec9b8fff06_400x400.png</url><title>Naveen&apos;s Substack: Bytes &amp; Biceps: Code</title><link>https://blog.naveensrinivasan.com/s/code</link></image><generator>Substack</generator><lastBuildDate>Sat, 04 Apr 2026 04:20:47 GMT</lastBuildDate><atom:link href="https://blog.naveensrinivasan.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Naveen]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[naveensrinivasan@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[naveensrinivasan@substack.com]]></itunes:email><itunes:name><![CDATA[Naveen Srinivasan]]></itunes:name></itunes:owner><itunes:author><![CDATA[Naveen Srinivasan]]></itunes:author><googleplay:owner><![CDATA[naveensrinivasan@substack.com]]></googleplay:owner><googleplay:email><![CDATA[naveensrinivasan@substack.com]]></googleplay:email><googleplay:author><![CDATA[Naveen Srinivasan]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Learn the ABCs of System Uptime - MTTD, MTTR, MTBF Explained]]></title><description><![CDATA[TL;DR: This post underscores the criticality of three metrics&#8212;Mean Time To Diagnose (MTTD), Mean Time To Recover (MTTR), and Mean Time Between Failures (MTBF)&#8212;in ensuring software system reliability and stellar user experiences.]]></description><link>https://blog.naveensrinivasan.com/p/learn-the-abcs-of-system-uptime-mttd</link><guid isPermaLink="false">https://blog.naveensrinivasan.com/p/learn-the-abcs-of-system-uptime-mttd</guid><dc:creator><![CDATA[Naveen Srinivasan]]></dc:creator><pubDate>Wed, 21 Feb 2024 16:00:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!gLgP!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe9ac5d16-fe4c-426a-8d93-0a440b6c61af_1678x1000.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em><strong>TL;DR:</strong></em> This post underscores the criticality of three metrics&#8212;Mean Time To Diagnose (MTTD), Mean Time To Recover (MTTR), and Mean Time Between Failures (MTBF)&#8212;in ensuring software system reliability and stellar user experiences. These metrics are crucial to minimizing downtime, as indicated by the 'number of nines' in availability and maintaining servic&#8230;</p>
      <p>
          <a href="https://blog.naveensrinivasan.com/p/learn-the-abcs-of-system-uptime-mttd">
              Read more
          </a>
      </p>
   ]]></content:encoded></item></channel></rss>