<?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>Scheduling on Widgita</title><link>https://widgita.xyz/tags/scheduling/</link><description>Recent content in Scheduling on Widgita</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://widgita.xyz/tags/scheduling/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Second-Guessing Cron Expressions</title><link>https://widgita.xyz/posts/2026/04/stop-second-guessing-cron-expressions/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://widgita.xyz/posts/2026/04/stop-second-guessing-cron-expressions/</guid><description>&lt;p&gt;Cron is one of those things I&amp;rsquo;ve been using for twenty-odd years and still occasionally stare at for thirty seconds before committing. Is &lt;code&gt;*/15 9-17 * * 1-5&lt;/code&gt; what I think it is? Does &lt;code&gt;0 0 * * 0&lt;/code&gt; fire at midnight Sunday or Monday? And does that depend on the box&amp;rsquo;s timezone or UTC? Most of the time you can squint and reason your way through it, but &amp;ldquo;most of the time&amp;rdquo; is exactly the kind of confidence level you don&amp;rsquo;t want when the cron in question is the nightly DB backup.&lt;/p&gt;</description></item></channel></rss>