<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nixos on MacWorks</title><link>https://macworks.dev/tags/nixos/</link><description>Recent content in Nixos on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/nixos/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/today/engineer-blogs-2026-05-21/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/engineer-blogs-2026-05-21/</guid><description>&lt;h1 id="engineering-reads--2026-05-21"&gt;Engineering Reads — 2026-05-21&lt;a class="anchor" href="#engineering-reads--2026-05-21"&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 software industry is constantly negotiating the tension between convenience and systemic fragility. Whether it&amp;rsquo;s abdicating code comprehension to LLMs, accepting endemic memory safety and supply-chain vulnerabilities as &amp;ldquo;acts of god,&amp;rdquo; or fighting complex tooling to retain local configuration control, our daily micro-choices compound into the security and maintainability baselines of the systems we operate.&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;[Bliki: Vibe Coding]&lt;/strong&gt; · Martin Fowler · &lt;a href="https://martinfowler.com/bliki/VibeCoding.html"&gt;Source&lt;/a&gt;
&amp;ldquo;Vibe coding,&amp;rdquo; a term coined by Andrej Karpathy, involves prompting an LLM to build software without the developer ever looking at the generated code. Fowler differentiates this from &amp;ldquo;Agentic Programming&amp;rdquo; (where engineers actively review LLM-generated code), arguing that true vibe coding intentionally ignores internal structure to maximize speed. This approach drastically accelerates prototyping and empowers non-programmers, but it heavily trades away correctness, maintainability, and security. LLM hallucinations and non-deterministic edits mean that unreviewed codebases quickly degrade into unmaintainable, vulnerable spaghetti code with a large attack surface. This is a must-read for engineering leaders and practitioners trying to formalize when to use LLMs for throwaway scripts versus robust, reviewed production systems.&lt;/p&gt;</description></item></channel></rss>