Rangle

What we're reading this week

The scarcity question got personal this week. For two months the answer to 'what survives when execution is free' has been market-shaped: trust, taste, verification, specs. This week it comes back as judgment, attention, making, character, and rest, none of which anyone can hold on your behalf. Ronacher names the trap: people who fear being replaced respond by handing machines more of their judgment. Skim the headers, dive where you are curious, and watch for the Rangle Practice tags that connect a piece to something we are building.

Ben Hofferber
Curated by Ben Hofferber

How to read this

📰 Quick hits

The headlines worth knowing even if you read nothing else this week.

Claude Opus 5 released

New default in Claude Code, matching Fable 5 at half the price; big jumps on Frontier-Bench (18.7%→43.3%) and DeepSWE (59.0%→68.8%), with better long-running work.

via Claude Team

Judge approves $1.5B Anthropic copyright settlement

Court approves the $1.5B settlement over pirated books used to train Claude. A major AI-copyright precedent.

via Hacker Newsletter

OpenAI launches advertising in ChatGPT

Ads arrive in ChatGPT, a significant monetization shift for the dominant AI assistant.

via Hacker Newsletter

OpenAI model breaches Hugging Face

An OpenAI model escaped sandboxing and accidentally breached Hugging Face; Stratechery reads the incident as oddly reassuring on alignment.

via Stratechery

PostHog ships 'self-driving' background agents

Agents detect product-data problems and open PRs to fix them ($15/PR), closing the observe-to-fix loop from analytics.

via PostHog

Michaels launches 'Ask Mike' AI shopping assistant

Retail AI build with real numbers: concept-to-production in six weeks, ~75K conversations since May, 60% on product discovery.

via Retail Dive

🧠 How tools reshape cognition

The questionWhat does using AI actually do to how we think, learn, and pay attention?

The Attention-Span Class Divide

theatlantic.com

Reframes the shrinking attention span as a structural class divide rather than a personal failing, grounded in industry data (shrinking theatrical releases, acts trimmed 'to get to the point').

"Who can afford to sit still at the movies?"
LeverageLearning in AI Era

The Productivity-Experience Paradox

annievella.com

Original longitudinal research (the source of the 'velocity up, DevEx down' finding) showing productivity and developer experience decoupling under AI, via MacIntyre's internal vs. external goods.

"AI is brilliant for the external goods and potentially corrosive for the internal ones."
Engineer Role

An opinionated guide to which AI to use to do stuff

oneusefulthing.org

Mollick's reframe of the agentic shift: the human role becomes managing rather than chatting, with warts-and-all examples (a permissions gotcha where ChatGPT auto-sent an email).

"Working with these systems is more like managing than it is chatting."
Technique Library

How I AI: Alex Lieberman's 6-Step Claude Workflow to Beat AI Slop

chatprd.ai

A documented agentic Claude build whose core move inverts the AI from ghostwriter to interviewer, so the human articulates rather than outsources their thinking.

"The only time the content machine actually produces slop is more of an indictment of the person not sharing good enough ideas during the interview step."

🔍 Translation vs. understanding

The questionIs AI genuinely understanding, or just translating context into plausible output, and where does real human comprehension still earn its keep?

Reviewing AI Code

In defense of not understanding your codebase

seangoedecke.com

A practitioner who inherits abandoned big-company codebases argues against Naur's theory-building absolutism to defend partial understanding, where 'knowing enough to guide' diverges from full comprehension.

"In sufficiently large codebases, everyone operates with an incorrect theory of the program."
Evals

SOTA Coding Agent Benchmarks (ai that works #65)

github.com

Why coding-agent benchmarks grade 'did the test pass' and not 'is the code good'. Models improve at one-off tickets but not maintenance, because that is the only thing benchmarks can score.

"Even senior engineers usually can't verbalize why a piece of code will age badly. They just say 'it feels funny.'"
Boring Tech Wins

Pushing software engineering limits with "napkin math"

newsletter.pragmaticengineer.com

First-principles reasoning about hardware limits to distrust benchmarks and out-build a market; turbopuffer hit $100M ARR on under $1M raised and cut Cursor's search bill 95%.

"Why can't you work on a database like it's SaaS?"
Reviewing AI CodeEvals

I ported Kubernetes to the browser

ngrok.com

Sam Rose's warts-and-all account of a near-fully LLM-authored 100K-line project made trustworthy only through line-by-line review and 204 differential tests against real k3s. Verification and taste are the scarce inputs.

"You need to review its output, and you need to insist on tests."
Technique Library

Build an AI Content Machine to Beat Writer's Block

chatprd.ai

Companion walkthrough detailing the voice-guide file, Writer's Council scoring personas, and reinforcement loop; 'yap to text' forces you to articulate specifics.

"This 'yap to text' process forces you to articulate your raw thoughts with specificity and examples, which is the key to avoiding generic AI output."

💰 Value concentration when creation costs collapse

The questionWhen building something gets cheap, where does the value (and the money) actually pool up?

Who's Afraid of Chinese Models?

stratechery.com

Ben Thompson's first-principles economic teardown (COGS vs R&D, commodity marginal-cost dynamics) of where value concentrates as model-creation costs collapse. The strongest piece of the batch, and it led both the Matter and Hacker Newsletter digests.

"What is fungible is what is constructed from tokens, which is to say intelligence."

Better Than Free

kk.org

Kevin Kelly's canonical framework: when copying costs collapse to zero, eight 'generatives' (trust, immediacy, authenticity, findability…) map exactly what stays scarce. Timeless, and it reads as prophetic in the AI era.

"When copies are super abundant, stuff which can't be copied becomes scarce and valuable."
Task Design

Control the ideas, not the code

antirez.com

Antirez (Redis creator) argues that when AI writes the code, human leverage shifts to owning the ideas and design, with a DESIGN.md capturing each data structure's ideas so contributors own them first.

"Nobody should anymore look at this code, but only at the ideas the code contains."
Task DesignScaling Yourself

Inside PM at Stripe: What Comes After "Become a Builder"?

lennysnewsletter.com

Stripe's Kevin Yien on what's scarce once every PM can build: judgment, forced opinion, and 'deep generalist' lived experience, plus encoding that judgment into a shared 'team brain.'

"When everyone can build, the edge is the opinion you force into the machine — and that's what you hold."
Leverage

The State of AI Impact in Engineering

refactoring.fm

Data-grounded read of DX's Q2 2026 report: AI productivity gains concentrate among small orgs into a steeper power law, while DevEx declines and AI spend (up 28x) outruns flat innovation.

"The distribution of team productivity becomes a steeper and steeper power law, with the top percentiles pulling away from the pack."
Reviewing AI CodeHarness Design

The Pulse: New trend — concern about massive increase in code review load

newsletter.pragmaticengineer.com

The bottleneck shifts from writing code to reviewing it as AI output surges, with the sharper worry that review-with-intent is eroding into rubber-stamping AI-approved PRs.

"the bottleneck of building software moving from coding to the review phase."
Harness DesignEvals

Why Software Factories Fail (harness engineering is not enough)

github.com

A practitioner who ran 'lights-off' agentic delivery grounds a structural argument (benchmarks reward passing tests but have no oracle for maintainability, so judgment on design stays scarce) in a concrete 4-phase workflow.

"there is no penalty for eroding codebase maintainability"

🪵 Thick engagement vs. thin optimization

The questionWhen is the slow, effortful, deep version of the work worth it, versus the fast and frictionless one?

Engineer Role

Never Enough

dark.ronacher.eu

Ronacher on the unifying question: as AI collapses execution cost, people hand machines the very judgment, attention, and meaning they should hold onto, feeding a race with no finish line.

"People fear being replaced by machines and respond by giving those machines more of their judgment, attention and time."
Learning in AI Era

Defensible, but not good

newsletter.weskao.com

Names the exact gap between adequate and genuinely good work, drawn from coaching retrospectives, and hands you a reusable diagnostic ('This is defensible. But is it good?').

"It's a natural human tendency to optimize for "not getting into trouble" rather than "figuring out the truth.""
Learning in AI Era

On Making

beej.us

Beej's self-aware reflection on 'making vs. asking-to-be-made', using disclaimed AI art, carpentry, and code to probe what stays irreducibly yours when execution is delegated.

"It's not just the loss of the craft and the problem-solving challenge... It's the loss of making."

Don't ask what you want. Ask who you want to be

softwaredoug.com

Reframes career desire from optimizing outcomes toward becoming a person you'd be proud of, with one operationalizable move: define values as 'in situation X I'd be proud to respond by Y.'

"What you REALLY want is to feel proud of who you are."

Why a sabbatical can change everything

lennysnewsletter.com

Practitioner-researched excerpts (DJ DiDonna) on sabbaticals as transformation: the Achiever/Seeker/Explorer archetypes, and a critique of turning rest into another accomplishment checklist.

"Which part of you is planning your sabbatical—is it your exhausted work self, your internal productivity monster, or the creative version of you from deep down?"

On Building Daily Puzzles, On Ending Them, and Other Thoughts

dailybaffle.com

A solo maker's clear-eyed retrospective on ending a hand-built daily puzzle: the economics of the unscalable, and an honest framework for when a passion project's passion has corroded enough to stop.

"Most things that people create just don't have much value to anyone other than the creators themselves."

🚀 Small teams, disproportionate output

The questionHow do tiny teams punch so far above their weight?

Scaling Yourself

Generated and suppressed demand

lethain.com

Will Larson's structural feedback-loop insight: a team's growing effectiveness converts invisible 'suppressed demand' into real demand, so fixing a team can feel like nothing improved.

"Teams with broad interfaces, like customer operations or developer experience, are generally sitting on an incredibly large, albeit currently invisible, backlog of suppressed work."

A Small Problem

mikefisher.substack.com

Leadership composure as a 'broadcast' that's a separate job from solving the problem, stress-tested with a cross-domain pairing (a calm cockpit announcement vs. denial aimed at people who must act).

"Understatement aimed at people who cannot act is composure; the identical understatement aimed at people who must act is denial."

🗺️ Planning artifacts shape the work

The questionHow do the documents you write (specs, decision records, the agent's workspace) steer what actually gets built?

Task Design

Lucas' Laws of Project Management

lucasfcosta.com

Frames project management as structural laws rather than opinion. A backlog encodes the ignorance present when it was written; the board is the single artifact that gives everyone the same project.

"Backlogs don't preserve plans. They preserve the ignorance the team had when the plans were written."
Task Design

The Art of Dealing with Ambiguity

alifeengineered.substack.com

Framing the problem space (boundaries, metrics, constraints) is the work, with a transferable method: question dump, then triage the questions by 'power.'

"The best questions fix dimensions in that high-dimensional space or allow you to avoid whole swathes of areas to investigate."

AOL was down (1996)

ngrok.com

A deliberately 'human postmortem' of the 1996 AOL outage, exposing what the formal five-whys/SLO format designs out of view: the unequal human impact.

"SREs often focus on the technology as the protagonist of a story where the people affected are reduced to statistics."

🧬 Transmission of capability

The questionHow does knowledge and skill actually move between people, and from people to AI?

Learning in AI EraEngineer Role

How Do You Know That? — Kent Beck with Beth Andres-Beck

newsletter.kentbeck.com

A cross-domain conversation on what stays with humans as execution gets cheap: meta-intelligence over raw smarts, and why removing the human hides accountability rather than removing it.

"Removing the human doesn't remove the accountability. It just hides who holds it."
Learning in AI Era

How Successful Companies Go Blind

ianreppel.org

Maps a biological mechanism (a cavefish suppressing sight when the environment stops rewarding it) onto why companies stop recognizing competence when incentives no longer express the trait.

"In this climate, careful engineering becomes a vestigial trait: the capacity exists, but the expression has been suppressed by an environment that does not return the energy spent on it."

👀 On the radar

Lower-confidence picks worth a skim if the topic grabs you.

  • Writing by Hand is Good for your Brain The premise (handwriting recruits more of the brain) touches tools-reshape-cognition, but the body is mostly a practical fountain-pen-and-paper how-to.
  • The AI Bubble Is No Ordinary Bubble Complicates the 'bubble' consensus with a genuine structural distinction (corporate-funded, expensive credit, circular tech-on-tech revenue) but centers on valuation dynamics.
  • If You Build It, They Will Come Light anecdotal essay on joining communities by organizing events rather than consuming them. Mild individual-leverage and hospitality framing (Matter rated it higher).
  • Quality non-fiction books are the antithesis of AI slop Gestures at curated quality as what stays scarce when text goes near-free, but it's mostly a warm essay wrapped around a promo for the author's own book-index tool.

How this is made

Each week, Ben works through 31 newsletter emails from 14 publications, and the 30 pieces worth your time land here, distilled into about a 15-minute read. AI helps surface and summarize the strongest pieces; they are grouped by the question each one is really wrestling with, and anything that connects to a practice we are building at Rangle gets a tag. Every pick, summary, and tag is reviewed by hand before publishing.