I quit the best job I ever had to try and build what I wish existed in the world. Two projects I'm working on now:
1. The Peterman Pod - When I first started at Meta, the career stories of incredible engineers always inspired me. I aim to share transparent career stories that I wish I had more of back in the day.
There are still many engineers who are heros to me that I'd love to bring on the show one day!
2. Compose - I could never really find what I wanted so I'm building the ergonomic keyboard I wish existed. Pictures of our prototype here: https://t.co/ZuF93hAteo
I've earmarked ~6 months of living expenses to fund this new career direction. I'm going to give it my all to see if it's sustainable.
Thank you for your support, working on my passion projects is something I’m only lucky enough to consider because of you all 🙏
More detail here: https://t.co/CuBuwZev0a
Turing Award winner Barbara Liskov on the downsides of Python
Barbara Liskov (Turing Award Winner): Python has modules, but it doesn't have encapsulation, so it allows code on the outside to muck around with what's going on inside a module. That's all I was talking about. Encapsulation is a crucial part of making modularity work.
When you're building big programs with many programmers working on them, your team is really only as strong as your weakest programmer. It's nice if the compiler can enforce things and make certain kinds of bad behavior not possible.
Barbara Liskov is a Turing award winner famous for her contributions to programming languages and distributed systems. I interviewed her recently about:
• Being rejected from college based on gender
• The software crisis of the 1970s
• Paxos vs Viewstamped replication (her invention) and why one is more well known
• Stories of Dijkstra and how his work influenced hers
• Why her Turing award was questioned
Where to watch:
• Youtube - https://t.co/1D4fgSym22
• Spotify - https://t.co/91fDmuPrtr
• Apple Podcasts - https://t.co/DM7faEiAxX
• Transcript - https://t.co/NjEMywF8W8
Brian Kernighan on writing one program in 24 different programming languages:
Brian Kernighan (Bell Labs MTS): I used to, in my class, I haven't done this for a long time, but I used to basically write the same program in as many languages as I could find. It was a simple program.
You would take text input lines of arbitrary lengths and put 'em out so that the lines were all at most 60 characters or something. So it was a simple-minded version of the reflow that you would see in a browser. And I would write it in every language I could lay my hands on.
I had 2 dozen or more of them and I'd show 'em in class. And the question was which ones ran faster and which ones were in some sense small or easy to understand or whatever. And awk was pretty fast, and it was the smallest always.
It was about 15 lines of code to do this job. And C was always the fastest, but it was harder because you had to worry about memory management a bit, and it was clunky to do strings. Yeah.
And the other scripting languages like Perl and Python and PHP, on the other hand, they were variously sort of okay. Perl was always the faster one. And some of the high-powered languages that were supposed to be better were actually slower.
Java was slower than the scripting languages. Kind of weird. C++ wasn't as fast as I thought it would be.
Brian Kernighan is a former Bell Labs member of technical staff, co-author of the original C book, and the one who popularized “Hello World.” We talked about what Bell Labs was like and the stories behind all the famous tools that were built there.
In this episode:
• Bell Labs culture and how he got hired
• Day in the life at Bell Labs and the best engineer
• Unix, C, and how awk got created
• His favorite languages and advice for students
Where to watch:
• YouTube - https://t.co/daXREKrTib
• Spotify - https://t.co/QCIwq7jcUw
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/u7ZY6qLLMS
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
00:42 What Bell Labs was and how he got hired
06:34 Why so many inventions came from Bell Labs
14:15 A day in the life at Bell Labs
27:55 The most impressive people he worked with
33:50 The AT&T film explaining Unix
39:46 Why C was so influential
43:25 How awk was created
48:40 What he misses most about Bell Labs
54:10 Are LLMs bad for computer science education
01:01:46 His 1972 commit in the Go repo
01:03:43 Grace Emlen, the fake Bell Labs employee
01:07:39 Why he writes so many books
01:19:58 His favorite and least favorite languages
01:24:28 Advice for students and young people
01:27:42 Outro
Microsoft Distinguished eng on why he doesn't read the code and what he does instead
Stephen Toub (Microsoft Distinguished Eng): I did not read every line. That would be impossible. And if I did, it would also be a waste.
There's no, me reading every line would not prevent bugs. In fact, agents reading every line is a lot more effective, not just faster, but more effective in quality than me doing so.
I absolutely looked at the code for every PR that I put up, but I was focusing more on big picture stuff, right? Is the direction of this correct? Is the architecture of this correct?
Or is the componentization of this correct? Is the approach, are the algorithms that are being used appropriate? Is there anything fishy about, if I, a lot of it is squinting at a 30,000-foot level and looking at the two codebases and does anything look off, right?
And then relying on the agents to focus on the line-by-line details. And in many situations, I would sort of do a quick scroll through all the changes to just see if anything popped out.
And I might notice a few things here and there, but for the most part, a really good agentic reviewer is going to be way better at sort of the line-level details than certainly me, and I would argue most humans.
In the year 2000, Joel Spolsky (founder of Stack Overflow) wrote a famous article titled “Things You Should Never Do, Part I.” In it, he talks about how rewriting your code from scratch is the single worst strategic mistake any software company can make. However, times have changed.
The cost of writing software is dropping exponentially and that has changed the math entirely on if it is worth rewriting your codebase. For instance, this year Anthropic’s Jarred Sumner ( @jarredsumner ) rewrote Bun in Rust in 11 days leading to many performance and correctness benefits.
Likewise, Stephen Toub (Distinguished Engineer at Microsoft, @stephentoub ) rewrote the GitHub Copilot runtime (400,000-line codebase) in Rust by himself. I thought it’d be interesting to lay out everything he learned in the process. So I interviewed him about how and why he did it.
In this episode:
• Why he choose Rust of all languages
• Rollout strategies (incremental vs all at once)
• How he prevented regressions
• Steering agents and which models he used
• Career lessons and engineering advice
Where to watch:
• YouTube - https://t.co/9Yj6kBj0ix
• Spotify - https://t.co/wa3my5QeBb
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/rI3rkhxsgG
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
01:06 Why the Copilot runtime needed a Rust port
05:38 Why he chose Rust
11:28 Discussing rollout strategies
21:57 How he caught regressions
32:08 Guiding the agents
42:11 Catching regressions before prod
45:16 Which models he used
50:03 The end benefit and costs
01:03:24 When to do a full rewrite
01:06:40 Career learnings on the way to Distinguished
01:16:00 Top technical book recommendation
01:17:49 Advice for young engineers
01:21:00 Outro
Brian Kernighan (Bell Labs) on the best engineer he ever worked with:
Brian Kernighan (Bell Labs MTS): Ken Thompson's the obvious one, I think. Certainly the best programmer I've ever met, unparalleled. And the story is the first version of Unix where he's got this little old PDP-7, which is an obsolete machine, has something like 8K 18-bit words.
So it's a tiny little machine. He's been fooling around with something to drive the disk on it. And he's thinking about how do you schedule disk operations so that it'll go fast and stuff like that?
And his wife takes their young son off to California for 3 weeks, and he thinks, I could do something here. And so in 3 weeks he builds himself an editor, an assembler, and an operating system. And there you have it.
Ryan: By himself?
Brian: Yeah. Oh yeah, absolutely.
Brian Kernighan is a former Bell Labs member of technical staff, co-author of the original C book, and the one who popularized “Hello World.” We talked about what Bell Labs was like and the stories behind all the famous tools that were built there.
In this episode:
• Bell Labs culture and how he got hired
• Day in the life at Bell Labs and the best engineer
• Unix, C, and how awk got created
• His favorite languages and advice for students
Where to watch:
• YouTube - https://t.co/daXREKrTib
• Spotify - https://t.co/QCIwq7jcUw
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/u7ZY6qLLMS
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
00:42 What Bell Labs was and how he got hired
06:34 Why so many inventions came from Bell Labs
14:15 A day in the life at Bell Labs
27:55 The most impressive people he worked with
33:50 The AT&T film explaining Unix
39:46 Why C was so influential
43:25 How awk was created
48:40 What he misses most about Bell Labs
54:10 Are LLMs bad for computer science education
01:01:46 His 1972 commit in the Go repo
01:03:43 Grace Emlen, the fake Bell Labs employee
01:07:39 Why he writes so many books
01:19:58 His favorite and least favorite languages
01:24:28 Advice for students and young people
01:27:42 Outro
In 1984, two first-time chip designers, Steve Furber and Sophie Wilson, created what would become the most popular processor in the world (ARM). I interviewed Steve about how they did it with such a small team that had no formal training.
We also covered a bunch of questions about hardware design and his answers were so clear. I learned a lot and hope you enjoy the episode!
Chapters:
00:00 Intro
00:27 Building his first computer
05:28 BBC Micro
10:28 Designing the ARM processor
17:15 Why their design was better
23:38 Emulators and interpreters
25:58 Instruction sets and microarchitecture
31:08 How they learned chip design
34:27 Why they were so successful
39:57 America vs UK
42:40 Why Acorn failed
44:10 Neuromorphic computing
48:52 Winning an IMO medal
50:45 His most proud engineering
51:46 Top technical book recommendation
52:29 Advice for young people
54:42 Outro
Where to watch:
• YouTube - https://t.co/b8XCwUEfNq
• Spotify - https://t.co/RBFf80j8rg
• Apple Podcasts - https://t.co/jOYDGtHtd1
• Transcript - https://t.co/Pe08oLTbxn
Thank you to the sponsors of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzGc3U
• Chargebee: billing and monetization infrastructure for the AI economy, so your pricing can evolve alongside your product, check them out at https://t.co/LALK1U6vX5
Why C++ is faster than C on average, according to its creator
Ryan: That was what I was going to ask you. You had said somewhere that C can be more performant than C++, but I tend to think that more abstraction costs you something.
Bjarne Stroustrup (Creator of C++): It's compiled away. This is why I talk about zero overhead abstraction, and people are beginning to take me to task for that because that's understating the ability of the C++ compiler. We can do negative overhead abstraction.
Ryan: What if I was really good at writing assembly and I had all the time in the world to write it? How does that compare?
Bjarne: If you are very smart and you have infinite time, you can do better. By and large, we are not as smart as the optimizers anymore, and we don't have infinite time.
Bjarne Stroustrup is the creator of C++ and a former researcher at Bell Labs at its peak. I interviewed him about:
• What made Bell Labs different
• Programming language design: types, memory safety, bootstrapping
• When abstraction improves performance
• Anecdotes from building C++
• Thoughts on AI writing C++
• Mistakes he'd change while building C++
Where to watch:
• YouTube: https://t.co/THHTMP9VoT
• Spotify: https://t.co/5kVNWCYEAI
• Apple Podcasts: https://t.co/jOYDGtHtd1
• Transcript: https://t.co/5jmJQWVtWp
Thank you to this episode's sponsors for supporting my work:
• Cursor 3: a unified workspace for building software with agents, check it out at https://t.co/PgHyLKgrxW
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzGc3U
Timestamps:
0:00 - Intro
0:50 - The origin of C++
8:46 - What Bell Labs was like
17:24 - Dennis Ritchie
24:00 - When to build a programming language
31:59 - Bootstrapping a language
33:58 - C++ is not object-oriented
37:32 - Discussing type systems
46:20 - Memory safety
49:26 - Standards committee anecdotes
1:09:40 - Adding automatic garbage collection to C++
1:18:25 - Template instantiation is Turing complete
1:21:57 - Abstraction and performance
1:28:51 - AI writing code
1:35:54 - His motivation
1:39:18 - Famous quotes
1:46:48 - Reflecting on building C++
1:49:12 - Top C++ book recommendation
1:50:59 - Advice for his younger self
1:58:06 - Outro
Marc Brooker's (AWS Distinguished Engineer) top technical book recommendations
Ryan: Do you have any top technical book recommendations?
Marc Brooker (AWS Distinguished Engineer): Anybody who's building distributed systems, I highly recommend Martin Kleppman's book. I think there's a second edition of that coming out soon. There's a new edition of the Quantitative Systems Design book, which I also think is great.
Hennessy and Patterson's Computer Architecture book is a super useful one that covers a ton of ground. I read a ton of fiction and nonfiction and mostly papers when I'm reading technical things. I find engaging at that level more useful for me.
And by the way, that's become way more accessible now. One of the great ways to dive into a paper is, hey, Claude, summarize this for me, and then I can dive into it and read the author's words.
I find that mode is great and it's super accessible for people who haven't been able to read papers in the past.
Marc Brooker ( @MarcJBrooker ) is a Distinguished Eng at AWS who has been building distributed systems there for almost 2 decades. I interviewed him about technical learnings from his experience. We discussed:
• Learnings from 3000+ post mortems
• When caching is a bad idea
• How software engineering is changing
• Visibility and apparent expertise
• How to find the best problems
Where to watch:
• YouTube: https://t.co/kmBAAiMbos
• Spotify: https://t.co/U5AhiGZX58
• Apple Podcasts: https://t.co/jOYDGtHtd1
• Transcript: https://t.co/dc6aoO1RLE
Turing Award winner Barbara Liskov on why Dijkstra's "Go To Statement Considered Harmful" was so controversial
Ryan: Why was it controversial at the time?
Barbara Liskov (Turing Award Winner): The programming languages were different then. First of all, there were people writing programs in assembler. In assembler, you have to use GOTOs.
Programming languages didn't have some of the constructs in them that we think of today. Some people were using GOTOs because they had to. Compilers didn't do all the kinds of optimizations that they do today.
There was a concern that if you didn't have GOTOs, maybe your program wouldn't be efficient enough. And then there were people who used GOTOs and wrote really good code. They were offended that Dijkstra was saying their code was bad.
So there was a whole bunch of controversy. Dijkstra was not the most diplomatic person, so he didn't write it nicely. You can imagine writing that paper in a more considerate way.
But there were many reasons why it was controversial. People were offended, but there were also concerns that programming languages didn't have these features. I need to know what I am supposed to do.
There were concerns about what the compiler was doing. The world is very different now, but clearly Dijkstra won the day because there are no go tos.
Barbara Liskov is a Turing award winner famous for her contributions to programming languages and distributed systems. I interviewed her recently about:
• Being rejected from college based on gender
• The software crisis of the 1970s
• Paxos vs Viewstamped replication (her invention) and why one is more well known
• Stories of Dijkstra and how his work influenced hers
• Why her Turing award was questioned
Where to watch:
• Youtube - https://t.co/1D4fgSym22
• Spotify - https://t.co/91fDmuPrtr
• Apple Podcasts - https://t.co/DM7faEiAxX
• Transcript - https://t.co/NjEMywF8W8
The creator of DNS on why URLs are ordered the way they are
Ryan: Why is it that URL goes from most specific to least specific? So I'm talking about if you go to, I don't know, maps. google.
com, the biggest one, Google's the more specific, Maps is the most specific. And then after that there's the path, which is also like a file directory. So it gets more and more specific as you go.
Why is it inverted like that?
Paul Mockapetris (Creator of DNS): You say inverted, I say it's an obvious choice. Think about this, okay? When you're typing in a URL, if I type maps, it can probably guess the google.
com. If I type in. com, is it going to address Google Maps?
No. So the point is that what you want to do is to put in the part. So if the machine is going to complete it, it has a chance, right?
Obviously, start with. com. You go, okay, well that narrows it down to 260 million different names, right?
Whereas if what you do is you type, oh, I don't know, you happen to have a machine called Alice, it may be able to say, oh, okay, I'll look what's around locally. And so that's why the order is the way it is. And I make no apologies.
And there's a lot of people that think I was wrong.
This interview is with Paul Mockapetris, the creator of the internet's Domain Name System (DNS). I talked to him about the story behind building it and certain design choices he made.
In this episode:
• Computing and the internet before DNS existed
• Why URLs use reversed names
• How DNS works
• Migrating the internet to DNS
• Advice for his younger self
Where to watch:
• YouTube - https://t.co/edubbKlHQY
• Spotify - https://t.co/W2UKqfD5DU
• Apple Podcasts - https://t.co/jOYDGtHtd1
• Transcript - https://t.co/mdug6tA7RS
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzGc3U
Chapters:
00:00 Intro
00:40 What computing was like before DNS
09:02 Why URLs are inverted
16:33 How DNS works
20:27 How he migrated the internet to DNS
25:17 Why do companies host DNS servers
33:17 What is an RFC
35:07 How he got into computing
46:39 Advice for his younger self
52:56 Outro
Stephen Toub (Microsoft Distinguished eng) on his top technical book recommendation
Ryan: Do you have any top book recommendation that maybe impacted you?
Stephen Toub (Microsoft Distinguished Eng): Yeah, I mean, it's old at this point, but I've read it several times and I absolutely love it. There's a book by Charles Petzold called Code. It's probably from what, 2003 maybe?
I don't know, something in that timeframe, but I love it. And it is one of the things that I really value is being able to explain complicated concepts in a way that doesn't require the person to know anything about what you're talking about.
I think that is a valuable skill, even if you're talking to people that do know what you're talking about, because being able to break down complicated concepts into very clear, concise pieces and communicate that clearly, and then at a 30,000-foot level, is a great way of getting everyone onto the same page and sort of arguing your case and pushing things in a direction that you want them to go.
And Code is a book where Charles basically does that, where he talks about how computers work from the ground up, teaching people that know nothing about computers, that aren't technically experienced, about binary, about logic gates, about circuits, about programming, about computers, about the Internet, and kind of building things up from basic principles, from nothing to a reasonable understanding of how everything works.
And I was blown away by the book, and I've since reread it on multiple occasions, even though I know everything that's in there. I just love the way that it communicates things.
In the year 2000, Joel Spolsky (founder of Stack Overflow) wrote a famous article titled “Things You Should Never Do, Part I.” In it, he talks about how rewriting your code from scratch is the single worst strategic mistake any software company can make. However, times have changed.
The cost of writing software is dropping exponentially and that has changed the math entirely on if it is worth rewriting your codebase. For instance, this year Anthropic’s Jarred Sumner ( @jarredsumner ) rewrote Bun in Rust in 11 days leading to many performance and correctness benefits.
Likewise, Stephen Toub (Distinguished Engineer at Microsoft, @stephentoub ) rewrote the GitHub Copilot runtime (400,000-line codebase) in Rust by himself. I thought it’d be interesting to lay out everything he learned in the process. So I interviewed him about how and why he did it.
In this episode:
• Why he choose Rust of all languages
• Rollout strategies (incremental vs all at once)
• How he prevented regressions
• Steering agents and which models he used
• Career lessons and engineering advice
Where to watch:
• YouTube - https://t.co/9Yj6kBj0ix
• Spotify - https://t.co/wa3my5QeBb
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/rI3rkhxsgG
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
01:06 Why the Copilot runtime needed a Rust port
05:38 Why he chose Rust
11:28 Discussing rollout strategies
21:57 How he caught regressions
32:08 Guiding the agents
42:11 Catching regressions before prod
45:16 Which models he used
50:03 The end benefit and costs
01:03:24 When to do a full rewrite
01:06:40 Career learnings on the way to Distinguished
01:16:00 Top technical book recommendation
01:17:49 Advice for young engineers
01:21:00 Outro
Creator of Postgres's top technical book recommendation for understanding databases
Ryan: For people who want to deeply understand databases. They're looking for some material to study. Is there a book that you recommend that's a top technical book to learn?
Mike Stonebraker (Turing Award Winner): Databases, papers in the literature. Joey Hellerstein and I published a red book, called Readings in Database Systems. It's now eight years old.
I think that would be a great set of readings from eight years ago and beyond that, popular papers from the literature.
Mike Stonebraker is a Turing award winner famous for his fundamental contributions to databases (e.g. Postgres, C-Store and much more). I interviewed him recently about:
• The story behind Postgres & the hardest technical challenge in building it
• Where he disagreed with Google's technical decisions
• Future problems in databases
• Literature recommendations to learn databases
• Why LLMs score 0% on his text-SQL benchmark
• What if you replaced all state in an OS with a DB
Timestamps:
0:00 - Intro
1:03 - How he got into databases
6:43 - Competing with Oracle
9:07 - What made Postgres special
15:55 - One size fits none
21:37 - Why he disagreed with Google
29:14 - Why he chose academia over big tech
30:58 - Replacing state in an OS with a DB
42:02 - Future problems in databases
51:36 - Technical book recommendations to learn databases
52:20 - Advice for younger self
55:52 - Outro
Where to watch:
• YouTube: https://t.co/YCunRSEIUK
• Spotify: https://t.co/7cCzATzN8z
• Apple Podcasts: https://t.co/jOYDGtGVnt
• Transcript: https://t.co/36BL7eGNmq
Anders Hejlsberg (creator of TypeScript and C#) on if AI will replace jr software engineers
Ryan: Three years from now, will AI replace junior software engineers or what junior software engineers do today?
Anders Hejlsberg (Creator of Typescript): Well, if it does, then how do we ever get senior software engineers? Right? It's just like, I don't think so.
Well, I'm not. Unless you also believe that you will be able to do your business three years later than that without any senior software engineers.
Ryan: Right.
Anders: Because where are they going to come from you got to train them, I mean. But to me, I think maybe one thing that to some extent has happened is that for certain classes of programmers, the pyramid has narrowed at the bottom.
There are fewer people coming in, and we are wanting them to advance higher up faster so that they can get to this more supervisory role.
I think the craft of being a software engineer is definitely changing from your typing in lines of code to you're having agents type in lines of code and you are reviewing the work of the agents. So you do more reviewing, less typing.
Some people love that and really are fantastic at that workflow. But it's a change in nature of what the job looks like as a programmer and this tool that you now have in a toolbox is having that impact.
But it is but a tool and there are still programmers involved in the process that I firmly believe.
Anders Hejlsberg ( @ahejlsberg ) is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering.
In this episode:
• How rewriting the compiler makes it 10x faster
• Why they picked Go instead of Rust
• Why they didn't use LLMs for the migration
• Predictions on AI's impact on software engineering
Where to watch:
• YouTube - https://t.co/h4WaILM1u6
• Spotify - https://t.co/tl9pLEKQmb
• Apple Podcasts - https://t.co/jOYDGtHtd1
• Transcript - https://t.co/mCS76KpPr7
Thank you to the sponsors of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzGc3U
• Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at https://t.co/ALUmdUvYHZ
Chapters:
00:00 Intro
00:48 Why write a compiler in JavaScript
07:29 Why rewrite the compiler in Go
14:49 LLMs for large migrations
20:12 Why Javascript is so popular
26:32 Why ever use Javascript on the backend
32:59 What it takes to build a programming language
37:06 Will there be fewer languages in 10 years
42:57 Hands on engineering vs delegation
49:14 Why fast tooling matters more now
51:16 AI software engineering predictions
58:52 The most technically challenging work
01:02:04 Top book recommendation
01:03:50 Advice for his younger self
01:05:00 Outro
Retired Netflix eng director on the most critical engineer he worked with:
David Ronca (Retired Netflix Eng Director): Apparently the most critical engineer. Oh, if we lose him, we're toast. The guy's cubicle was so full of junk, the walls were bulging out.
He was like a pack rat. And he wouldn't engage with anybody, and he would work all night and fix problems. He was always the hero.
And the managers, they did, had no understanding of what he did or whatever, but all they knew is if he quit, we're in trouble. Well, he quit, right? And guess what?
The company didn't die, right? Once he was out of the way, he wanted to do something else. Everybody else moved in.
They actually had other people understand, just nobody could work with this guy. And he established himself as the center of gravity for this one big area of our system. I think it was
David Ronca was an engineering director at both Netflix and Meta. Recently he retired so he was willing to transparently share advice and stories from his 36 year career. We discussed:
• How Netflix differed from everywhere else he worked
• The legendary 2009 culture memo
• Why people crush Leetcode yet produce bad work
• Regrets and advice for his younger self
• How a near death experience early in his career changed him
Where to watch:
• YouTube: https://t.co/DhvOzHtXcN
• Spotify: https://t.co/8z7ey0N6W3
• Apple: https://t.co/jOYDGtHtd1
• Transcript: https://t.co/OYfuqJhfVR
Turing Award winner on building a file system on a database
Mike Stonebraker (Turing Award Winner): A file system written on top of a DBMS is faster than the Linux file system. The scheduling engine is competitive with other scheduling engines. You can make everything fail over, so you get high availability without having to do anything else.
There's really no downside.
Ryan: Then why wouldn't Linux incorporate that and upgrade itself with this?
Mike: You hope they would. In other words, you should keep all the device driver junk down at the bottom because there's a lot of it, and no one wants to do that. Replace everything else with the database implementation.
Ryan: Is that something you've mentioned to Linux people, and what's their typical reaction?
Mike: Back in the academic project, when I mentioned that to the Operating System folks, they would get very threatened. This is the database guys trying to take over their turf,
Mike Stonebraker is a Turing award winner famous for his fundamental contributions to databases (e.g. Postgres, C-Store and much more). I interviewed him recently about:
• The story behind Postgres & the hardest technical challenge in building it
• Where he disagreed with Google's technical decisions
• Future problems in databases
• Literature recommendations to learn databases
• Why LLMs score 0% on his text-SQL benchmark
• What if you replaced all state in an OS with a DB
Timestamps:
0:00 - Intro
1:03 - How he got into databases
6:43 - Competing with Oracle
9:07 - What made Postgres special
15:55 - One size fits none
21:37 - Why he disagreed with Google
29:14 - Why he chose academia over big tech
30:58 - Replacing state in an OS with a DB
42:02 - Future problems in databases
51:36 - Technical book recommendations to learn databases
52:20 - Advice for younger self
55:52 - Outro
Where to watch:
• YouTube: https://t.co/YCunRSEIUK
• Spotify: https://t.co/7cCzATzN8z
• Apple Podcasts: https://t.co/jOYDGtGVnt
• Transcript: https://t.co/36BL7eGNmq
Venki Ramakrishnan (Molecular biologist, Nobel Prize): "The experimental part [of drug discovery] is always going to be the bottleneck."
Recent headlines about using AI to speed up drug discovery made me curious about what that looks like and where it is today. So I flew to the UK to interview Venki Ramakrishnan who is on the scientific advisory board of Demis Hassabis' Isomorphic Labs.
He has described himself as a "failed physicist" starting originally with a physics PhD who changed fields because he felt his work was incremental. After pivoting into molecular biology without a degree he discovered the field of work that eventually led to his Nobel prize.
So aside from drug discovery, I also asked him about how AI is impacting the field of biology, how biology compares to physics, and the politics behind the Nobel prize.
Chapters:
00:00 Intro
00:43 How drugs are designed
04:54 Why drug testing remains difficult
07:02 How AI will impact the field of biology
10:35 Switching from physics to biology
15:00 How to choose research problems that matter
23:19 Did lacking a credential hurt his career
26:50 Physics vs biology
33:21 Why physicists succeed in other fields
35:10 The politics of the Nobel Prize
38:37 Top scientific book recommendations
40:05 Advice for young people
41:43 Outro
Where to watch:
• YouTube - https://t.co/MuIiZtAnQG
• Spotify - https://t.co/OtCWuJWxCZ
• Apple Podcasts - https://t.co/jOYDGtHtd1
• Transcript - https://t.co/MkmzGqz0Og
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzGc3U
@bcantrill I love the idea of extending it to the present, then people can follow along to see if they are ever vindicated which would be interesting! Thank you
What is the most interesting question you could ask anyone?
Want to improve the questions I ask for my podcast. Most questions are tailored to the guest but some questions like "what's your top book recommendation" are more general
I asked ChatGPT, Claude, and Gemini for their top ideas:
ChatGPT: "What's a question you've spent years thinking about but still don't know the answer to?"
Gemini: "What is a deeply held belief you had for years that you recently completely reversed your position on?"
Claude: "What’s something you were confidently wrong about for years, and what finally made it click?"
Gemini/Claude recs feel a little cliche, the ChatGPT one does make me curious though for guests at the frontier
Open to feedback and ideas, I will factor your replies into my future questions
@MagpieMcGraw If someone has been hidden with what they want in public, they’re unlikely to reveal it on a podcast imo (although I would be interested too hypothetically)
@implabinash Good idea, when I have a big guest I’m confident about I’ll solicit questions from the audience
Also to your question on the best part of podcasting, it is the privilege of chasing my interests as a job. I feel very lucky