
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Ryan Todd</title>
      <link>https://ryantodd.dev/blog</link>
      <description>Notes on AI, operational automation, cloud infrastructure, and platform engineering.</description>
      <language>en-us</language>
      <managingEditor>rmtodd618@gmail.com (Ryan Todd)</managingEditor>
      <webMaster>rmtodd618@gmail.com (Ryan Todd)</webMaster>
      <lastBuildDate>Tue, 03 Nov 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://ryantodd.dev/tags/observability/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://ryantodd.dev/blog/the-tool-couldnt-tell-me-if-it-was-working</guid>
    <title>The Tool Couldn&#39;t Tell Me If It Was Working</title>
    <link>https://ryantodd.dev/blog/the-tool-couldnt-tell-me-if-it-was-working</link>
    <description>A small scheduled Lambda emailed me a report every evening for three months, and nothing I had shipped could say whether it worked. Fixing that surfaced the same failures I see in production systems: config drift between package and deploy, retention that deletes the record, jobs that fail by not running, and metrics measured against the wrong baseline.</description>
    <pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate>
    <author>rmtodd618@gmail.com (Ryan Todd)</author>
    <category>sre</category><category>observability</category><category>aws</category><category>lambda</category><category>side-projects</category>
  </item>

    </channel>
  </rss>
