Gergely Orosz on the Pragmatic Engineer, Newsletter Economics, and the Creator Life

Gergely Orosz on the Pragmatic Engineer, Newsletter Economics, and the Creator Life

transcriptnewslettercreatorwritingcareerlenny

Gergely Orosz on the Pragmatic Engineer, Newsletter Economics, and the Creator Life

Source: Lenny’s Podcast Speaker: Gergely Orosz Link: Episode

Overview

Gergely Orosz, author of the Pragmatic Engineer (the #1 technology newsletter on Substack at ~189K subscribers at time of recording), sits down with Lenny for a peer conversation between two full-time newsletter creators. The episode covers Gergely’s path from software engineer at Uber to newsletter writer, the economics of paid newsletters, the daily realities of the creator life (calendar freedom, loneliness, structural challenges, difficulty taking holidays), and practical advice for anyone considering going down this route. Both hosts treat the newsletter as a business, not a hobby.

Key ideas

  • The accidental path. Gergely left Uber during COVID layoffs to start a VC-backed startup in platform engineering. He used the six-month gap before fundraising to write a book, accidentally published a free mobile-engineering ebook (Building Mobile Apps at Scale) that made $100K in its first year, and pivoted to a paid newsletter instead of a startup — following the pull of demonstrated reader interest rather than a pre-set plan. By the time he launched the paid newsletter, he had six years of blogging at The Pragmatic Engineer already behind him.
  • Newsletter economics. At the time of the episode: 189K subscribers, ~1,000 new subscribers per day, thousands of paying members. Newsletter income already exceeds the ~$320–330K total compensation Gergely earned in his best year at Uber. Revenue is recurring and uncapped by employer grade structures but constrained by churn and growth rate. No exit path comparable to equity: the business is person-dependent and typically valued at ~4–5× annual revenue, but can’t be cleanly sold. PTO is limited — sustained non-production triggers churn.
  • The craft of weekly writing. Two posts per week (Tuesday in-depth + Thursday scoop). Each Tuesday post takes roughly a full week: research (including interviews), first draft, peer feedback, editor pass. The cadence is the discipline — external commitment to readers functions as the pressure that drives output. Gergely’s secret: articles double as raw material for a long-planned book (the Software Engineer’s Guidebook), inspired by Alexandre Dumas writing The Three Musketeers in magazine serialisation format.
  • Productivity under unstructured time. The biggest surprise: diligent corporate employees often become unfocused when working for themselves. Proven tactics: public deadlines (announcing the commitment before starting), a hosts-file script to block distracting sites during focused sessions, a 20-minute timer to get past the resistance before flow kicks in, and coworking spaces to address loneliness. “I fixed it by telling people you’re going to get this every week. Now I have to do it. I just have no choice.”
  • Getting started: years, not weeks. Jeff Atwood’s formula — write, do it three times a week, for two years — distilled to: build genuine domain depth first; start teaching and sharing in whatever format; maintain cadence; follow signals of pull (demonstrated reader interest) over pre-set plans. Background from real companies doing interesting things provides the credibility and material that makes expertise-based content valuable. Results are not reproducible without the accumulated background.