What we're reading this week

David Brooks argues the differentiator in the AI age isn't intelligence but your relationship to mental effort: the paradox of tools that promise to free thinking while eroding the capacity to think. (Atlantic headline: "The People Who Will Thrive in the AI Age".)

Uses the vanished human "calculator" job as an analogy for coding agents: the tool removes mechanical work but makes the underlying intuition more valuable. Skipping the struggle leaves you unable to judge the output.

Distinguishes scepticism-as-conclusion from scepticism-as-identity; the real test is whether you can say what would change your mind. The author turns the knife on his own enthusiast position.

Kent Beck and systems veteran Keith Adams on what happens when the twenty-year software playbook goes blank: Jevons paradox, compute-as-moat, and the flow state of programming traded for something closer to air traffic control.

Mollick's structural read on the shift from co-intelligence chatbots to assigning work to agents: the operator's job is now management, and domain expertise (not profession) predicts how much useful output you extract.

A career-spanning retrospective (TDD, XP, Agile) re-examined for the AI era, with the structural claim that we're failing to accumulate trust at the rate we accumulate code.

Elena Verna complicates the AI-hype consensus with a "Show me" heuristic and a sharp hiring point: AI made average intelligence cheap and handed everyone the vocabulary of expertise, so sounding competent and being competent now diverge.

Hadley Wickham demystifies coding agents by building a minimal one from three tools, then layering in safety and edit tools. A build-it-to-understand-it deep dive.

Carson Gross walks through a concrete hyperscript parser bug fix to show AI's strengths (investigation, tests) and its weakness (clean architecture), narrowly avoiding the "sorcerer's apprentice" trap because he understood the codebase.

When AI can execute any technique flawlessly, value concentrates in aesthetic authorship: the who and why behind a coherent body of work. Cross-domain analysis across art, fashion, film, politics, and business. (Listed in the email as "The Aesthetic Is The Art Now".)

A structural theory that a small audience of the right people beats a mass audience, because prestige converts judgment into influence and judgment is independent of scale.

Firsthand structural analysis of cloud agents going mainstream and engineering work shifting toward "building environments for agents to execute efficiently." Where does engineering value migrate when execution is automated?

Laurence Tratt visibly changes his mind on whether AI needs new languages: AI is strong locally but weak globally, so languages that enforce global properties via local reasoning (Rust's data-race freedom) regain value.

A candid retrospective building a real points-of-interest pipeline where AI got demoted from writing (it hallucinated) but promoted for the subjective taste latent in its weights, and where verification had no ground truth.

Argues creation is a process of becoming where the work transforms the maker, treating frictionless AI output as a structural problem rather than an "AI is the future" opinion piece. Squarely on the question of what to hold onto as execution cost approaches zero.

A first-person reckoning with what should be done by hand versus offloaded to AI when producing words costs nothing. Lands on the core question of what humans hold onto as execution becomes free.

Research-driven analysis (LeadDev 2026 survey) of why engineer motivation erodes as the job shifts from authoring to reviewing, from creating to verifying. Complicates the productivity-only narrative.

A five-person team shipped a tier-one product in 10 weeks by stripping process to a perma-Zoom room and Claude Code, with the PR replacing the PRD. Coordination overhead becomes optional when the model carries state. (Also hits Planning Artifacts.)

A working "software factory" where agents write BAML around the clock, capture failures as "trophies," file tickets, open PRs, and answer CI; humans only decide what counts. A warts-and-all practitioner build.

Werner Vogels on how coding agents invert Amazon's write-first "Working Backwards" process into prototype-first, and reaffirm small autonomous teams. (Also hits Planning Artifacts.)

A practitioner-grounded treatment of design docs as the artifact that articulates hard problems and enables feedback before code is written, with a sharp heuristic for deciding what belongs in the plan.