<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Task Machines</title>
    <link>https://taskmachines.com/</link>
    <description>Essays on workflow automation: idempotency and retries, queues versus schedulers, human approval steps, long-running workflows, observability of background jobs, compensating transactions, and when automation does not pay.</description>
    <language>en</language>
    <atom:link href="https://taskmachines.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The Automation Not Worth Building</title>
      <link>https://taskmachines.com/the-automation-not-worth-building/</link>
      <guid isPermaLink="true">https://taskmachines.com/the-automation-not-worth-building/</guid>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      <category>Practice</category>
      <description>Most automation cases are argued on the time the task takes and lost on the maintenance nobody counted. On unstable processes, exception rates, the cost of supervision, and the tasks that should stay manual on purpose.</description>
    </item>
    <item>
      <title>Undo Is a Business Decision</title>
      <link>https://taskmachines.com/undo-is-a-business-decision/</link>
      <guid isPermaLink="true">https://taskmachines.com/undo-is-a-business-decision/</guid>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      <category>Reliability</category>
      <description>Compensation is not rollback. On sagas across systems that never agreed to a transaction, steps with no inverse, ordering compensations by reversibility, and the semantic gap between undoing a change and apologising for it.</description>
    </item>
    <item>
      <title>Nobody Watches the Night Shift</title>
      <link>https://taskmachines.com/nobody-watches-the-night-shift/</link>
      <guid isPermaLink="true">https://taskmachines.com/nobody-watches-the-night-shift/</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
      <category>Operations</category>
      <description>Background work fails without anyone noticing, because there is no user to complain. On staleness as the primary signal, alerting on absence, tracing across queue boundaries, and why a green dashboard proves very little.</description>
    </item>
    <item>
      <title>Work That Outlives the Process</title>
      <link>https://taskmachines.com/work-that-outlives-the-process/</link>
      <guid isPermaLink="true">https://taskmachines.com/work-that-outlives-the-process/</guid>
      <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
      <category>Architecture</category>
      <description>A workflow lasting weeks will survive deployments, restarts and code changes that a request never has to face. On durable state, versioning running instances, timers you cannot trust to memory, and why determinism becomes a constraint.</description>
    </item>
    <item>
      <title>The Step Where a Person Decides</title>
      <link>https://taskmachines.com/the-step-where-a-person-decides/</link>
      <guid isPermaLink="true">https://taskmachines.com/the-step-where-a-person-decides/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <category>Design</category>
      <description>Human approval is a step in the workflow, not an escape from it. On the difference between review and rubber-stamping, timeouts on human steps, context at the point of decision, and what happens when the approver is on leave.</description>
    </item>
    <item>
      <title>A Queue Is Not a Schedule</title>
      <link>https://taskmachines.com/a-queue-is-not-a-schedule/</link>
      <guid isPermaLink="true">https://taskmachines.com/a-queue-is-not-a-schedule/</guid>
      <pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
      <category>Architecture</category>
      <description>Schedulers answer to the clock, queues answer to demand, and confusing the two produces systems that run punctually while falling behind. On triggers, backlogs, lateness and the reconciliation loop that saves both.</description>
    </item>
    <item>
      <title>Retries Are Cheap. Side Effects Are Not.</title>
      <link>https://taskmachines.com/retries-are-cheap-side-effects-are-not/</link>
      <guid isPermaLink="true">https://taskmachines.com/retries-are-cheap-side-effects-are-not/</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <category>Reliability</category>
      <description>A retry is only safe if the step it repeats is safe to repeat. On timeout ambiguity, idempotency keys that come from the caller, dedupe windows, and why retry budgets matter more than backoff curves.</description>
    </item>
  </channel>
</rss>
