<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Formal Logic on MacWorks</title><link>https://macworks.dev/tags/formal-logic/</link><description>Recent content in Formal Logic on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/formal-logic/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/today/engineer-blogs-2026-07-29/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/engineer-blogs-2026-07-29/</guid><description>&lt;h1 id="engineering-reads--2026-07-29"&gt;Engineering Reads — 2026-07-29&lt;a class="anchor" href="#engineering-reads--2026-07-29"&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;Applying rigorous frameworks to our engineering intuition reveals the hidden realities of software systems. Whether using statistical curves to expose how the slowest 1% of requests secretly consume the majority of your server capacity, or applying formal logic to untangle domain modeling, adopting a more mathematical lens pays outsized dividends in system design.&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;Lorenz and Little: How Much Does Your Tail Cost?&lt;/strong&gt; · Marc Brooker · &lt;a href="http://brooker.co.za/blog/2026/07/29/lorenz-and-little.html"&gt;brooker.co.za&lt;/a&gt;
Tail latency is often treated purely as a customer experience problem, but it is actually a massive driver of system cost and capacity demand. Brooker demonstrates this by using the empirical Lorenz Curve to calculate how much requests above a certain latency percentile contribute to the overall mean latency. Because Little&amp;rsquo;s Law dictates that a request&amp;rsquo;s contribution to mean latency equals its contribution to system concurrency, a p99 latency that contributes 52% of the mean indicates that the top 1% of your slowest requests are occupying 52% of your busy threads. While the exact mapping from concurrency to cost gets complicated in queued or event-based systems, and estimating true percentiles from raw samples introduces statistical noise, the core mechanics hold true. Systems engineers optimizing for cost should read this to understand why ignoring or casually trimming off heavy tails is a mistake when those outliers are precisely what drives your infrastructure bill.&lt;/p&gt;</description></item></channel></rss>