Engineering Reads — 2026-05-28#

The Big Idea#

True systems mastery requires breaking down monolithic black boxes into understandable, isolated components. Whether you are mathematically decomposing a complex signal into orthogonal basis vectors or strictly isolating untrusted code within a mocked WebAssembly sandbox, engineering craft comes down to defining rigorous boundaries and understanding the mechanisms beneath the abstraction.

Deep Reads#

Notes on Fourier series · Eli Bendersky The trigonometric Fourier series is more than a signal processing trick; it is deeply rooted in linear algebra within a Hilbert space. Bendersky walks through the mechanics of decomposing a periodic function into an infinite sum of sinusoids, demonstrating how the integral formulas for coefficients are actually just projections calculating the dot product of a function against orthogonal basis vectors. The post grounds these continuous concepts with practical constraints, noting that functions need only be square-integrable and piecewise smooth to guarantee pointwise convergence. It bridges the gap between pure math and engineering intuition, trading abstract analysis for concrete examples like complex exponentials and periodic extensions of non-periodic intervals. Engineers looking to build intuition for frequency-domain transforms or those rusty on the linear algebraic foundations of signal processing should read this.

Simon Willison — 2026-05-28#

Highlight#

Anthropic’s release of Claude Opus 4.8 brings welcome improvements to model honesty and prompt caching, which Simon immediately put to the test using his newly updated llm-anthropic CLI plugin to generate SVGs of pelicans riding bicycles.

Posts#

Claude Opus 4.8: “a modest but tangible improvement” Simon highlights Anthropic’s refreshing honesty in marketing this release as an incremental upgrade, noting the model’s decreased hallucination rate achieved by simply abstaining when uncertain. Key technical changes include a reduced prompt cache minimum of 1,024 tokens and the ability to insert system messages mid-conversation, which preserves cache hits and reduces input costs in agentic loops. He tested the model by generating SVG pelicans riding bicycles at different thinking levels via his LLM CLI, using Opus 4.8 to build the rendering HTML tool and relying on GPT-5.5 as a “code security blanket” to patch XSS vulnerabilities.

Engineering Reads — 2026-05-29#

The Big Idea#

The standard multi-round technical interview is a fundamentally flawed simulation of work that yields terrible predictive signal and massive false positive/negative rates. It is slowly being replaced by a “campfire” model of paid, provisional work where candidates ship real tickets on an actual codebase, trading the low-fidelity noise of algorithmic whiteboarding for the high-fidelity assessment of real execution.

Deep Reads#

The Last Technical Interview · Steve Yegge Yegge argues that the standard tech interview loop is a statistically bankrupt pseudoscience that functions primarily as an unconscious bias filter and a “do I like you” dating round. Drawing from decades of internal data gathered via Amazon Bar Raisers and Google Hiring Committees, he points out that interviewer consensus is rare and interview scores correlate incredibly poorly with actual on-the-job performance. The proposed solution abandons work simulation entirely in favor of a “campfire” model: bringing candidates in to tackle real tasks on real codebases alongside the actual team over a few days. To solve the historical incentive problem—where senior engineers logically refused the risk of temporary, try-before-you-buy employment—Yegge suggests making these contributions portable. This means allowing candidates to walk away with a verified, compounding reputation stamp for their work regardless of the final hiring outcome, transforming the interview from an operational cost center into a mutually beneficial proof-of-work mechanism. Engineering leaders and hiring managers should read this to rethink how they extract signal from their hiring pipelines before the industry fully shifts beneath them.

Engineering Reads — Week of 2026-05-14 to 2026-05-21#

Week in Review#

This week’s engineering discourse centers heavily on the boundaries of control, specifically how we constrain non-deterministic LLMs into predictable workflows and stop abdicating technical responsibility to our tools. Whether it is defining rigorous feedback loops for coding agents, fighting the structural normalization of memory-safety vulnerabilities, or reclaiming local execution capabilities for frontier AI, the mandate is clear. The mature engineering response to modern complexity is to establish rigorous, observable boundaries rather than surrendering to the path of least resistance.

Engineering Reads — Week of 2026-03-28 to 2026-04-03#

Week in Review#

The industry is undergoing a structural shift from authoring syntax to orchestrating and verifying system state. As probabilistic AI agents commoditize raw code generation, the defining engineering challenge has become building the rigorous deterministic harnesses—and maintaining the strict personal accountability—required to safely control these systems in production.

Must-Read Posts#

tar: a slop-free alternative to rsync · Drew DeVault Stringing together fundamental Unix utilities often provides a more predictable mental model than complex, dedicated tools. DeVault argues for migrating directories using a simple tar pipeline over SSH, trading the bandwidth efficiency of rsync’s delta calculations for total cognitive simplicity around path resolution. Engineers tired of wrestling with finicky trailing-slash rules should read this for a refreshing return to composable Unix fundamentals.

Simon Willison — Week of 2026-03-30 to 2026-04-03#

Highlight of the Week#

This week highlighted a monumental shift in the open-source security landscape, marking the sudden end of “AI slop” security reports and the arrival of a tsunami of high-quality, AI-generated vulnerability discoveries. High-profile maintainers of the Linux kernel, cURL, and HAPROXY are reporting an overwhelming influx of legitimate bugs found by AI agents, fundamentally altering the economics of exploit development and forcing open-source projects to rapidly adapt to a massive increase in valid bug reports.

Engineering Reads — Week of 2026-04-02 to 2026-04-10#

Week in Review#

This week’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.

Simon Willison — Week of 2026-04-04 to 2026-04-10#

Highlight of the Week#

Anthropic’s decision to delay the general release of their highly capable Claude Mythos model under “Project Glasswing” marks a significant turning point in the AI industry. The move underscores a massive shift in frontier model capabilities, as models evolve from generating text to autonomously chaining multiple minor vulnerabilities into sophisticated exploits, requiring a new level of security safeguards before release.

Engineering Reads — Week of 2026-04-08 to 2026-04-16#

Week in Review#

This week’s reading is dominated by the tension between raw, AI-driven generation and the enduring necessity of classical engineering discipline. As AI commoditizes rote code generation, the defining characteristics of engineering are migrating from writing syntax to exercising architectural taste, writing clear specifications, and deliberately bounding probabilistic systems with human constraints. The consensus is clear: creating output is increasingly trivial, but owning the execution mechanics and maintaining systemic intuition requires a conscious, hands-on imperative.

Simon Willison — Week of 2026-04-11 to 2026-04-17#

Highlight of the Week#

This week’s most striking revelation came from Simon’s infamous “pelican riding a bicycle” SVG generation benchmark, where a 21GB quantized local model (Qwen3.6-35B-A3B) unexpectedly outperformed Anthropic’s brand-new Claude Opus 4.7 flagship. Running locally on a MacBook Pro via LM Studio, Qwen generated a better bicycle frame and even won a secret unicycle backup test, leading Simon to conclude that his joke benchmark’s long-standing correlation with general model utility has finally broken down.