Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

29,839 subscribers

61,917 Aufrufe • vor 1 Monat •via X (Twitter)

Wissenschaft & TechnologieBildung
LIVE

Anya Rossi• Live Now

Private livecam show

6 Kommentare

Profilbild von __pythonista
__pythonistavor 1 Monat

@ahejlsberg And before that, Turbo Pascal and Delphi. The guy is an absolute legend.

Profilbild von David Brown
David Brownvor 1 Monat

@ahejlsberg Hejlsberg is a legend, great interview!

Profilbild von 7alken
7alkenvor 1 Monat

@ahejlsberg 6:41 ...are you only too young or its deeper?

Profilbild von Nkanauzu
Nkanauzuvor 1 Monat

@ahejlsberg Porting, not rewriting. If it were to be rewriting, it would have been in C# or Rust.

Profilbild von Dave Choi
Dave Choivor 1 Monat

@ahejlsberg Wrong Luke Hoban and Steve Lucco are the original creators of TypeScript, originally known as Strand Anders joined the team later

Profilbild von Dr. Jawa
Dr. Jawavor 1 Monat

@ahejlsberg (1) I really admired him starting with Turbo Pascal and then Delphi. They were always among the fastest #compilers on the market. With #TypeScript, I feel he lost the idea of his origins. The TypeScript transpiler was so slow. 👇

Ähnliche Videos

Martin Odersky (Martin Odersky) is the creator of Scala and I interviewed him to compare different languages designs (Rust vs Zig vs Python vs Scala) and how AI will impact programming languages. In this episode: • Comparing Rust, Zig, Python, and Scala designs • Why its hard to write a compiler • Predictions about how AI will impact software • Why functional programming matters Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:44 Why care about functional programming 06:35 Why should people learn Scala 09:26 Rust vs Scala 12:42 Rust vs Zig 15:45 Scala vs Python 18:31 The programming languages that influenced him 22:16 How running on the JVM works 26:33 Why writing a compiler is hard 29:19 Why Twitter adopted Scala early on 31:00 How he believes AI will impact programming languages 43:40 Will there be less engineers in ten years 44:34 Top programming languages to learn to grow 46:18 Top technical book recommendation 46:51 Why he chose academia instead of industry 48:28 Reflecting on Scala 55:42 Advice for his younger self 56:33 Outro
57:30

Martin Odersky (Martin Odersky) is the creator of Scala and I interviewed him to compare different languages designs (Rust vs Zig vs Python vs Scala) and how AI will impact programming languages. In this episode: • Comparing Rust, Zig, Python, and Scala designs • Why its hard to write a compiler • Predictions about how AI will impact software • Why functional programming matters Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - 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 • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:44 Why care about functional programming 06:35 Why should people learn Scala 09:26 Rust vs Scala 12:42 Rust vs Zig 15:45 Scala vs Python 18:31 The programming languages that influenced him 22:16 How running on the JVM works 26:33 Why writing a compiler is hard 29:19 Why Twitter adopted Scala early on 31:00 How he believes AI will impact programming languages 43:40 Will there be less engineers in ten years 44:34 Top programming languages to learn to grow 46:18 Top technical book recommendation 46:51 Why he chose academia instead of industry 48:28 Reflecting on Scala 55:42 Advice for his younger self 56:33 Outro

Ryan Peterman

103,762 Aufrufe • vor 1 Monat

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,845 Aufrufe • vor 4 Monaten

My goal was to record a conversation completely free of "AI doomer" takes as a timeline cleanser. For this episode, I interviewed Casey Muratori (Casey Muratori) who is a video game developer and programming creator also known for his talks about the history of computing. In this episode: • Surprising findings in computer history • Where bad code comes from • The only unbreakable law in software engineering • His career in the video game industry • Why you should read technical papers Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them 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 Chapters: 00:00 Intro 01:08 Digging into computer science history 04:08 What shocked him 16:23 Dijkstra was depressed 26:17 The personal side of goto considered harmful 35:09 The anatomy of a 35 year mistake 50:12 Clean code horrible performance 58:33 How to write high performance code 01:01:18 Where bad code comes from 01:06:37 Why design docs before code is a bad idea 01:09:20 The only unbreakable law in software engineering 01:15:57 How he got into programming 01:21:16 Why he didnt work in big tech 01:30:44 Should you work at a startup early on 01:34:52 What video game engineering is like 01:39:57 Why preventing recursion is reasonable 01:43:24 Is vibe coding bad for the industry 01:50:17 Technical reading recommendation 01:54:27 Advice for his younger self 01:56:54 Outro
1:57:50

My goal was to record a conversation completely free of "AI doomer" takes as a timeline cleanser. For this episode, I interviewed Casey Muratori (Casey Muratori) who is a video game developer and programming creator also known for his talks about the history of computing. In this episode: • Surprising findings in computer history • Where bad code comes from • The only unbreakable law in software engineering • His career in the video game industry • Why you should read technical papers Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them 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 Chapters: 00:00 Intro 01:08 Digging into computer science history 04:08 What shocked him 16:23 Dijkstra was depressed 26:17 The personal side of goto considered harmful 35:09 The anatomy of a 35 year mistake 50:12 Clean code horrible performance 58:33 How to write high performance code 01:01:18 Where bad code comes from 01:06:37 Why design docs before code is a bad idea 01:09:20 The only unbreakable law in software engineering 01:15:57 How he got into programming 01:21:16 Why he didnt work in big tech 01:30:44 Should you work at a startup early on 01:34:52 What video game engineering is like 01:39:57 Why preventing recursion is reasonable 01:43:24 Is vibe coding bad for the industry 01:50:17 Technical reading recommendation 01:54:27 Advice for his younger self 01:56:54 Outro

Ryan Peterman

62,932 Aufrufe • vor 29 Tagen

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,949 Aufrufe • vor 2 Monaten

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

24,256 Aufrufe • vor 2 Monaten

Thariq Shihipar (Thariq) is an engineer on Anthropic’s Claude Code team I asked him how Anthropic makes the most out of the models for engineering and how the industry will change soon. In this episode: • Internal best practices in leveraging the models • What percent of Anthropic's work is fully autonomous • How Anthropic maintains higher volumes of code • What has worked in preventing AI-written breakages 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:29 Onboarding at Anthropic 02:53 Internal capabilities vs external perception 06:16 Model vs Harness 08:55 What percent of Anthropics changes are fully autonomous 14:51 Computer use 17:42 How to make the most out of your compute 20:45 Loop engineering 22:47 Where the industry will go soon 26:02 Which model do Anthropic engineers use 27:38 Is learning a particular model worth it 30:56 Prompting tips for todays models 35:04 How to get the models to do tasteful work 39:00 How much of writing is done by AI at Anthropic 45:36 Code ownership and maintenance at Anthropic 52:04 How Anthropic prevents breakages 55:24 Visibility and sharing your work 58:42 Luck surface area example 01:00:57 Should people still learn to code 01:07:42 Advice for his younger self 01:09:58 Outro
1:10:54

Thariq Shihipar (Thariq) is an engineer on Anthropic’s Claude Code team I asked him how Anthropic makes the most out of the models for engineering and how the industry will change soon. In this episode: • Internal best practices in leveraging the models • What percent of Anthropic's work is fully autonomous • How Anthropic maintains higher volumes of code • What has worked in preventing AI-written breakages 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:29 Onboarding at Anthropic 02:53 Internal capabilities vs external perception 06:16 Model vs Harness 08:55 What percent of Anthropics changes are fully autonomous 14:51 Computer use 17:42 How to make the most out of your compute 20:45 Loop engineering 22:47 Where the industry will go soon 26:02 Which model do Anthropic engineers use 27:38 Is learning a particular model worth it 30:56 Prompting tips for todays models 35:04 How to get the models to do tasteful work 39:00 How much of writing is done by AI at Anthropic 45:36 Code ownership and maintenance at Anthropic 52:04 How Anthropic prevents breakages 55:24 Visibility and sharing your work 58:42 Luck surface area example 01:00:57 Should people still learn to code 01:07:42 Advice for his younger self 01:09:58 Outro

Ryan Peterman

65,784 Aufrufe • vor 1 Monat

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 Aufrufe • vor 3 Monaten

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

260,440 Aufrufe • vor 4 Monaten

Sergey Levine (Sergey Levine) is one of the world's top robotics researchers and co-founder of Physical Intelligence. We talked about where humanoid robotics is today, thoughts on the Chinese robotics ecosystem, and his predictions for future timelines. In this episode: • Current state of robotics and surprising capabilities so far • Chinese robotics compared to US ecosystem • If OpenAI and Anthropic got into robotics • His top robotics research paper recommendation • Predictions for when humanoid robotics will land 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:37 Where are we today 04:20 Most surprising capabilities so far 07:03 The most inspiring real world robotics 08:36 If OpenAI or Anthropic got into robotics 10:22 Chinese robotics 13:15 Will one lab breakout from the rest 16:59 Thoughts on a concrete roadmap 21:03 Generalization and demonstrating it 26:04 Types of data and which is best for robotics 34:34 Why humanoid robotics differs from Waymo 37:10 If humanoid robotics failed here is why 39:55 Are there hot take modeling architectures in robotics 42:05 Thoughts on AI safety in robotics 46:44 Top robotics research paper recommendation 49:35 Why is Boston Dynamics less top of mind 53:47 Advice for his younger self 56:42 Outro
57:38

Sergey Levine (Sergey Levine) is one of the world's top robotics researchers and co-founder of Physical Intelligence. We talked about where humanoid robotics is today, thoughts on the Chinese robotics ecosystem, and his predictions for future timelines. In this episode: • Current state of robotics and surprising capabilities so far • Chinese robotics compared to US ecosystem • If OpenAI and Anthropic got into robotics • His top robotics research paper recommendation • Predictions for when humanoid robotics will land 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:37 Where are we today 04:20 Most surprising capabilities so far 07:03 The most inspiring real world robotics 08:36 If OpenAI or Anthropic got into robotics 10:22 Chinese robotics 13:15 Will one lab breakout from the rest 16:59 Thoughts on a concrete roadmap 21:03 Generalization and demonstrating it 26:04 Types of data and which is best for robotics 34:34 Why humanoid robotics differs from Waymo 37:10 If humanoid robotics failed here is why 39:55 Are there hot take modeling architectures in robotics 42:05 Thoughts on AI safety in robotics 46:44 Top robotics research paper recommendation 49:35 Why is Boston Dynamics less top of mind 53:47 Advice for his younger self 56:42 Outro

Ryan Peterman

72,757 Aufrufe • vor 1 Monat

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 Aufrufe • vor 5 Monaten

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

191,659 Aufrufe • vor 4 Monaten

The singularity has already begun for math: Scott Aaronson is one of the world's leading quantum computing researchers and spent two years at OpenAI working on AI safety. We talked about why he thinks the singularity has already begun for math, who gets credit when AI writes the proof, and whether intelligence will still matter once machines do the thinking. In this episode: • Why the singularity has already begun for math • Who gets credit when AI writes the proof • What a proof that P = NP would be worth • Why he turned down getting rich to keep blogging • Whether intelligence will still matter 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:34 Why he updated so hard on AI 01:14 The people still denying AI progress 03:53 The singularity has already begun for math 08:30 Will human-driven math research survive 13:12 Who gets credit for AI-written papers 15:55 OpenAI's $15M Navier-Stokes proof 19:20 What if AI proved P = NP 23:07 Why AI is so good at finding counterexamples 26:13 The goalposts keep moving 28:52 Why AI disclosure matters in research 32:59 The fake Monet experiment 35:23 Why he blogs instead of getting rich 39:45 Are AI labs racing too fast 42:01 Will intelligence still matter 47:12 Book recommendations 52:27 Advice for students today 57:23 Reacting live to a new AI result 59:58 Outro
1:01:02

The singularity has already begun for math: Scott Aaronson is one of the world's leading quantum computing researchers and spent two years at OpenAI working on AI safety. We talked about why he thinks the singularity has already begun for math, who gets credit when AI writes the proof, and whether intelligence will still matter once machines do the thinking. In this episode: • Why the singularity has already begun for math • Who gets credit when AI writes the proof • What a proof that P = NP would be worth • Why he turned down getting rich to keep blogging • Whether intelligence will still matter 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:34 Why he updated so hard on AI 01:14 The people still denying AI progress 03:53 The singularity has already begun for math 08:30 Will human-driven math research survive 13:12 Who gets credit for AI-written papers 15:55 OpenAI's $15M Navier-Stokes proof 19:20 What if AI proved P = NP 23:07 Why AI is so good at finding counterexamples 26:13 The goalposts keep moving 28:52 Why AI disclosure matters in research 32:59 The fake Monet experiment 35:23 Why he blogs instead of getting rich 39:45 Are AI labs racing too fast 42:01 Will intelligence still matter 47:12 Book recommendations 52:27 Advice for students today 57:23 Reacting live to a new AI result 59:58 Outro

Ryan Peterman

71,001 Aufrufe • vor 1 Tag

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,714 Aufrufe • vor 4 Monaten

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 Aufrufe • vor 4 Monaten

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

87,027 Aufrufe • vor 8 Monaten

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 Aufrufe • vor 7 Monaten

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,757 Aufrufe • vor 5 Monaten

.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,465 Aufrufe • vor 7 Monaten

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,336 Aufrufe • vor 4 Monaten