Generated by Codex with GPT-5

The Pragmatic Engineer surfaced this May 20, 2026 podcast episode, and the original episode page is Why Rust is different, with Alice Ryhl.

Rust makes correctness part of the workflow

The episode is a useful explanation of Rust because Alice Ryhl does not frame the language as a prestige choice or a benchmark contest. She explains it as a language that changes where engineering effort goes. Rust asks developers to make ownership, lifetimes, error handling, and unsafe boundaries explicit earlier than many other languages do. That can make the first draft slower and the learning curve steeper, but it also moves classes of mistakes out of runtime debugging and into compiler feedback.

Generated by Codex with GPT-5

The Pragmatic Engineer surfaced this May 19, 2026 article, and the original post is AI’s impact on software engineers in 2026: key trends, Part 2.

The productivity story is getting messier

Gergely Orosz’s latest survey analysis is interesting because it treats AI coding tools less like a single productivity lever and more like an organizational stress test. The piece draws on more than 900 responses from The Pragmatic Engineer subscribers and closes a series on how software engineers are actually using AI tools in 2026.

Generated by Codex with GPT-5

The Pragmatic Engineer surfaced this May 12, 2026 essay: Revisiting “No Silver Bullets” in the age of AI.

The old question returns

Gergely Orosz uses Frederick Brooks’s 1986 essay “No Silver Bullet” as a way to test the AI coding moment against a harder standard than demo output. Brooks argued that no single technology or management technique would create a tenfold improvement in software productivity, reliability, or simplicity, because the hardest parts of software are bound up with complexity, judgment, coordination, and changing requirements.

Generated by Codex with GPT-5

The Pragmatic Engineer surfaced this piece: The Pulse: AI load breaks GitHub - why not other vendors?, published May 7, 2026.

GitHub’s AI Load Problem

Gergely Orosz frames GitHub’s recent reliability problems as more than another stretch of SaaS downtime. The article argues that GitHub is being tested by the new shape of software work: AI agents do not just write code, they generate pull requests, trigger checks, hit APIs, update workflows, fan out notifications, and exercise every old assumption inside a developer platform.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this April 30, 2026 post, and the original is The Pulse: token spend breaks budgets - what next?.

Gergely Orosz reports that AI coding agents have moved from a discretionary experiment to a fast-growing operating expense. After speaking with engineers and leaders at 15 companies, he found a common pattern: token spend has surged over the past few months, often far faster than budgets, finance processes, or internal measurement systems expected.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this April 29, 2026 piece, and the original post is Building Pi, and what makes self-modifying software so fascinating.

Gergely Orosz’s podcast episode with Mario Zechner and Armin Ronacher is less a product pitch than a critique of the current agent boom. Pi is presented as a minimalist, self-modifying coding agent built in reaction to Claude Code becoming harder to predict as features piled up. Zechner’s core idea is that AI harnesses should stay small, stable, and adaptable enough to be specialized for particular jobs, instead of trying to become giant assistants that do everything at once.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this April 28, 2026 piece, and the original post is How will AI change operating systems? Part 1: Ubuntu and Linux.

Gergely Orosz uses reporting from Canonical VP of Engineering Jon Seager to ask a more interesting question than which coding model is best this week: what does AI change at the operating-system layer? The article’s answer is that Linux distributions do not need to become chatbots. They need to become better substrates for a world full of AI accelerators, local inference, agentic tooling, and much messier hardware diversity.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this April 14, 2026 piece, and the original post is The impact of AI on software engineers in 2026: key trends.

Gergely Orosz and Elin Nilsson use more than 900 survey responses from engineers and engineering leaders to describe how AI coding tools are changing daily software work in practice. The article is less interested in which model won last week and more interested in what happens once these tools become routine: who pays for them, who runs into limits, who benefits most, and what kinds of tradeoffs teams are quietly accepting.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this April 8, 2026 piece, and the original post is DHH’s new way of writing code.

Gergely Orosz interviews David Heinemeier Hansson about a notable reversal. Six months ago, DHH said he did not want AI writing his code. Now he describes an agent-first workflow built around terminals, tmux, Neovim, and multiple models running in parallel. His argument is not that the principles of software craft changed. It is that the tools improved enough to make delegation worthwhile. Autocomplete used to feel annoying and low-value; newer agents can now produce code that he is comfortable reviewing and sometimes merging with minimal changes.

Generated by Codex with GPT-5

What happened

The Pragmatic Engineer surfaced this piece in its April 7, 2026 issue, and the original post is Cycles of disruption in the tech industry: with software pioneers Kent Beck & Martin Fowler.

Gergely Orosz summarizes a live conversation with Kent Beck and Martin Fowler about how AI compares with earlier technology shifts like the internet, object-oriented programming, and Agile. Their broad argument is that AI feels bigger, faster, and messier than those earlier transitions, and that it is already changing how software teams work, how companies measure performance, and what good engineering discipline looks like.