Rangle

What we're reading this week

This week's pieces keep arriving at the same claim from different directions: as AI pushes the cost of writing code toward zero, the durable work moves upstream into understanding, verification, and specification. Ronacher's Tower of Babel essay is the capstone; Bun's 11-day, $165K Rust rewrite is the price tag. 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.

Kimi K3: open frontier model released

Moonshot ships a new open-weights frontier model, feeding the open/local-model thread.

via Hacker Newsletter

Thinking Machines releases "Inkling," its open-weights model

Mira Murati's lab enters the open-weights landscape.

via Hacker Newsletter

OpenAI's GPT-5.6 lineup (Sol, Terra) lands

Sol as the practical daily-driver, Terra for crisp docs; benchmarked against the Claude family.

via Lenny's Newsletter

OpenAI refashions Codex as the new ChatGPT app

the Mac app is rebuilt around Codex, raising whether OpenAI is abandoning the chat category it pioneered.

via Stratechery

Postgres-in-Rust (pgrust) passes 100% of Postgres regression tests

a data point echoing the AI-era Rust-rewrite feasibility theme.

via Hacker Newsletter

AI memory shortage is driving consumer-electronics price hikes

Apple products and Nintendo Switches get pricier as AI demand for memory chips ripples outward; a structural constraint on the boom.

via Retail Dive: Tech

🧠 How tools reshape cognition

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

Reviewing AI CodeLearning in AI Era

Five studies that are changing how I think about AI in software engineering

getdx.com

a rare research synthesis where five independent papers converge on one story: AI compresses code generation while the real bottleneck shifts downstream to verification and shared understanding. A practitioner openly changing his mind.

"an accumulation of not knowing"
Harness DesignReviewing AI Code

Context engineering with Dex Horthy

pragmaticengineer.com

twelve warts-and-all points from the person who coined "context engineering": the dumb zone, trajectory poisoning, intentional compaction, and a system they threw out after four months of shipping unread code.

"It took three weeks to re-onboard to a codebase no human had ever read."
Learning in AI Era

We should be more tired than the model

vickiboykis.com

agentic coding produces the outputs of writing code without the cognitive processes that build skill; Boykis catalogs concrete friction-adding practices to rebuild your own foundation.

"When I finish an agentic session, I get all the outward signs of having written code, but none of the internal processes that happen when we write code by hand."
Harness DesignTechnique Library

What is "loop engineering"?

pragmaticengineer.com

traces loop engineering from Huntley's "Ralph Wiggum" loop to its productization, holding both the real use cases and the disappointment ("tokenmaxxing," agent drift) that it may be a temporary hack.

"I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops."

Good Tools Are Invisible

gingerbill.org

the creator of Odin on how tools should disappear into cognition rather than become identity or a puzzle-game; the feeling-productive vs. being-productive gap, examined through his own config-fiddling past.

"Good defaults are a form of respect for the user's time"

Why Reading Matters

calnewport.com

Cal Newport uses Ong's Orality and Literacy to argue literacy isn't merely a tool but the technology that produced logic and the independent self, lifting it above the "reading is dying" framing it answers.

"conceptual children born from the mind-shaping power of the written word"

πŸ” 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

The Tower Keeps Rising

lucumr.pocoo.org

Armin Ronacher uses the Tower of Babel as a lens on how agents strip away the coordination friction that used to synchronize human understanding of a codebase. The thematic capstone of the week. (Surfaced by both Hacker Newsletter and Matter.)

"the codebases become Babel not because nobody can communicate, but because nobody needs to. Every developer has a tireless translator that can explain a corner of the tower."
Engineer RoleTask Design

Why AI hasn't replaced software engineers, and won't

normaltech.ai

Narayanan & Kapoor use a "decide-execute-deliver sandwich" model plus labor economics and forensic debunking of "AI-washed" layoffs to argue value migrates upward to irreducible decision-making.

"Once a decision can be delegated to AI, it is no longer a source of competitive advantage, and the value of human decision-making migrates upward."

You can't design software you don't work on

seangoedecke.com

useful software design is concrete (individual files and lines) and can't be done by detached architects; the line between translating generic advice and actually understanding a system.

"In practice, software architecture advice often has to be ignored by the people on the ground. There's simply no way to actually translate it into something they can implement."

What does "playing politics" mean for software engineers?

seangoedecke.com

reframes politics not as scheming but as reading how the organization actually operates: the tacit, undocumentable capability separating effective engineers from invisible ones.

"Senior managers live in an information-poor environment: for them to learn something about a team's work, that information has to bubble up through several layers of interpretation and summary."
Engineer Role

A Collection of Design Engineers

maggieappleton.com

Maggie Appleton's attempt to define the "design engineer": knowing the medium's constraints collapses the artifact/handoff chain so one person can hold design-to-implementation in their head.

"they are the ones downstream of the designs"

πŸ’° Value concentration when creation costs collapse

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

Leverage

The Pulse: What can we learn from Bun's rapid Rust rewrite with AI?

pragmaticengineer.com

Bun's 535K-line Zig-to-Rust rewrite done in 11 days with 64 parallel agents (git-stash collisions, 16K compiler errors, $165K in tokens): AI makes previously-impractical migrations feasible, changing the economics of what gets built.

"The realistic alternative was to do nothing and keep fixing the bugs at the top of this post forever."
Harness Design

How I Built a Custom AI Harness with the Claude Agent SDK for Bug Triage

How I AI Β· Lenny's Newsletter

Claire Vo's walkthrough of a real Sentry-to-Linear triage harness demystifies "harness" concretely (tool adapters, permissions-as-flags, structured artifact bundles) and argues owning the harness layer is the durable moat.

"A harness is just code around an AI agent. That's it."

When AI Costs More Than the Engineer

tomtunguz.com

treats the compute-to-payroll ratio as the new dominant cost of software engineering (Anthropic at 2.3x payroll), triangulating sources into three 2029 scenarios. Economics, not opinion.

"The cost structure follows the revenue structure."

Pseudpocalypse

dynomight.net

a first-principles, cross-domain argument (information theory + stylometry + demographics) that as de-anonymization costs collapse, privacy and pseudonymity become the scarce things, and VPNs and pen names won't save you.

"Effectively, this countermeasure would preserve pseudonymity by taking writing and destroying all traces of humanity."

Canva's Affinity Strategy: Normies Over Power Users

tedium.co

a teardown of value capture when creation costs collapse: Canva makes pro tools free, turning Affinity's power users into a loss leader to monetize the far larger pool of office "normies."

"Rather than feeling choked by its power users, it's turned those power users into a loss leader. Usually, it's the low-end users that are the loss leaders."

πŸͺ΅ Thick engagement vs. thin optimization

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

Learning in AI Era

Interview with Mitchell Hashimoto (Ghostty and Zig)

alexalejandre.com

an agenda-free retrospective on craft over scalability: the toolmaker's dilemma, building Ghostty for an audience of one, and why understanding computers matters more than any language.

"My goal was to run vim and the compiler in it, have it build itself, then throw it away."

πŸš€ Small teams, disproportionate output

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

LeverageScaling Yourself

Alex Finn's Local AI Fleet and Automated Software Factory

How I AI Β· Lenny's Newsletter

a solo builder's concrete architecture for a 24/7 local AI fleet (Mac Studio, DGX Spark, RTX 5090) routing cheap continuous local grunt-work to frontier models for judgment. Self-hosting, build/review loops, and small-team leverage at once.

"The case for local AI isn't ROI; it's unlimited inference."
Harness Design

Using Local Coding Agents

magazine.sebastianraschka.com

a hands-on build of a fully local coding-agent stack (Ollama + open-weight models on a Mac Mini / DGX Spark wired into Qwen-Code, Codex, Claude Code) with custom benchmarks and a non-obvious finding about where the token cost really goes.

"the token usage is largely driven by the harness, not the LLM itself"

Viability of local models for coding

martinfowler.com

Birgitta BΓΆckeler (Thoughtworks) structurally decomposes what actually gates local models for agentic coding (RAM, MoE architecture, quantization, tool-call schema mismatches) rather than hype.

"reasoning is not always necessary, and can sometimes even be counterproductive"

Staying on the path to high performing teams

lethain.com

Will Larson maps teams onto four states (falling behind, treading water, repaying debt, innovating), argues hiring is over-reached-for, and prescribes a distinct lever per state plus consolidating resources on one team at a time.

"Many folks try to move all teams at the same time, peanut buttering their limited resources, but resist that indecision-framed-as-fairness: no one getting anything is not a fair outcome."

Code Yellow, Code Red

theengineeringmanager.substack.com

a real Code Yellow at Provet becomes a study in how shared vocabulary and a reusable template (problem statement, exit criteria, "tap on the shoulder" authority) mobilize a whole org under pressure.

"If you're waiting for the dramatic failure, you've already waited too long."

🧬 Transmission of capability

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

Learning in AI Era

In defense of AI mandates

charity.wtf

Honeycomb's CTO reframes the reviled AI mandate not as coercion but as a funding mechanism that forces orgs to name tradeoffs and allocate real time for skill-building.

"The mandate is one way of putting organizational muscle behind a decision."

How do I deal with my team members who are resisting change?

andiroberts.com

recasts resistance as information, not a character flaw, with a six-profile readiness taxonomy and the "immunity to change" lens; invest in the persuadable middle, not the loudest deniers.

"Fairness, not enthusiasm, was the lever."

The Beginnings of an Idea: XP is Long Volatility

Kent Beck Β· Tidy First?

Kent Beck on how ideas ferment over years and, more sharply, on the mechanics of explanation: refining an idea by explaining it badly, repeatedly.

"The only way to learn how to explain something well is to explain it badly over & over."

πŸ‘€ On the radar

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

How this is made

Each week, Ben works through 28 newsletter emails from 12 publications, and the 25 pieces worth your time land here, distilled into about a 13-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.