<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge Management on MacWorks</title><link>https://macworks.dev/tags/knowledge-management/</link><description>Recent content in Knowledge Management on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/knowledge-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/today/engineer-blogs-2026-07-28/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/engineer-blogs-2026-07-28/</guid><description>&lt;h1 id="engineering-reads--2026-07-28"&gt;Engineering Reads — 2026-07-28&lt;a class="anchor" href="#engineering-reads--2026-07-28"&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 prevailing theme across today&amp;rsquo;s reads is the systemic management of bottlenecks, whether that bottleneck is an AI model&amp;rsquo;s context window, the closed doors of a frontier AI lab, or the unwritten knowledge graph of a busy engineering leader. Decentralizing &amp;ldquo;working memory&amp;rdquo;—by explicitly delegating tasks, open-sourcing models, or externalizing thought processes—is required to prevent complex systems from degrading under their own weight.&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;&lt;a href="https://martinfowler.com/rachels-ramblings/intro.html"&gt;Why I’m Writing Rachel’s Ramblings&lt;/a&gt;&lt;/strong&gt; · Rachel
The core claim here is that waiting for technical hypotheses to be fully polished is an anti-pattern that traps valuable industry insights inside a leader&amp;rsquo;s head. Operating as the global CTO of a forward-thinking tech organization requires constant pattern matching across clients and teams, effectively turning the author&amp;rsquo;s brain into a highly associative knowledge graph. However, without a forcing function to externalize these thoughts, this high-context understanding is lost to busy operational schedules and perfectionism. The explicit tradeoff is accepting imperfection; the writing will be fast, early-stage, and occasionally wrong, acting as a release valve rather than a definitive textbook. Engineering leaders who struggle to balance the daily operational grind with the need to articulate long-term technical strategy should read this.&lt;/p&gt;</description></item></channel></rss>