<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mechanical Sympathy on MacWorks</title><link>https://macworks.dev/tags/mechanical-sympathy/</link><description>Recent content in Mechanical Sympathy on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/mechanical-sympathy/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>2026-04-07</title><link>https://macworks.dev/docs/week/blogs/engineer-blogs-2026-04-07/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/week/blogs/engineer-blogs-2026-04-07/</guid><description>&lt;h1 id="engineering-reads--2026-04-07"&gt;Engineering Reads — 2026-04-07&lt;a class="anchor" href="#engineering-reads--2026-04-07"&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;The defining engineering challenge of our time isn&amp;rsquo;t just writing logic—it&amp;rsquo;s managing the friction between abstraction layers. Whether you are evolving storage interfaces to reduce data friction, stripping away software abstractions to respect hardware cache lines, or using standardized protocols to finally introspect opaque build systems, effective systems design requires knowing exactly when to hide the underlying machinery and when to expose it.&lt;/p&gt;</description></item></channel></rss>