“who was on the podcast who's the author of pragmatic engineer”
The Pragmatic Engineer
By Gergely Orosz
1 recommend/use · 2 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“your newsletter is the number one technology newsletter on sub stack called the pragmatic engineer”
“if you work in Tech consider signing up to my my newsletter”
Related frameworks
Clarity and Conviction: Insights, Strategy, Big Rocks
The whole craft of PM in two words, expressed as a two-page narrative every team can recite.
Controllable Goals
Set goals inside your control (inputs), not outcomes you can't guarantee
Double Down on the Pull
When something you made gets unexpected traction, drop the plan and lean all-in
Earn the Right to Teach
Build real depth and pedigree first — then your writing has something worth reading
Empathize–Create–Evangelize
The three-stage loop for developing a product vision: understand deeply, imagine the solved world, then sell it.
Manufactured Deadlines
Impose external constraints so solo creative work actually ships
The 20-Minute Focus Ignition
Beat the hardest part of deep work — starting — by force-blocking distractions for 20 minutes
The Four Tests of a Compelling Product Vision
A vision must be lofty, realistic, free of today's constraints, and anchored to a potent problem.
The Future Headline
Write the tech-press headline your launch would earn, mocked into the real publication's page.
The Human Behind the Role
Optimise for being loved, not liked — earn the right to give raw feedback by proving you care first.
The Marquee Mock Exercise
Hand everyone blank App Store screenshot panels and make them draw the world where the problems are solved.
The Once Upon a Time Vision Story
A five-blank Mad Libs template that turns a product vision into a story anyone can retell.
The Three Concentric Circles of Evangelism
Socialise a vision outward: core team, then stakeholders, then leadership as high as you can reach.
The Time-Boxed Leap Bet
De-risk a scary career leap by treating it as a fixed-length experiment with a fallback
The Two-Year Publishing Cadence
Write a post several times a week for two years and an audience will find you
Top 10 Things You Should Know
A living, stack-ranked problem doc every PM owns — and every stakeholder must fill in too.
People in these episodes
Related resources
- Airbnb
- Amazon
- Amsterdam
- Atlassian
- Burning Man
- Cameo
- Center
- ChatGPT
- Contentful
- DJay Pro AI
- Eppo
- Goodreads
- Google Bard
- Google Play Store
- Hacker News
- IKEA
- Invictus
- Jira Product Discovery
- JPMorgan
- Lemon.io
- Lenny's Podcast
- lennyspodcast.com
- Microsoft
- Netflix
- Netlify
- Outliers
- pragmaticengineer.com
- Scavengers Reign
- Sidebar
- Skype
- Skyscanner
- Sleep Cycle
- SOC 2
- Spotify
- Stack Overflow
- Stripe
- Substack
- TechCrunch
- TED
- Tesla
- The 48 Laws of Power
- The Bear
- The God of Small Things
- The Last of Us
- The New York Times
- The Verge
- The White Lotus
- Uber
- Uber Pool
- Vanta
- Wix Studio
- YouTube
Spot an error or want this page removed? Request a correction or removal.