<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Engineering on Binary Yoga</title><link>https://yogirk.dev/categories/data-engineering/</link><description>Recent content in Data Engineering on Binary Yoga</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yogirk.dev/categories/data-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>'Merge On False' Is Not the Anti-Pattern You Think It Is</title><link>https://yogirk.dev/posts/merge-on-false-is-not-the-antipattern/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://yogirk.dev/posts/merge-on-false-is-not-the-antipattern/</guid><description>I set out to prove MERGE ON FALSE is an anti-pattern in BigQuery. The data told a different story. The real culprit is unclustered tables and unscoped delete clauses.</description></item></channel></rss>