I’m sorry, but I couldn’t find enough context in the document to answer your query. Try giving me more specific keywords if you think I should know the answer.

Simon Willison — 2026-04-13#

Highlight#

Today’s standout is Simon’s hands-on research into the newly released servo crate using Claude Code. It perfectly captures his classic approach to AI-assisted exploration, demonstrating how quickly you can prototype a Rust CLI tool and evaluate WebAssembly compatibility with an LLM sidekick.

Posts#

[Exploring the new servo crate] · Source Following the initial release of the embeddable servo browser engine on crates.io, Simon tasked Claude Code for web with exploring its capabilities. The AI successfully generated a working Rust CLI tool called servo-shot for taking web screenshots. While compiling Servo itself to WebAssembly proved unfeasible due to its heavy use of threads and SpiderMonkey dependencies, Claude instead built a playground page utilizing a WebAssembly build of the html5ever and markup5ever_rcdom crates to parse HTML fragments.

Engineering Reads — 2026-04-14#

The Big Idea#

The defining characteristic of good software engineering isn’t output volume, but the human constraints—specifically “laziness” and “doubt”—that force us to distill complexity into crisp abstractions and exercise restraint. As AI effortlessly generates code and acts on probabilistic certainty, our primary architectural challenge is deliberately designing simplicity and deferral into these systems.

Deep Reads#

[Fragments: April 14] · Martin Fowler · Martin Fowler’s Blog Fowler synthesizes recent reflections on how AI-native development challenges our classical engineering virtues. He draws on Bryan Cantrill to argue that human “laziness”—our finite time and cognitive limits—is the forcing function for elegant abstractions, whereas LLMs inherently lack this constraint and will happily generate endless layers of garbage to solve a problem. Through a personal anecdote about simplifying a playlist generator via YAGNI rather than throwing an AI coding agent at it, he highlights the severe risk of LLM-induced over-complication. The piece then shifts to adapting our practices, touching on Jessitron’s application of Test-Driven Development to multi-agent workflows and Mark Little’s advocacy for AI architectures that value epistemological “doubt” over decisive certainty. Engineers navigating the integration of LLMs into their daily workflows should read this to re-calibrate their mental models around the enduring value of human constraints and system restraint.

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.

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 — 2026-04-11#

The Big Idea#

Sometimes the most valuable reflection for our craft isn’t found in a new architectural pattern, but in remembering the foundational mathematics and history that made software engineering possible. Recognizing the human element and the monumental historical impact of early computing pioneers provides necessary perspective against the constant churn of modern tooling.

Deep Reads#

Alan Turing play in Cambridge MA · Martin Fowler Martin Fowler steps away from architectural design discussions to highlight the human and historical foundation of our profession, recommending the play “Breaking the Code” currently running at the Central Square Theater. Rather than dissecting a specific technical mechanism, Fowler briefly underscores the monumental contributions Alan Turing made to both theoretical computer science and the survival of free democracies. It is easy to get lost in the noise of ephemeral frameworks, but our entire field rests on Turing’s initial formalizations of computation and his practical cryptographic breakthroughs. While there are no system tradeoffs debated in this brief post, it serves as a stark reminder of the profound impact software and cryptography have on the world stage. Engineers in the Boston area should read this quick recommendation and consider dedicating an evening to understanding the roots of our profession.

Simon Willison — 2026-04-12#

Highlight#

Simon shares a highly practical, single-command recipe for running local speech-to-text transcription on macOS using the Gemma 4 model and Apple’s MLX framework. It is a prime example of his ongoing exploration into making local, multimodal LLMs frictionless and accessible using modern Python packaging tools like uv.

Posts#

[Gemma 4 audio with MLX] · Source Thanks to a tip from Rahim Nathwani, Simon demonstrates a quick uv run recipe to transcribe audio locally using the 10.28 GB Gemma 4 E2B model via mlx-vlm. He tested the pipeline on a 14-second voice memo, and while it slightly misinterpreted a couple of words (hearing “front” instead of “right”), Simon conceded that the errors were understandable given the audio itself. The post highlights how easy it has become to test heavyweight, local AI models on Apple Silicon without complex environment setup.

Engineering Reads — 2026-04-10#

The Big Idea#

As AI abstractions upend our relationship with code, engineering craft is bifurcating: we must simultaneously grapple with emergent, functional behaviors in massive models while deliberately preserving the mechanical, systems-level intuition that historically grounded software ethics.

Deep Reads#

watgo - a WebAssembly Toolkit for Go · Eli Bendersky This piece introduces watgo, a zero-dependency WebAssembly toolkit written in pure Go that parses, validates, encodes, and decodes WASM. The core of the system lowers WebAssembly Text (WAT) to a semantic intermediate representation called wasmir, flattening syntactic sugar to match WASM’s strict binary execution semantics. To guarantee correctness, watgo executes the official 200K-line WebAssembly specification test suite by converting .wast files to binary and running them against a Node.js harness. An earlier attempt to maintain a pure-Go execution pipeline using wazero was abandoned because the runtime lacked support for recent WASM garbage collection proposals. Engineers working on compilers, parsers, or WebAssembly infrastructure should read this for a masterclass in leveraging specification test suites to bootstrap confidence in new tooling.

Simon Willison — 2026-04-11#

Highlight#

The standout update today centers on the release of SQLite 3.53.0, where Simon highlights highly anticipated native ALTER TABLE constraint improvements and showcases his classic rapid-prototyping workflow by using Claude Code on his phone to build a WebAssembly-powered playground for the database’s new Query Result Formatter.

Posts#

SQLite 3.53.0 · Source This is a substantial release following the withdrawal of SQLite 3.52.0, packed with accumulated user-facing and internal improvements. Simon specifically highlights that ALTER TABLE can now directly add and remove NOT NULL and CHECK constraints, a workflow he previously had to manage using his own sqlite-utils transform() method. The update also introduces json_array_insert() (alongside its jsonb equivalent) and brings significant upgrades to the CLI mode’s result formatting via a new Query Results Formatter library. True to form, Simon leveraged AI assistance—specifically Claude Code on his phone—to compile this new C library into WebAssembly to build a custom playground interface.