Week 22 Summary

Blogs
Software Engineering, Artificial Intelligence, Memory Safety, Static Analysis, Cybersecurity, Nixos, Mac, Command Line, Rss, Self-Hosted, Automation, Future of Work, Jevons Paradox, Coding-Agents, Software Security, Software Testing, Data Portability, Machine Learning, Large Language Models, Webassembly, Mathematics, Systems Engineering, Technical Interviews, Hiring, Talent Assessment, Engineering Management

Engineering Reads — Week of 2026-05-20 to 2026-05-29#

Week in Review#

This week’s reading underscores a collective reckoning with the abstractions we build upon, particularly as AI coding agents stress-test our verification mechanisms. The dominant conversation revolves around the necessary shift from writing code to over-engineering the guardrails around it, while simultaneously confronting the chronic denialism in historically fragile ecosystems.

Must-Read Posts#

[Agentic software development hypothesis] · Marc Brooker · [Source] Brooker formalizes the trajectory of AI code generation by arguing that coding tasks only become trivialized when we possess complete specifications and deterministic oracles. Since the industry rarely produces complete specifications and true deterministic oracles are virtually nonexistent, this piece serves as a necessary reality check for systems thinkers who must recalibrate expectations away from magic and toward the hard realities of system definition.

2026-05-24

Blogs
Artificial Intelligence, Automation, Future of Work, Jevons Paradox

Engineering Reads — 2026-05-24#

The Big Idea#

Attempting to build deterministic models of how AI will automate jobs is a category error akin to the failures of early expert systems. Instead of simply eliminating roles, cheap automation often triggers the Jevons paradox—drastically increasing the volume of work while unpredictably shifting the underlying business models that fund it.

Deep Reads#

[Predicting AI job exposure] · Benedict Evans · Source Evans argues that trying to quantify AI’s impact on specific jobs using rigid taxonomies like O*NET is fundamentally impossible. He draws a sharp parallel to the failure of symbolic AI: just as engineers couldn’t manually encode the logical steps for image recognition, we cannot reduce complex knowledge work into a deterministic checklist of automatable tasks. Back-testing past technological shifts reveals massive secondary effects, such as the Jevons paradox, where automating a costly task like financial analysis simply increases the demand for more analysis rather than reducing headcount. Furthermore, we often suffer from a variant of “Gell-Mann Amnesia,” assuming AI will replace consultants or lawyers because it can generate documents, while forgetting that clients pay for trust and strategy, not just the raw artifact. Engineers building AI products should read this to internalize a humbling historical reality: new technology rarely just executes old tasks cheaper; it unlocks entirely new behaviors that break predictive models.