Powered by RND
PodcastsTechnologyThe Pragmatic Engineer
Listen to The Pragmatic Engineer in the App
Listen to The Pragmatic Engineer in the App
(7,438)(250,057)
Save favourites
Alarm
Sleep timer

The Pragmatic Engineer

Podcast The Pragmatic Engineer
Gergely Orosz
Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons,...

Available Episodes

5 of 20
  • How Linux is built with Greg Kroah-Hartman
    Supported by Our Partnersā€¢ WorkOS ā€” The modern identity platform for B2B SaaS.ā€¢ Vanta ā€” Automate compliance and simplify security with Vanta.ā€”Linux is the most widespread operating system, globally ā€“ but how is it built? Few people are better to answer this than Greg Kroah-Hartman: a Linux kernel maintainer for 25 years, and one of the 3 Linux Kernel Foundation Fellows (the other two are Linus Torvalds and Shuah Khan). Greg manages the Linux kernelā€™s stable releases, and is a maintainer of multiple kernel subsystems.We cover the inner workings of Linux kernel development, exploring everything from how changes get implemented to why its community-driven approach produces such reliable software. Greg shares insights about the kernel's unique trust model and makes a case for why engineers should contribute to open-source projects. We go into:ā€¢ How widespread is Linux?ā€¢ What is the Linux kernel responsible for ā€“ and why is it a monolith?ā€¢ How does a kernel change get merged? A walkthroughā€¢ The 9-week development cycle for the Linux kernelā€¢ Testing the Linux kernelā€¢ Why is Linux so widespread?ā€¢ The career benefits of open-source contributionā€¢ And much more!ā€”Timestamps(00:00) Intro(02:23) How widespread is Linux?(06:00) The difference in complexity in different devices powered by LinuxĀ (09:20) What is the Linux kernel?(14:00) Why trust is so important with the Linux kernel development(16:02) A walk-through of a kernel change(23:20) How Linux kernel development cycles work(29:55) The testing process at Kernel and Kernel CIĀ (31:55) A case for the open source development process(35:44) Linux kernel branches: Stable vs. development(38:32) Challenges of maintaining older Linux codeĀ (40:30) How Linux handles bug fixes(44:40) The range of work Linux kernel engineers doĀ (48:33) Gregā€™s review process and its parallels with Uberā€™s RFC process(51:48) Linux kernel within companies like IBM(53:52) Why Linux is so widespreadĀ (56:50) How Linux Kernel Institute runs without product managersĀ (1:02:01) The pros and cons of using Rust in Linux kernelĀ (1:09:55) How LLMs are utilized in bug fixes and coding in LinuxĀ (1:12:13) The value of contributing to the Linux kernel or any open-source projectĀ (1:16:40) Rapid fire roundā€”The Pragmatic Engineer deepdives relevant for this episode:ā€¢ ā€”See the transcript and other references from the episode at ā ā https://newsletter.pragmaticengineer.com/podcastā ā ā€”Production and marketing by ā ā ā ā ā ā ā ā https://penname.co/ā ā ā ā ā ā ā ā . For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    -------- Ā 
    1:21:19
  • Developer Experience at Uber with Gautam Korlam
    Supported by Our Partnersā€¢ Sentry ā€” Error and performance monitoring for developers.ā€¢ The Software Engineerā€™s Guidebook: Written by me (Gergely) ā€“ now out in audio form as well.ā€”In todayā€™s episode of The Pragmatic Engineer, I am joined by former Uber colleague, Gautam Korlam. Gautam is the Co-Founder of Gitar, an agentic AI startup that automates code maintenance. Gautam was mobile engineer no. 9 at Uber and founding engineer for the mobile platform team ā€“ and so he learned a few things about scaling up engineering teams.We talk about:ā€¢ How Gautam accidentally deleted Uberā€™s Java monorepo ā€“ really!ā€¢ Uber's unique engineering stack and why custom solutions like SubmitQueue were built in-houseā€¢ Monorepo: the benefits and downsides of this approachā€¢ From Engineer II to Principal Engineer at Uber: Gautamā€™s career trajectoryā€¢ Practical strategies for building trust and gaining social capitalĀ ā€¢ How the platform team at Uber operated with a product-focused mindsetā€¢ Vibe coding: why it helps with quick prototypingā€¢ How AI tools are changing developer experience and productivityā€¢ Important skills for devs to pick up to remain valuable as AI tools spreadā€¢ And more!ā€”Timestamps(00:00) Intro(02:11) How Gautam accidentally deleted Uberā€™s Java Monorepo(05:40) The impact of Gautamā€™s mistake(06:35) Uberā€™s unique engineering stack(10:15) Uberā€™s SubmitQueue(12:44) Why Uber moved to a monorepo(16:30) The downsides of a monorepo(18:35) Measurement products built in-houseĀ (20:20) Measuring developer productivity and happinessĀ (22:52) How Devpods improved developer productivityĀ (27:37) The challenges with cloud development environments(29:10) Gautamā€™s journey from Eng II to Principal Engineer(32:00) Building trust and gaining social capitalĀ (36:17) An explanation of Principal Engineer at Uberā€”and the archetypes at UberĀ (45:07) The platform and program split at Uber(48:15) How Gautam and his team supported their internal usersĀ (52:50) Gautamā€™s thoughts on developer productivityĀ (59:10) How AI enhances productivity, its limitations, and the rise of agentic AI(1:04:00) An explanation of Vibe coding(1:07:34) An overview of Gitar and all it can help developers withĀ (1:10:44) Top skills to cultivate to add value and stay relevant(1:17:00) Rapid fire roundā€”The Pragmatic Engineer deepdives relevant for this episode:ā€¢ The Platform and Program split at Uberā€¢ How Uber is measuring engineering productivityā€¢ Inside Uberā€™s move to the Cloudā€¢ How Uber built its observability platformā€¢ Software Architect Archetypesā€”See the transcript and other references from the episode at ā ā https://newsletter.pragmaticengineer.com/podcastā ā ā€”Production and marketing by ā ā ā ā ā ā ā ā https://penname.co/ā ā ā ā ā ā ā ā . For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    -------- Ā 
    1:20:35
  • Design-first software engineering: Craft ā€“ with Balint Orosz
    Supported by Our Partnersā€¢ WorkOS ā€” The modern identity platform for B2B SaaS.ā€¢ The Software Engineerā€™s Guidebook: Written by me (Gergely) ā€“ now out in audio form as wellā€¢ Augment Code ā€” AI coding assistant that pro engineering teams loveā€”Not many people know that I have a brother: Balint Orosz. Balint is also in tech, but in many ways, is the opposite of me. While I prefer working on backend and business logic, he always thrived in designing and building UIs. While I opted to work at more established companies, he struck out on his own and started his startup, Distinction. And yet, our professional paths have crossed several times: at one point in time I accepted an offer to join Skyscanner as a Principal iOS Engineer ā€“ and as part of the negotiation, I added a clause to my contrac that I will not report directly or indirectly to the Head of Mobile: who happened to be my brother, thanks to Skyscanner acquiring his startup the same month that Skyscanner made an offer to hire me.Today, Balint is the founder and CEO of Craft, a beloved text editor known for its user-friendly interface and sleek design ā€“ an app that Apple awarded the prestigious Mac App of the Year in 2021.In our conversation, we explore how Balint approaches building opinionated software with an intense focus on user experience. We discuss the lessons he learned from his time building Distinction and working at Skyscanner that have shaped his approach to Craft and its development.In this episode, we discuss:ā€¢ Balintā€™s first startup, Distinction, and his time working for Skyscanner after they acquired itā€¢ A case for a balanced engineering culture with both backend and frontend prioritiesĀ ā€¢ Why Balint doesnā€™t use iOS Auto Layoutā€¢ The impact of Craft being personal software on front-end and back-end developmentā€¢ The balance between customization and engineering fear in frontend workā€¢ The resurgence of local-first software and its role in modern computingā€¢ The value of building a physical prototypeĀ ā€¢ How Balint uses GenAI to assist with complicated coding projectsĀ ā€¢ And much more!ā€”Timestamps(00:00) Intro(02:13) What itā€™s like being a UX-focused founderĀ (09:00) Why it was hard to gain recognition at SkyscannerĀ (13:12) Takeaways from Skyscanner that Balint brought to CraftĀ (16:50) How frameworks work and why they arenā€™t always a good fit(20:35) An explanation of iOS Auto Layout and its pros and consĀ (23:13) Why Balint doesnā€™t use Auto LayoutĀ (24:23) Why Craft has one code baseĀ (27:46) Craftā€™s unique toolbar features and a behind the scenes peek at the codeĀ (33:15) Why frontend engineers have fear around customizationĀ (37:11) How Craftā€™s design system differs from most companiesĀ (42:33) Behaviors and elements Craft uses rather than having a system for everythingĀ (44:12) The back and frontend architecture in building personal softwareĀ (48:11) Shifting beliefs in personal computingĀ (50:15) The challenges faced with operating system updatesĀ (50:48) The resurgence of local-first software(52:31) The value of opinionated software for consumersĀ (55:30) Why Craftā€™s focus is on the userā€™s emotional experience(56:50) The size of Craftā€™s engineering department and platform teams(59:20) Why Craft moves faster with smaller teams(1:01:26) Balintā€™s advice for frontend engineers looking to demonstrate valueĀ (1:04:35) Balintā€™s breakthroughs using GenAI(1:07:50) Why Balint still writes code(1:09:44) Rapid fire roundā€”The Pragmatic Engineer deepdives relevant for this episode:ā€¢ The AI hackathon at Craft Docsā€¢ Engineering career paths at Big Tech and scaleupsā€¢ Thriving as a Founding Engineer: lessons from the trenchesā€¢ The past and future of modern backend practicesā€”See the transcript and other references from the episode at ā ā https://newsletter.pragmaticengineer.com/podcastā ā ā€”Production and marketing by ā ā ā ā ā ā ā ā https://penname.co/ā ā ā ā ā ā ā ā . For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    -------- Ā 
    1:12:37
  • The man behind the Big Tech comics ā€“ with Manu Cornet
    Supported by Our Partnersā€¢ WorkOS ā€” The modern identity platform for B2B SaaS.ā€¢ Graphite ā€” The AI developer productivity platform.Ā ā€¢ Formation ā€” Level up your career and compensation with Formation.ā€”In todayā€™s episode of The Pragmatic Engineer, I am joined by a senior software engineer and cartoonist, Manu Cornet. Manu spent over a decade at Google, doing both backend and frontend development. He also spent a year and a half at Twitter before Elon Musk purchased it and rebranded it to X. But what Manu is most known for are his hilarious internet comics about the tech world, including his famous org chart comic from 2011 about Facebook, Apple, Amazon, and Microsoft.In todayā€™s conversation, we explore many of his comics, discuss the meaning behind them, and talk about the following topics:Ā ā€¢ The viral org chart comic that captured the structure of Big Tech companiesā€¢ Why Google is notorious for confusing product namesā€¢ The comic that ended up on every door at Googleā€¢ How Googleā€™s 20% time fostered innovationā€”and what projects came from itā€¢ How one of Manuā€™s comics predicted Google Stadiaā€™s failureā€”and the reasons behind itā€¢ The value of connecting to users directlyĀ ā€¢ Twitterā€™s climate before and after Elon Muskā€™s acquisition and the mass layoffs that followedā€¢ And more!ā€”Timestamps(00:00) Intro(02:01) Manuā€™s org structure comicĀ (07:10) Manuā€™s ā€œWho Sues Whoā€ comic(09:15) Google vs. Amazon comic(14:10) Confusing names at Google(20:00) Different approaches to sharing information within companies(22:20) The two ways of doing things at Google(25:15) Manuā€™s code reviews comic(27:45) The comic that was printed on every single door of Google(30:55) An explanation of 20% at Google(36:00) Gmail Labs and Google Stadia(41:36) Manuā€™s time at Twitter and the threat of Elon Musk buying(47:07) How Manu helped Gergely with a bug on Twitter(49:05) Muskā€™s acquirement of Twitter and the resulting layoffs(59:00) Manuā€™s comic about his disillusionment with Twitter and Google(1:02:37) Rapid fire roundā€”The Pragmatic Engineer deepdives relevant for this episode:ā€¢ How Manu creates comicsā€¢ Consolidating technologiesā€¢ Is Big Tech becoming more cutthroat?ā€”See the transcript and other references from the episode at ā ā https://newsletter.pragmaticengineer.com/podcastā ā ā€”Production and marketing by ā ā ā ā ā ā ā ā https://penname.co/ā ā ā ā ā ā ā ā . For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    -------- Ā 
    1:07:49
  • Developer productivity with Dr. Nicole Forsgren (creator of DORA, co-creator of SPACE)
    Supported by Our Partnersā€¢ WorkOS ā€” The modern identity platform for B2B SaaSā€¢ CodeRabbit ā€” Cut code review time and bugs in halfā€¢ Augment Code ā€” AI coding assistant that pro engineering teams loveā€”How do you architect a live streaming system to deal with more load than itā€™s ever been done before? Today, we hear from an architect of such a system: Ashutosh Agrawal, formerly Chief Architect of JioCinema (and currently Staff Software Engineer at Google DeepMind.)We take a deep dive into video streaming architecture, tackling the complexities of live streaming at scale (at tens of millions of parallel streams) and the challenges engineers face in delivering seamless experiences. We talk about the following topics:Ā ā€¢ How large-scale live streaming architectures are designedā€¢ Tradeoffs in optimizing performanceā€¢ Early warning signs of streaming failures and how to detect themā€¢ Why capacity planning for streaming is SO difficultā€¢ The technical hurdles of streaming in APAC regionsā€¢ Why Ashutosh hates APMs (Application Performance Management systems)ā€¢ Ashutoshā€™s advice for those looking to improve their systems design expertiseā€¢ And much more!ā€”Timestamps(00:00) Intro(01:28) The world record-breaking live stream and how support works with live events(05:57) An overview of streaming architecture(21:48) The differences between internet streaming and traditional television.l(22:26) How adaptive bitrate streaming works(25:30) How throttling works on the mobile tower sideĀ (27:46) Leading indicators of streaming problems and the data visualization needed(31:03) How metrics are setĀ (33:38) Best practices for capacity planningĀ (35:50) Which resources are planned for in capacity planningĀ (37:10) How streaming services plan for future live events with vendors(41:01) APAC specific challenges(44:48) Horizontal scaling vs. vertical scalingĀ (46:10) Why auto-scaling doesnā€™t work(47:30) Concurrency: the golden metric to scale against(48:17) User journeys that cause problemsĀ (49:59) Recommendations for learning more about video streamingĀ (51:11) How Ashutosh learned on the job(55:21) Advice for engineers who would like to get better at systems(1:00:10) Rapid fire roundā€”The Pragmatic Engineer deepdives relevant for this episode:ā€¢ Software architect archetypes https://newsletter.pragmaticengineer.com/p/software-architect-archetypesĀ ā€¢ Engineering leadership skill set overlaps https://newsletter.pragmaticengineer.com/p/engineering-leadership-skillset-overlapsĀ ā€¢ Software architecture with Grady Booch https://newsletter.pragmaticengineer.com/p/software-architecture-with-grady-boochā€”See the transcript and other references from the episode at ā ā https://newsletter.pragmaticengineer.com/podcastā ā ā€”Production and marketing by ā ā ā ā ā ā ā ā https://penname.co/ā ā ā ā ā ā ā ā . For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
    -------- Ā 
    1:22:39

More Technology podcasts

About The Pragmatic Engineer

Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons, interesting stories and advice they have on building software. Especially relevant for software engineers and engineering leaders: useful for those working in tech. newsletter.pragmaticengineer.com
Podcast website

Listen to The Pragmatic Engineer, All-In with Chamath, Jason, Sacks & Friedberg and many other podcasts from around the world with the radio.net app

Get the free radio.net app

  • Stations and podcasts to bookmark
  • Stream via Wi-Fi or Bluetooth
  • Supports Carplay & Android Auto
  • Many other app features
Social
v7.11.0 | Ā© 2007-2025 radio.de GmbH
Generated: 3/24/2025 - 9:53:48 PM