<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lossy Compression on MacWorks</title><link>https://macworks.dev/tags/lossy-compression/</link><description>Recent content in Lossy Compression on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/lossy-compression/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/today/engineer-blogs-2026-06-19/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/engineer-blogs-2026-06-19/</guid><description>&lt;h1 id="engineering-reads--2026-06-19"&gt;Engineering Reads — 2026-06-19&lt;a class="anchor" href="#engineering-reads--2026-06-19"&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 recurring theme in today&amp;rsquo;s reading is that our standard interfaces—whether they are system metrics, text outputs, or daily tools—are lossy compressions of a much more complex reality. From the hidden user pain masked by mean latency metrics, to the wordless, high-dimensional spaces operating beneath an LLM&amp;rsquo;s text box, the technical lesson is to always understand what critical data is being thrown away by your aggregations and abstractions.&lt;/p&gt;</description></item></channel></rss>