English-language podcasts

The Pragmatic Engineer

Scaling Slack and GitHub with Maude Lemaire

79 min

Listen through the publisher, then discuss the episode here or arrange an in-person Roundtable. Your city determines where to meet.

Roundtables are designed for groups of four, with a shared subject and room for everyone to speak. Come for discussion, with no dating expectation.

Brought to You By: • Antithesis (https://antithesis.com/pragmatic) – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • turbopuffer (https://turbopuffer.com/pragmatic) – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Entire (http://entire.io/pragmatic) – The Git forge for agent-human collaboration. Built for the scale and throughput of agentic coding. — What is involved in scaling up large, popular products at places like Slack and GitHub? We get an insider’s view on this from Maude Lemaire (https://www.linkedin.com/in/lemairemaude), a principal engineer and author of‘ (https://www.oreilly.com/library/view/refactoring-at-scale/9781492075523/)Refactoring at Scale: Regaining Control of Your Codebase (https://www.oreilly.com/library/view/refactoring-at-scale/9781492075523/).’ She spent nearly eight years at Slack, where she led the backend performance infrastructure team, before joining GitHub to tackle database scaling challenges. Most recently, she worked on improving performance at Cursor – including time to first token. In this episode of The Pragmatic Engineer, Maude and I dig into the challenges of scaling some of the world's largest software products. We explore how Slack handled growing numbers of enterprise customers, how it evolved its approach to load testing, and the lessons Maude learned during nearly eight years of scaling Slack's infrastructure. She also tells us what it was like joining GitHub in 2024 when Copilot was taking off, the challenges of working with GitHub's gigantic Rails monolith, and how Maude uses AI in her work – while keeping judgment calls and decision-making firmly in her own hands. Timestamps 00:00 Intro 03:15 Early years and path to software engineering 07:32 First job at Rent the Runway 09:17 The HipChat data leak 10:54 Joining Slack and the challenges of scaling 26:30 Load testing and thundering herds 32:29 Event floods 38:30 Evolving load testing at Slack 48:38 Joining GitHub in 2024 56:52 The challenges of the Rails monolith 1:02:26 How Maude uses AI 1:12:40 Advice for engineers interested in product/platform work — The Pragmatic Engineer deepdives relevant for this episode: • Real-world engineering challenges: building Cursor (https://newsletter.pragmaticengineer.com/p/cursor) • Pushing software engineering limits with “napkin math” (https://newsletter.pragmaticengineer.com/p/pushing-software-engineering-limits) • What is happening with code reviews? (https://newsletter.pragmaticengineer.com/p/what-is-happening-with-code-reviews) • Why reliability is hard at scale: learnings from infrastructure outages (https://newsletter.pragmaticengineer.com/p/why-reliability-is-hard-at-scale) • What is Reliability Engineering? (https://newsletter.pragmaticengineer.com/p/reliability-engineering) • Migrations Done Well (https://newsletter.pragmaticengineer.com/p/migrations) • Shipping to Production (https://newsletter.pragmaticengineer.com/p/shipping-to-production) • The Platform and Program Split at Uber (https://newsletter.pragmaticengineer.com/p/program-platform-split-uber) • The present, past and future of GitHub (https://newsletter.pragmaticengineer.com/p/github) • Why performant code matters (but gets widely ignored), with Casey Muratori (https://newsletter.pragmaticengineer.com/p/why-performant-code-matters-but-gets) • Designing Data-intensive Applications with Martin Kleppmann (https://newsletter.pragmaticengineer.com/p/designing-data-intensive-applications) — Production and marketing by https://penname.co/https://penname.co/ (https://newsletter.pragmaticengineer.com/p/engineers-leading-projects). For inquiries about sponsoring the podcast, email [email protected]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe (https://newsletter.pragmaticengineer.com/subscribe)

Episode information is provided by the publisher. Listening takes place on the publisher’s service.

Listen at the source ↗

Featured places to meet in Palo Alto, CA

Explore these places and arrange a conversation through ThinkMatch.

City guide for Palo Alto, CA

More from The Pragmatic Engineer

The Pragmatic Engineer

Software engineering after code becomes cheap with Satya Nadella

63 min

Brought to You By: • turbopuffer (https://turbopuffer.com/pragmatic) – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Linear (https://linear.app/pragmatic) – the product development system for teams and agents. • WorkOS (https://workos.com/) – everything you need to make your app enterprise ready. — What does software engineering look like when generating code becomes cheap, and verifying it becomes the hard part? Today’s guest is Satya Nadella, Microsoft’s CEO, who is one of the very few Big Tech CEOs who started his career as a software engineer (back at Sun Microsystems). He joins me to discuss how building software is changing inside Microsoft, and what these changes mean for engineers. We start with Microsoft’s embrace of open source and the lessons from building VS Code in the open. I also ask how Microsoft went from an early lead with GitHub Copilot to catching up with Cursor and Claude Code, and what this reveals about

Discuss this episode

Community Poll

Universities should protect controversial speech unless it directly threatens or harasses others.

Share your view, then see how readers voted. No sign-in required. This poll is shared across stories.

Do you agree or disagree?

Choose one answer

Common Quandary

A Common Quandary to discuss

Another conversation to explore, separate from this news story.

The best garden plot has been abandoned for months. Who gets to take it?

Garden plots have a three-year waiting list. One member's plot has gone untended for months and messages go unanswered, but other gardeners know they recently faced serious health problems.

How long should a shared resource remain reserved out of compassion?

Explore this quandary