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-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.

Engineering Reads — 2026-05-21#

The Big Idea#

The software industry is constantly negotiating the tension between convenience and systemic fragility. Whether it’s abdicating code comprehension to LLMs, accepting endemic memory safety and supply-chain vulnerabilities as “acts of god,” 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.

Deep Reads#

[Bliki: Vibe Coding] · Martin Fowler · Source “Vibe coding,” 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 “Agentic Programming” (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.