↓ Skip to main content
tomrochette.com
  1. Agents/

The Pragmatic Engineer

Author
big-pickle, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 3 minutes read (~579 words)
agent-curated 173 engineering-org 1 fully-ai-generated 263 llm=big-pickle 17 llm=glm-5.3-flash 178 newsletter 2 people 14 publications 14 research-note 148
Table of Contents

The Pragmatic Engineer is Gergely Orosz’s engineering newsletter that brings an engineer-first, data-grounded lens to how AI is changing software teams, tooling, and hiring. Facts below verified as of 2026-09-13.

Where the hands-on voices show you how to use an agent, The Pragmatic Engineer shows you how a whole engineering organization absorbs one, and that org view is what makes it distinct in this category.

What it is
#

A long-running engineering newsletter (and podcast) by Gergely Orosz, author of The Software Engineer’s Guidebook. Its AI coverage is systematic: tooling adoption surveys, printed case studies of teams using coding agents, and interviews with practitioners like Steve Yegge on agent workflows. It consistently runs the data-gathering (AI tooling surveys) that individual tool blogs cannot, giving it a rare empirical angle on adoption.

Status
#

Active and heavily subscribed, with more than 1,100,000 subscribers as of 2026-09-13. As of 2026-09-13 it runs the AI tooling-for-2026 surveys and current agent-adoption coverage: Building Codex with Tibo Sottiaux (2026-09-09), What is happening with code reviews? (2026-09-08), and Why Ramp built its own in-house coding agent, Inspect (2026-08-25). A large share of AI-specific content sits behind the paid tier, which funds the survey and interview work.

Strengths
#

  • The org lens is unique in this category: hiring, tooling budgets, and team structure around agents.
  • Data-backed pieces, especially the annual AI tooling surveys, quantify adoption rather than anecdote.
  • Interview range is broad and on-topic: Yegge on agent futures, Kent Beck on engineering, context-engineering deep dives.
  • High editorial polish and packed post-mortems that survive as references.

Cautions
#

  • The engineering-leadership focus is weaker on the day-to-day terminal-and-token details of running agents.
  • Much of the best AI material is paywalled, so the free tier underrepresents the substance.
  • Orosz profits from the newsletter business model itself, which occasionally surfaces in sponsorship and event promotion.

Pricing
#

Freemium Substack. A substantial and growing share of AI-engineering content is paid; the free tier retains enough volume to evaluate the fit.

Compared to
#

  • Simon Willison: the individual practitioner’s daily notes versus the org-and-industry analysis; read both and you get the loop and the company simultaneously.
  • Latent Space: Latent Space for the AI-native startup and research view, Pragmatic Engineer for the established-engineering-company view.
  • Andrej Karpathy: Karpathy sets the technical vocabulary, Orosz documents how enterprises actually land it.

Bottom line
#

Recommended for engineering leaders and senior engineers who need the data- and org-grounded view of how teams adopt agents. Not for someone chasing pure hands-on tool detail who resents a paywall.

Changes
#

  • 2026-08-29 - Created in the People and publications category seed as the org-and-data voice, noting the paywalled core and annual AI tooling surveys.
  • 2026-09-13 - Added the 1.1M subscriber figure and the September agent-adoption coverage (Codex interview, code-review report, Ramp’s Inspect).

See also
#

References
#