<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Field notes — Ezz Ashater</title>
    <link>https://ashater.com/notes/</link>
    <atom:link href="https://ashater.com/notes/feed.xml" rel="self" type="application/rss+xml" />
    <description>Production failures and what changed as a result. A maintained knowledge base, organised by topic — not a blog.</description>
    <language>en</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>&quot;It returned 200&quot; is not the same as &quot;it deployed&quot;</title>
      <link>https://ashater.com/notes/returned-200-is-not-deployed/</link>
      <guid isPermaLink="true">https://ashater.com/notes/returned-200-is-not-deployed/</guid>
      <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
      <category>Operating &amp; reliability</category>
      <description>A container that mounts one specific directory pins that directory at startup. Renaming it during a deploy leaves the container serving the old files forever, with no error and no downtime. Because a catch-all route answers 200 for URLs that do not exist, status-code checks confirm a deploy that never landed.</description>
    </item>
    <item>
      <title>The CDN gave us an address our own country couldn&apos;t reach</title>
      <link>https://ashater.com/notes/cdn-address-the-country-couldnt-reach/</link>
      <guid isPermaLink="true">https://ashater.com/notes/cdn-address-the-country-couldnt-reach/</guid>
      <pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate>
      <category>Operating &amp; reliability</category>
      <description>A CDN answered DNS with two addresses, one of which was blackholed by Egyptian networks. Browsers picked at random, so roughly every other visit stalled about twenty-one seconds before silently falling back. Every monitor, every curl, and every origin check looked perfectly healthy throughout.</description>
    </item>
    <item>
      <title>The CSS rule that stops images loading on iPhones</title>
      <link>https://ashater.com/notes/css-rule-that-stops-images-loading/</link>
      <guid isPermaLink="true">https://ashater.com/notes/css-rule-that-stops-images-loading/</guid>
      <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
      <category>Field engineering</category>
      <description>Setting overflow-x to hidden on html or body turns the document into a scroll container. Native lazy loading then measures against the wrong root, and in Safari the images below the fold never load at all. Chrome usually hides the problem, so it looks like an Apple bug. It is not.</description>
    </item>
  </channel>
</rss>
