<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Making Data Systems Behave - refresh-cadence</title><link>https://makingdatabehave.com/</link><description/><atom:link href="https://makingdatabehave.com/refresh-cadence/feed.xml" rel="self"/><lastBuildDate>Wed, 22 Jul 2026 14:15:24 +0100</lastBuildDate><item><title>Unreviewed Output Is Provisional Output</title><link>https://makingdatabehave.com/refresh-cadence/2</link><description>&lt;p&gt;Frequent pipeline runs can create provisional output faster than controls, consumers and recovery processes can accept it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Wilson</dc:creator><pubDate>Wed, 22 Jul 2026 00:00:00 +0100</pubDate><guid>tag:makingdatabehave.com,2026-07-22:/refresh-cadence/2</guid><category>refresh-cadence</category><category>data-engineering</category><category>dataops</category><category>data-architecture</category><category>data-governance</category><category>data-quality</category></item><item><title>Refresh Cadence Is a Design Decision</title><link>https://makingdatabehave.com/refresh-cadence/1</link><description>&lt;p&gt;Choose pipeline cadence from source change, consumption, recovery and cost rather than treating frequent execution as a default.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Wilson</dc:creator><pubDate>Fri, 19 Jun 2026 00:00:00 +0100</pubDate><guid>tag:makingdatabehave.com,2026-06-19:/refresh-cadence/1</guid><category>refresh-cadence</category><category>data-engineering</category><category>dataops</category><category>data-architecture</category><category>data-governance</category><category>data-quality</category></item></channel></rss>