Loading video...

Video Failed to Load

Go Home

Anders Hejlsberg ( Anders Hejlsberg ) 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...

ryanlpeterman's profile picture

Ryan Peterman

28,563 subscribers

59,982 views • 6 days ago •via X (Twitter)

Science & TechnologyEducation
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self
1:27:52

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self

Ryan Peterman

128,294 views • 2 months ago

Leonardo de Moura (Leonardo de Moura) is the creator of Lean and the Z3 theorem prover. I talked with him about how Lean works and why LLMs plus Lean will fundamentally change how we write software and do math. In this episode: • How formal verification and proof assistants work • How Lean will impact handwritten math & software • Lean’s role in recent math breakthroughs • When software is worth formalizing Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 Intro 00:28 How formal verification works 05:21 A new way of writing software 13:15 Proof assistants vs programming languages 21:06 How Lean has assisted in mathematical breakthroughs 32:03 When is it worth formalizing software 33:29 How Lean will impact handwritten math 38:55 The Z3 theorem prover project he started 45:44 The most technically challenging work of his career 51:10 Lean vs its competitors 01:00:37 The future of Lean 01:04:10 Technical book recommendations 01:06:15 Advice for his younger self 01:07:10 Outro
1:08:06

Leonardo de Moura (Leonardo de Moura) is the creator of Lean and the Z3 theorem prover. I talked with him about how Lean works and why LLMs plus Lean will fundamentally change how we write software and do math. In this episode: • How formal verification and proof assistants work • How Lean will impact handwritten math & software • Lean’s role in recent math breakthroughs • When software is worth formalizing Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 Intro 00:28 How formal verification works 05:21 A new way of writing software 13:15 Proof assistants vs programming languages 21:06 How Lean has assisted in mathematical breakthroughs 32:03 When is it worth formalizing software 33:29 How Lean will impact handwritten math 38:55 The Z3 theorem prover project he started 45:44 The most technically challenging work of his career 51:10 Lean vs its competitors 01:00:37 The future of Lean 01:04:10 Technical book recommendations 01:06:15 Advice for his younger self 01:07:10 Outro

Ryan Peterman

13,570 views • 13 days ago

Xavier Leroy (creator of OCaml) is an expert in compilers, formal verification of software and functional programming. This interview should be an approachable resource if you're curious about formal verification of software since I was learning that on the fly during it. In this episode: • OCaml compared with Rust and JavaScript • What is formal verification and how does it work • How languages call each other across boundaries • How to address "almost-correct" LLM code • How type inference works in programming languages Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:43 - What sets OCaml apart 04:39 - OCaml vs Rust 07:57 - Why is manual memory management more performant 11:21 - Javascript vs OCaml 14:00 - Famous Rob Pike quote 16:05 - Type inference and how it works 22:12 - What is formal verification and how does it work 40:07 - What made multicore support difficult for OCaml 50:17 - How programming languages interface and call each other 57:41 - The danger of almost-correct LLM code 01:05:39 - How LLMs will change programming languages 01:10:26 - Industry vs academia 01:15:05 - Most interesting unsolved problems 01:18:30 - Top book recommendations for engineers 01:21:17 - Advice for his younger self 01:23:31 - Outro
1:24:27

Xavier Leroy (creator of OCaml) is an expert in compilers, formal verification of software and functional programming. This interview should be an approachable resource if you're curious about formal verification of software since I was learning that on the fly during it. In this episode: • OCaml compared with Rust and JavaScript • What is formal verification and how does it work • How languages call each other across boundaries • How to address "almost-correct" LLM code • How type inference works in programming languages Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:43 - What sets OCaml apart 04:39 - OCaml vs Rust 07:57 - Why is manual memory management more performant 11:21 - Javascript vs OCaml 14:00 - Famous Rob Pike quote 16:05 - Type inference and how it works 22:12 - What is formal verification and how does it work 40:07 - What made multicore support difficult for OCaml 50:17 - How programming languages interface and call each other 57:41 - The danger of almost-correct LLM code 01:05:39 - How LLMs will change programming languages 01:10:26 - Industry vs academia 01:15:05 - Most interesting unsolved problems 01:18:30 - Top book recommendations for engineers 01:21:17 - Advice for his younger self 01:23:31 - Outro

Ryan Peterman

23,942 views • 1 month ago

Ryan Williams (Ryan Williams @rrwilliams.bsky.social) is a professor at MIT and the winner of the Gödel Prize in theoretical computer science. I interviewed him all about his work starting by asking him a popular Leetcode question (3 SUM). In this episode: • Solving Leetcode faster than popular "optimal" solutions • SAT problems and solvers • Hot takes on famous open questions • How to pick good research direction Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:41 - Asking him a popular Leetcode question 03:54 - Doing better than the popular optimal solution 08:26 - Fine grained complexity 17:00 - A severe strengthening of P vs NP 24:38 - SAT problems and solvers 34:51 - Hot takes on famous open questions 46:57 - Simulating space with time 01:01:02 - Why he solves hard problems 01:02:35 - How to pick good research direction 01:07:14 - Technical book recommendations 01:08:31 - Advice for his younger self 01:11:56 - Outro
1:12:52

Ryan Williams (Ryan Williams @rrwilliams.bsky.social) is a professor at MIT and the winner of the Gödel Prize in theoretical computer science. I interviewed him all about his work starting by asking him a popular Leetcode question (3 SUM). In this episode: • Solving Leetcode faster than popular "optimal" solutions • SAT problems and solvers • Hot takes on famous open questions • How to pick good research direction Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:41 - Asking him a popular Leetcode question 03:54 - Doing better than the popular optimal solution 08:26 - Fine grained complexity 17:00 - A severe strengthening of P vs NP 24:38 - SAT problems and solvers 34:51 - Hot takes on famous open questions 46:57 - Simulating space with time 01:01:02 - Why he solves hard problems 01:02:35 - How to pick good research direction 01:07:14 - Technical book recommendations 01:08:31 - Advice for his younger self 01:11:56 - Outro

Ryan Peterman

148,279 views • 1 month ago

Avi Wigderson is the only person in history to have won both a Turing Award (computer science) and Abel Prize (math). I interviewed him all about his field. We discussed: • His intuition on a proof of P vs NP • Why we use SAT solvers for most NP problems • Zero knowledge proofs and their impact • Quantum computation and implications • Math and computer science's relationship Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsors 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 Timestamps: 00:00 - Intro 01:08 - P vs NP 14:51 - What if you relaxed correctness 25:38 - Why NP complete problems are equivalent 30:33 - Space vs time complexity 43:06 - Why people use SAT solvers 45:53 - Randomness is a resource 55:48 - Randomness depends on computational power 01:21:20 - Zero knowledge proofs and their significance 01:38:30 - Quantum computation and why it matters 01:56:24 - Math vs computer science 02:08:16 - Major breakthroughs and his experience 02:12:31 - Advice for his younger self 02:14:48 - Outro
2:15:47

Avi Wigderson is the only person in history to have won both a Turing Award (computer science) and Abel Prize (math). I interviewed him all about his field. We discussed: • His intuition on a proof of P vs NP • Why we use SAT solvers for most NP problems • Zero knowledge proofs and their impact • Quantum computation and implications • Math and computer science's relationship Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsors 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 Timestamps: 00:00 - Intro 01:08 - P vs NP 14:51 - What if you relaxed correctness 25:38 - Why NP complete problems are equivalent 30:33 - Space vs time complexity 43:06 - Why people use SAT solvers 45:53 - Randomness is a resource 55:48 - Randomness depends on computational power 01:21:20 - Zero knowledge proofs and their significance 01:38:30 - Quantum computation and why it matters 01:56:24 - Math vs computer science 02:08:16 - Major breakthroughs and his experience 02:12:31 - Advice for his younger self 02:14:48 - Outro

Ryan Peterman

259,775 views • 2 months ago

David Malan (David J. Malan) is a professor at Harvard famous for transforming CS50 into a freely-available, world-class online course. I interviewed him about: • How he went from student -> teacher of CS50 • The knowledge that matters most in the future (not just programming) • How to be engaging in long-form lectures • How AI has impacted CS education including cheating / academic dishonesty • Advice for his younger self Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: 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 • 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 Timestamps: 0:00 - Intro 1:09 - Getting into computer science 3:27 - Becoming the professor of CS50 11:19 - How to lecture well 14:25 - Depth vs engagement in education 18:11 - Why don't we consolidate educational resources 23:20 - Why start with C 31:51 - The ideal use of AI in education 34:54 - Cheating and AI 38:21 - Should we really learn CS still? 45:24 - College vs online education 47:06 - The most difficult concept to learn 51:00 - Growth vs fixed mindset 52:35 - The future of CS50 55:56 - Biggest career regret 1:00:29 - Top book recommendations 1:02:36 - Advice for his younger self 1:03:35 - Outro
1:04:30

David Malan (David J. Malan) is a professor at Harvard famous for transforming CS50 into a freely-available, world-class online course. I interviewed him about: • How he went from student -> teacher of CS50 • The knowledge that matters most in the future (not just programming) • How to be engaging in long-form lectures • How AI has impacted CS education including cheating / academic dishonesty • Advice for his younger self Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: 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 • 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 Timestamps: 0:00 - Intro 1:09 - Getting into computer science 3:27 - Becoming the professor of CS50 11:19 - How to lecture well 14:25 - Depth vs engagement in education 18:11 - Why don't we consolidate educational resources 23:20 - Why start with C 31:51 - The ideal use of AI in education 34:54 - Cheating and AI 38:21 - Should we really learn CS still? 45:24 - College vs online education 47:06 - The most difficult concept to learn 51:00 - Growth vs fixed mindset 52:35 - The future of CS50 55:56 - Biggest career regret 1:00:29 - Top book recommendations 1:02:36 - Advice for his younger self 1:03:35 - Outro

Ryan Peterman

23,116 views • 3 months ago

Vlad Feinberg (Vlad Feinberg) is Google DeepMind’s pre-training area lead and I asked him all about how to land a job at a frontier lab like Google DeepMind, Anthropic or OpenAI. In this episode: • Skills frontier labs need • Differences between software engineering and AI research • Domains that matter for frontier research • Concrete steps engineers can take to get closer to research • Jeff Dean spot bonus story Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:33 - Skills frontier labs need 08:45 - The difference between AI research and engineering 21:41 - Domains that matter for the frontier 30:50 - Marketing yourself to frontier labs 35:13 - Concrete steps engineers can take 38:29 - Overview of pre-training areas 47:23 - Jeff Dean spot bonus story 50:14 - Favorite Gemini war story 58:59 - Advice for his younger self 01:03:07 - Outro
1:04:03

Vlad Feinberg (Vlad Feinberg) is Google DeepMind’s pre-training area lead and I asked him all about how to land a job at a frontier lab like Google DeepMind, Anthropic or OpenAI. In this episode: • Skills frontier labs need • Differences between software engineering and AI research • Domains that matter for frontier research • Concrete steps engineers can take to get closer to research • Jeff Dean spot bonus story Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 Chapters: 00:00 - Intro 00:33 - Skills frontier labs need 08:45 - The difference between AI research and engineering 21:41 - Domains that matter for the frontier 30:50 - Marketing yourself to frontier labs 35:13 - Concrete steps engineers can take 38:29 - Overview of pre-training areas 47:23 - Jeff Dean spot bonus story 50:14 - Favorite Gemini war story 58:59 - Advice for his younger self 01:03:07 - Outro

Ryan Peterman

190,169 views • 2 months ago

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: • Spotify: • Apple Podcasts: • Transcript: 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 • 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 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
1:59:03

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: • Spotify: • Apple Podcasts: • Transcript: 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 • 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 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

Ryan Peterman

322,251 views • 3 months ago

James Cowling (James Cowling) was the most senior engineer at Dropbox (Senior Principal) before he left to start his own company, Convex. I interviewed him about: • Career navigation in the "AI era" • Why simplicity >> complexity • Promo incentives tied to complexity • Technical details of his major projects and PhD • His top career regrets • Thoughts on the permanent underclass Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsor 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 Timestamps: 0:00 - Intro 0:53 - Systems work during his PhD 13:05 - Dropbox technical deep dive 21:57 - Why Dropbox migrated from AWS 36:40 - How to do massive migrations 44:31 - Simplicity vs complexity in promos 49:23 - What technical teams should be focused on 1:00:25 - Doing the right thing vs promo hypothetical 1:08:13 - Why he dipped into management sometimes 1:11:36 - Why you shouldn't lead by example 1:23:23 - How to mentor Senior Staff+ engineers 1:27:30 - Career advice for the AI era 1:37:21 - Why he started his own company 1:46:05 - The most technically challenging work of his career 1:48:10 - How he got involved in Silicon Valley 1:52:16 - Career regrets 1:55:54 - Top technical book recommendation 1:56:36 - Younger self & permanent underclass advice
2:01:53

James Cowling (James Cowling) was the most senior engineer at Dropbox (Senior Principal) before he left to start his own company, Convex. I interviewed him about: • Career navigation in the "AI era" • Why simplicity >> complexity • Promo incentives tied to complexity • Technical details of his major projects and PhD • His top career regrets • Thoughts on the permanent underclass Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsor 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 Timestamps: 0:00 - Intro 0:53 - Systems work during his PhD 13:05 - Dropbox technical deep dive 21:57 - Why Dropbox migrated from AWS 36:40 - How to do massive migrations 44:31 - Simplicity vs complexity in promos 49:23 - What technical teams should be focused on 1:00:25 - Doing the right thing vs promo hypothetical 1:08:13 - Why he dipped into management sometimes 1:11:36 - Why you shouldn't lead by example 1:23:23 - How to mentor Senior Staff+ engineers 1:27:30 - Career advice for the AI era 1:37:21 - Why he started his own company 1:46:05 - The most technically challenging work of his career 1:48:10 - How he got involved in Silicon Valley 1:52:16 - Career regrets 1:55:54 - Top technical book recommendation 1:56:36 - Younger self & permanent underclass advice

Ryan Peterman

32,161 views • 3 months ago

Amjad Masad (Amjad Masad), co-founder & CEO of Replit, has spent nearly a decade making programming accessible to everyone. With AI, that vision is closer than ever. In his AI Startup School talk, Amjad traces computing’s arc from mainframes to PCs to a future where AI agents generate software on demand—driving the value of traditional software toward zero and reshaping how companies are built. 00:22 - Evolution of Computing 01:27 - The Rise of Software Engineering 02:16 - Replit's Vision: Making Programming Accessible 02:42 - The Role of AI in Software Development 04:32 - Challenges and Infrastructure for AI Agents 05:03 - Building a Scalable and Secure Environment 06:08 - Future of Software Engineering Agents 09:25 - Autonomy Levels in AI Agents 15:56 - Predictions for the Software Market 18:31 - Impact on Business and Employment 19:58 - The Role of Generalist Employees 26:00 - Audience Q&A
42:01

Amjad Masad (Amjad Masad), co-founder & CEO of Replit, has spent nearly a decade making programming accessible to everyone. With AI, that vision is closer than ever. In his AI Startup School talk, Amjad traces computing’s arc from mainframes to PCs to a future where AI agents generate software on demand—driving the value of traditional software toward zero and reshaping how companies are built. 00:22 - Evolution of Computing 01:27 - The Rise of Software Engineering 02:16 - Replit's Vision: Making Programming Accessible 02:42 - The Role of AI in Software Development 04:32 - Challenges and Infrastructure for AI Agents 05:03 - Building a Scalable and Secure Environment 06:08 - Future of Software Engineering Agents 09:25 - Autonomy Levels in AI Agents 15:56 - Predictions for the Software Market 18:31 - Impact on Business and Employment 19:58 - The Role of Generalist Employees 26:00 - Audience Q&A

Y Combinator

224,320 views • 11 months ago

What if we're actually in the middle of the third golden age of software engineering? This is what Grady Booch sees happening. If you are anxious about the state of the industry, you want to watch/listen to Grady's longer-term perspective and stories. Watch the full episode here: 00:00 Intro 01:58 The first golden age of software engineering 18:59 The software crisis 33:01 The second golden age of software engineering 42:21 Y2K and the Dotcom crash 45:47 Early AI 47:34 The third golden age of software engineering 51:48 Why software engineers will very much be needed 58:46 Grady responds to Dario Amodei 1:06:54 New skills engineers will need to succeed 1:10:04 Resources for studying complex systems 1:14:33 How to thrive during periods of change Brought to you by: • Statsig — ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for automated code review. Join me online at the Sonar Summit on March 3rd, where I talk about practical tactics for the AI era. • WorkOS – Everything you need to make your app enterprise-ready.
1:17:58

What if we're actually in the middle of the third golden age of software engineering? This is what Grady Booch sees happening. If you are anxious about the state of the industry, you want to watch/listen to Grady's longer-term perspective and stories. Watch the full episode here: 00:00 Intro 01:58 The first golden age of software engineering 18:59 The software crisis 33:01 The second golden age of software engineering 42:21 Y2K and the Dotcom crash 45:47 Early AI 47:34 The third golden age of software engineering 51:48 Why software engineers will very much be needed 58:46 Grady responds to Dario Amodei 1:06:54 New skills engineers will need to succeed 1:10:04 Resources for studying complex systems 1:14:33 How to thrive during periods of change Brought to you by: • Statsig — ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for automated code review. Join me online at the Sonar Summit on March 3rd, where I talk about practical tactics for the AI era. • WorkOS – Everything you need to make your app enterprise-ready.

Gergely Orosz

86,896 views • 6 months ago

Michael Bolin (Michael Bolin) is the tech lead of the Codex open source repository at OpenAI and formerly a distinguished eng (E9) at Meta. I asked him for all the details on his career story and how he uses Codex for max benefit. Timestamps: 00:00:00 - Intro 00:00:56 - Chickenfoot 00:02:45 - Working at Google 00:06:34 - Overhauling Facebook's build system 00:16:36 - Rewriting Facebook's IDE 00:26:01 - Struggles after Principal Eng (E8) promo 00:28:39 - Building a virtual filesystem for Facebook 00:35:47 - Delayed Distinguished promo (E9) and learnings 00:39:56 - Joining OpenAI 00:43:05 - Research-led vs engineering-led cultures 00:44:53 - The story behind Codex 00:51:00 - How he uses Codex 00:57:00 - Why Codex's harness is open source 00:59:50 - Top technical book recommendations 01:05:02 - Why deep technical skills are still valuable (for now) 01:11:07 - How to start projects well 01:14:27 - Advice on writing better and career planning 01:17:06 - Advice for his younger self 01:19:10 - Outro He was a dream guest of mine and I'm excited to share his story with you all! Other places to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript:
1:20:03

Michael Bolin (Michael Bolin) is the tech lead of the Codex open source repository at OpenAI and formerly a distinguished eng (E9) at Meta. I asked him for all the details on his career story and how he uses Codex for max benefit. Timestamps: 00:00:00 - Intro 00:00:56 - Chickenfoot 00:02:45 - Working at Google 00:06:34 - Overhauling Facebook's build system 00:16:36 - Rewriting Facebook's IDE 00:26:01 - Struggles after Principal Eng (E8) promo 00:28:39 - Building a virtual filesystem for Facebook 00:35:47 - Delayed Distinguished promo (E9) and learnings 00:39:56 - Joining OpenAI 00:43:05 - Research-led vs engineering-led cultures 00:44:53 - The story behind Codex 00:51:00 - How he uses Codex 00:57:00 - Why Codex's harness is open source 00:59:50 - Top technical book recommendations 01:05:02 - Why deep technical skills are still valuable (for now) 01:11:07 - How to start projects well 01:14:27 - Advice on writing better and career planning 01:17:06 - Advice for his younger self 01:19:10 - Outro He was a dream guest of mine and I'm excited to share his story with you all! Other places to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript:

Ryan Peterman

119,601 views • 5 months ago

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”
1:16:01

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”

Gergely Orosz

129,443 views • 3 months ago

.Poetiq is a new startup that recently achieved a major jump on the ARC-AGI benchmark by layering a recursive self-improvement system on top of existing models. In this episode of the Lightcone Podcast, Poetiq's Founder & CEO Ian Fischer joined us to discuss how small teams can build “reasoning harnesses” that outperform base models, what that means for startups and why automating prompt engineering may be one of the most powerful levers in AI today. 00:00 – Intro 00:40 – What Is Poetiq? 01:07 – Recursive Self-Improvement Explained 02:07 – The Fine-Tuning Trap 02:59 – “Stilts” for LLMs 03:14 – Recursive Self-Improvement vs. Fine-Tuning 05:05 – Taking the Top Spot on ARC-AGI 06:37 – Beating Claude on Humanity’s Last Exam 08:40 – How the Meta-System Works 10:26 – Beyond RL: A New S-Curve 11:32 – Automating Prompt Engineering 13:37 – From 5% to 95% Performance 14:50 – Early Access & Putting Your Agent on Stilts 16:17 – From YC Founder to DeepMind Researcher 18:29 – Advice for Engineers in the AI Era
19:45

.Poetiq is a new startup that recently achieved a major jump on the ARC-AGI benchmark by layering a recursive self-improvement system on top of existing models. In this episode of the Lightcone Podcast, Poetiq's Founder & CEO Ian Fischer joined us to discuss how small teams can build “reasoning harnesses” that outperform base models, what that means for startups and why automating prompt engineering may be one of the most powerful levers in AI today. 00:00 – Intro 00:40 – What Is Poetiq? 01:07 – Recursive Self-Improvement Explained 02:07 – The Fine-Tuning Trap 02:59 – “Stilts” for LLMs 03:14 – Recursive Self-Improvement vs. Fine-Tuning 05:05 – Taking the Top Spot on ARC-AGI 06:37 – Beating Claude on Humanity’s Last Exam 08:40 – How the Meta-System Works 10:26 – Beyond RL: A New S-Curve 11:32 – Automating Prompt Engineering 13:37 – From 5% to 95% Performance 14:50 – Early Access & Putting Your Agent on Stilts 16:17 – From YC Founder to DeepMind Researcher 18:29 – Advice for Engineers in the AI Era

Y Combinator

156,173 views • 5 months ago

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”
1:33

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”

The Pragmatic Engineer

116,193 views • 2 months ago

Sat down with Aaron Levie, CEO of Box, to discuss where AI agents are going, how agentic workflows are transforming software, why agents will require much more memory, and how token budgets for enterprises are evolving. Thank you Aaron Levie for taking the time! 00:00 - Intro 01:30 - Where are we in AI 06:25 - The Role of Agents in Software 11:40 - The Role of Memory for Agents 14:45 - TokenMaxxing 24:54 - Why Are There AI Doomers? 31:50 - Aaron's Take on Nvidia
32:57

Sat down with Aaron Levie, CEO of Box, to discuss where AI agents are going, how agentic workflows are transforming software, why agents will require much more memory, and how token budgets for enterprises are evolving. Thank you Aaron Levie for taking the time! 00:00 - Intro 01:30 - Where are we in AI 06:25 - The Role of Agents in Software 11:40 - The Role of Memory for Agents 14:45 - TokenMaxxing 24:54 - Why Are There AI Doomers? 31:50 - Aaron's Take on Nvidia

amit

96,221 views • 1 month ago

tylercowen is bullish on AI education — here's why. 00:00 -- Preview 00:24 -- President Carlos Carvalho's AI-generated intro 03:21 -- Cowen reacts to UATX's campus 04:38 -- The AI revolution is here. Who will lose the most? 06:05 -- AI lawyers 07:17 -- Don't underestimate this 10:41 -- Changes to the "upper upper middle class" 12:38 -- How to be successful 13:43 -- The rise of managerial empires 14:02 -- When will we have the first billion dollar company with one employee? 16:05 -- 10-20 year forecast 16:19 -- Why education is so behind 17:01 -- Should you be bullish on UATX? 18:36 -- Should you still read Homer? 21:50 -- Write to think 25:01 -- Meet more people 25:42 -- How to get hired 26:54 -- Is AI your best mentor? 38:17 -- How to curb cheating 39:02 -- The new life of the mind 42:34 -- Q&A: Will there be more status associated with real education or AI education? 45:50 -- Q&A: Why do tech-savvy students need to practice using AI? 47:56 -- Q&A: Do LLMs atrophy your mind? 49:29 -- Q&A: How do you avoid AI-dependency? 51:05 -- Q&A: Isn't this vision lonely and isolating? 53:06 -- Q&A: Do students need teachers? 55:36 -- Q&A: What are the four most important courses for undergrads? 57:49 -- Q&A: Which AI company will win the AI race in the next five years and why? 59:22 -- Q&A: Can AI teach religion? 01:01:32 -- Q&A: Will AI narrow or widen our world? 01:04:37 -- Q&A: What makes us human? 01:05:42 -- Q&A: What is art? 01:08:33 -- Q&A: It's easy to catch cheaters
1:10:31

tylercowen is bullish on AI education — here's why. 00:00 -- Preview 00:24 -- President Carlos Carvalho's AI-generated intro 03:21 -- Cowen reacts to UATX's campus 04:38 -- The AI revolution is here. Who will lose the most? 06:05 -- AI lawyers 07:17 -- Don't underestimate this 10:41 -- Changes to the "upper upper middle class" 12:38 -- How to be successful 13:43 -- The rise of managerial empires 14:02 -- When will we have the first billion dollar company with one employee? 16:05 -- 10-20 year forecast 16:19 -- Why education is so behind 17:01 -- Should you be bullish on UATX? 18:36 -- Should you still read Homer? 21:50 -- Write to think 25:01 -- Meet more people 25:42 -- How to get hired 26:54 -- Is AI your best mentor? 38:17 -- How to curb cheating 39:02 -- The new life of the mind 42:34 -- Q&A: Will there be more status associated with real education or AI education? 45:50 -- Q&A: Why do tech-savvy students need to practice using AI? 47:56 -- Q&A: Do LLMs atrophy your mind? 49:29 -- Q&A: How do you avoid AI-dependency? 51:05 -- Q&A: Isn't this vision lonely and isolating? 53:06 -- Q&A: Do students need teachers? 55:36 -- Q&A: What are the four most important courses for undergrads? 57:49 -- Q&A: Which AI company will win the AI race in the next five years and why? 59:22 -- Q&A: Can AI teach religion? 01:01:32 -- Q&A: Will AI narrow or widen our world? 01:04:37 -- Q&A: What makes us human? 01:05:42 -- Q&A: What is art? 01:08:33 -- Q&A: It's easy to catch cheaters

University of Austin (UATX)

27,770 views • 7 months ago

New episode with Dr. Konrad Kording (Kording Lab 🦖), professor of bioengineering and neuroscience at the University of Pennsylvania (Penn) and co-director of CIFAR's Learning in Machines & Brains program (CIFAR). Konrad works at the intersection of causality, machine learning, and neuroscience, building rigorous methods for causal reasoning when experiments aren't possible — and challenging how researchers interpret neural data and build AI. Konrad argues the most promising path to understanding how the brain works is to read the brain’s wiring directly, down to the molecular detail of each connection, and to build compilers and simulations to understand the brain’s computation directly. In this episode we go deep into how neurons work, how neurons wire together, and how organic and artificial neural networks differ. We discuss why organic neurons are doing much more; how a model of a single organic neuron can solve MNIST — computing more like a 3-layer artificial neural network; how the brain might learn by solving credit assignment with only local signals; how to approximate backprop without a global algorithm; why AI and humans are intelligent along different dimensions; why Konrad isn’t very worried about AI replacing us; economic models of intelligence and physical work; and much more. Konrad is a brilliant, contrarian thinker who explains complex concepts very intuitively. It is a solid computational neuroscience primer. I hope you enjoy this conversation as much as I did! Other links to this episode and references below. Chapters 00:00:00 Introduction 00:01:01 How organic neurons work 00:24:13 How the brain learns: circuits and credit assignment 00:45:29 Recording the brain 00:52:47 Why simulating brains is hard 01:05:00 A new approach: connectomes and compilers 01:21:00 Why simulate brains? 01:29:50 How AI and human intelligence differ 01:41:04 Evolution, intelligence and AI risk 01:52:42 Robotics, causality, and the roots of intelligence 02:05:53 AI for science and scientific rigor 02:13:05 The economics of intelligence 02:27:50 A hopeful future
2:29:40

New episode with Dr. Konrad Kording (Kording Lab 🦖), professor of bioengineering and neuroscience at the University of Pennsylvania (Penn) and co-director of CIFAR's Learning in Machines & Brains program (CIFAR). Konrad works at the intersection of causality, machine learning, and neuroscience, building rigorous methods for causal reasoning when experiments aren't possible — and challenging how researchers interpret neural data and build AI. Konrad argues the most promising path to understanding how the brain works is to read the brain’s wiring directly, down to the molecular detail of each connection, and to build compilers and simulations to understand the brain’s computation directly. In this episode we go deep into how neurons work, how neurons wire together, and how organic and artificial neural networks differ. We discuss why organic neurons are doing much more; how a model of a single organic neuron can solve MNIST — computing more like a 3-layer artificial neural network; how the brain might learn by solving credit assignment with only local signals; how to approximate backprop without a global algorithm; why AI and humans are intelligent along different dimensions; why Konrad isn’t very worried about AI replacing us; economic models of intelligence and physical work; and much more. Konrad is a brilliant, contrarian thinker who explains complex concepts very intuitively. It is a solid computational neuroscience primer. I hope you enjoy this conversation as much as I did! Other links to this episode and references below. Chapters 00:00:00 Introduction 00:01:01 How organic neurons work 00:24:13 How the brain learns: circuits and credit assignment 00:45:29 Recording the brain 00:52:47 Why simulating brains is hard 01:05:00 A new approach: connectomes and compilers 01:21:00 Why simulate brains? 01:29:50 How AI and human intelligence differ 01:41:04 Evolution, intelligence and AI risk 01:52:42 Robotics, causality, and the roots of intelligence 02:05:53 AI for science and scientific rigor 02:13:05 The economics of intelligence 02:27:50 A hopeful future

Juan Benet

50,121 views • 1 month ago

State of Enterprise AI 2026: Aaron Levie on Tokenmaxxing, The Rise of Headless, and AI-Proofing Your Job 00:00 Intro 01:18 Silicon Valley engineering vs. everyone else 05:35 Are enterprise CIOs actually bullish on AI? 08:51 Tokenmaxxing & why your AI bill is about to explode 11:34 The myth of falling token costs and AI spend escaping IT budgets 17:37 The $5B startup hiding in AI compute 18:14 The mosaic of models inside every enterprise 21:28 Why coding works and the rest of knowledge work doesn't 25:53 The Bob and Sally problem: access control breaks agents 30:31 Will enterprise AI really take 10 years to roll out 32:24 The capability overhang: why faster models slow diffusion 34:23 Data is the bottleneck (it always was) 39:02 The rise of internal forward-deployed engineers 41:23 Why the AI doomers are wrong about jobs 43:43 Headless software is inevitable 46:14 What replaces per-seat pricing 47:37 How Box itself is going headless 49:42 How the org chart actually evolves 1:00:33 Future-proofing yourself as an enterprise employee 1:06:40 Are we all just going to work for OpenAI and Anthropic? 1:07:11 Where startups can still win as the labs move up
1:12:54

State of Enterprise AI 2026: Aaron Levie on Tokenmaxxing, The Rise of Headless, and AI-Proofing Your Job 00:00 Intro 01:18 Silicon Valley engineering vs. everyone else 05:35 Are enterprise CIOs actually bullish on AI? 08:51 Tokenmaxxing & why your AI bill is about to explode 11:34 The myth of falling token costs and AI spend escaping IT budgets 17:37 The $5B startup hiding in AI compute 18:14 The mosaic of models inside every enterprise 21:28 Why coding works and the rest of knowledge work doesn't 25:53 The Bob and Sally problem: access control breaks agents 30:31 Will enterprise AI really take 10 years to roll out 32:24 The capability overhang: why faster models slow diffusion 34:23 Data is the bottleneck (it always was) 39:02 The rise of internal forward-deployed engineers 41:23 Why the AI doomers are wrong about jobs 43:43 Headless software is inevitable 46:14 What replaces per-seat pricing 47:37 How Box itself is going headless 49:42 How the org chart actually evolves 1:00:33 Future-proofing yourself as an enterprise employee 1:06:40 Are we all just going to work for OpenAI and Anthropic? 1:07:11 Where startups can still win as the labs move up

Matt Turck

49,634 views • 2 months ago