<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Version Control on MacWorks</title><link>https://macworks.dev/tags/version-control/</link><description>Recent content in Version Control on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/version-control/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/week/blogs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/week/blogs/</guid><description>&lt;h1 id="engineering-reads--week-of-2026-04-02-to-2026-04-10"&gt;Engineering Reads — Week of 2026-04-02 to 2026-04-10&lt;a class="anchor" href="#engineering-reads--week-of-2026-04-02-to-2026-04-10"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="week-in-review"&gt;Week in Review&lt;a class="anchor" href="#week-in-review"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This week&amp;rsquo;s reading reflects a fundamental inflection point: raw LLM intelligence is no longer the bottleneck in software development. Instead, the industry is pivoting toward the hard systems engineering required to constrain probabilistic models—whether through strict data ledgers, living specifications, or formal verification harnesses. The dominant debate centers on how we preserve architectural taste, mechanical sympathy, and system ethics as the mechanical act of writing code becomes increasingly commoditized.&lt;/p&gt;</description></item><item><title>Week 14 Summary</title><link>https://macworks.dev/docs/month/blogs/weekly-2026-W14/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/month/blogs/weekly-2026-W14/</guid><description>&lt;h1 id="engineering-reads--week-of-2026-03-28-to-2026-04-03"&gt;Engineering Reads — Week of 2026-03-28 to 2026-04-03&lt;a class="anchor" href="#engineering-reads--week-of-2026-03-28-to-2026-04-03"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="week-in-review"&gt;Week in Review&lt;a class="anchor" href="#week-in-review"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The industry is undergoing a structural shift from authoring syntax to orchestrating and verifying system state. As probabilistic AI agents commoditize raw code generation, the defining engineering challenge has become building the rigorous deterministic harnesses—and maintaining the strict personal accountability—required to safely control these systems in production.&lt;/p&gt;
&lt;h2 id="must-read-posts"&gt;Must-Read Posts&lt;a class="anchor" href="#must-read-posts"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="#"&gt;tar: a slop-free alternative to rsync&lt;/a&gt;&lt;/strong&gt; · Drew DeVault
Stringing together fundamental Unix utilities often provides a more predictable mental model than complex, dedicated tools. DeVault argues for migrating directories using a simple &lt;code&gt;tar&lt;/code&gt; pipeline over SSH, trading the bandwidth efficiency of &lt;code&gt;rsync&lt;/code&gt;&amp;rsquo;s delta calculations for total cognitive simplicity around path resolution. Engineers tired of wrestling with finicky trailing-slash rules should read this for a refreshing return to composable Unix fundamentals.&lt;/p&gt;</description></item><item><title>2026-04-03</title><link>https://macworks.dev/docs/archives/blogs/engineer-blogs-2026-04-03/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/archives/blogs/engineer-blogs-2026-04-03/</guid><description>&lt;h1 id="engineering-reads--2026-04-03"&gt;Engineering Reads — 2026-04-03&lt;a class="anchor" href="#engineering-reads--2026-04-03"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="the-big-idea"&gt;The Big Idea&lt;a class="anchor" href="#the-big-idea"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Relying purely on probabilistic systems—whether that means the unconstrained memory of LLM agents or pure vector search for recommendations—inevitably breaks down in production. Real-world systems require hard data constraints, from backing agent state with SQL-queryable Git ledgers to tempering semantic similarity with exact algorithmic keyword matching.&lt;/p&gt;
&lt;h2 id="deep-reads"&gt;Deep Reads&lt;a class="anchor" href="#deep-reads"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;[Gas Town: from Clown Show to v1.0]&lt;/strong&gt; · Steve Yegge · &lt;a href="https://steve-yegge.medium.com/gas-town-from-clown-show-to-v1-0-c239d9a407ec?source=rss-c1ec701babb7------2"&gt;Medium&lt;/a&gt;
LLM agents suffer from progressive dementia and a lack of working memory, fundamentally limiting their long-horizon planning capabilities. Yegge argues that the solution is a persistent, queryable data plane called &amp;ldquo;Beads,&amp;rdquo; which serves as an unopinionated memory system and universal ledger for agent work. By migrating from a fragile SQLite and JSONL architecture to Dolt—a SQL database with Git-like versioning—the system eliminates race conditions and merge conflicts, providing a complete historical log of every agent action. This shifts the orchestration paradigm from reading scrolling walls of raw text output by monolithic agents to interacting with a high-level supervisor interface that manages state deterministically. Engineers building multi-agent workflows should read this to understand why robust state management, deterministic save-games, and audit trails are more critical than raw agent reasoning.&lt;/p&gt;</description></item></channel></rss>