<?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>The Date on Jerry Mannel Reghunadh</title>
    <link>https://jerrymannel.me/series/the-date/</link>
    <description>Recent content in The Date on Jerry Mannel Reghunadh</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Jul 2023 23:09:05 -0500</lastBuildDate>
    <atom:link href="https://jerrymannel.me/series/the-date/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 3: After the Date</title>
      <link>https://jerrymannel.me/writing/2023/part-3-after-the-date/</link>
      <pubDate>Tue, 11 Jul 2023 23:09:05 -0500</pubDate>
      <guid>https://jerrymannel.me/writing/2023/part-3-after-the-date/</guid>
      <description>Supporting multiple date formats at the API level sounds convenient. It isn&amp;#39;t. Part 3 on why one standard beats many.</description>
    </item>
    <item>
      <title>Part 2: The Second Date</title>
      <link>https://jerrymannel.me/writing/2023/part-2-the-second-date/</link>
      <pubDate>Mon, 10 Jul 2023 23:08:35 -0500</pubDate>
      <guid>https://jerrymannel.me/writing/2023/part-2-the-second-date/</guid>
      <description>ISO 8601 solves most date-time problems. Part 2 walks through designing the field properly, timezone and all.</description>
    </item>
    <item>
      <title>Part 1: The Date</title>
      <link>https://jerrymannel.me/writing/2023/part-1-the-date/</link>
      <pubDate>Sun, 09 Jul 2023 23:07:38 -0500</pubDate>
      <guid>https://jerrymannel.me/writing/2023/part-1-the-date/</guid>
      <description>Date-time looks like a simple data type until you have to store it. Part 1 of a three-part look at what actually goes wrong.</description>
    </item>
  </channel>
</rss>
