Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Just six months ago, DHH (creator of Ruby on Rails and Omarchy) said how he doesn’t really use AI tools to write code, because they are not good enough. Things have changed, a lot. Timestamps: 00:00 Intro 02:11 Omarchy and Ruby on Rails 08:25 37signals overview 10:12 Launching HEY...

GergelyOrosz's profile picture

Gergely Orosz

345,093 subscribers

329,135 görüntüleme • 4 ay önce •via X (Twitter)

EğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

How has the day-to-day workflow of Mitchell Hashimoto (Mitchell Hashimoto) changed, thanks to AI tools? Timestamps: 00:00 Intro 07:19 HashiCorp origins 18:22 The 2010s startup scene in SF 23:11 Funding HashiCorp 25:23 The "Hashi stack" 38:28 The open-core pivot 48:08 Taking HashiCorp public 51:58 The almost-VMware acquisition 59:10 Mitchell’s take on AWS, GCP and Azure 01:06:02 AI’s impact on open source 01:07:00 Ghostty 01:19:13 How Mitchell uses AI 01:28:36 Open source + AI 01:31:46 The problem of Git and monorepos 01:39:57 Mitchell’s hiring practices 01:47:52 Mitchell’s AI adoption journey 01:50:41 Advice to future founders 01:55:03 Closing Also on YouTube, Spotify and Apple (see the next tweet) 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: • WorkOS – Everything you need to make your app enterprise ready.
1:58:23

How has the day-to-day workflow of Mitchell Hashimoto (Mitchell Hashimoto) changed, thanks to AI tools? Timestamps: 00:00 Intro 07:19 HashiCorp origins 18:22 The 2010s startup scene in SF 23:11 Funding HashiCorp 25:23 The "Hashi stack" 38:28 The open-core pivot 48:08 Taking HashiCorp public 51:58 The almost-VMware acquisition 59:10 Mitchell’s take on AWS, GCP and Azure 01:06:02 AI’s impact on open source 01:07:00 Ghostty 01:19:13 How Mitchell uses AI 01:28:36 Open source + AI 01:31:46 The problem of Git and monorepos 01:39:57 Mitchell’s hiring practices 01:47:52 Mitchell’s AI adoption journey 01:50:41 Advice to future founders 01:55:03 Closing Also on YouTube, Spotify and Apple (see the next tweet) 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: • WorkOS – Everything you need to make your app enterprise ready.

Gergely Orosz

59,544 görüntüleme • 5 ay önce

After many months, a lot of model releases and even more Amp releases, here it is: A new episode of Raising An Agent with Quinn Slack and Thorsten Ball. They discuss: - Why Gemini 3 might have been the inflection point, not Opus 4.5 - What changed over Christmas and why everybody talks about agents now - "The assistant is dead, long live the factory" - How codebases need to adapt for agents - Why small/local models don't give you an impression of the frontier - What does it mean for a codebase to be agent-friendly? - New things coming to Amp Enjoy! And happy hacking! Timestamps: 1:51 The Impact of Gemini 3 and Opus 4.5 5:28 Shifting Perceptions of AI Agents 10:17 Adapting Codebases for AI Efficiency 14:48 The Future of Software Development with AI Agents 19:29 Challenges and Opportunities Ahead 24:00 The Importance of Frontier Models 25:12 Adapting to AI-Driven Workflows 26:57 The Future of Coding Agents 28:07 Building an Agentic Code Base 30:22 Rethinking Development Tools 31:44 Amp's Evolution and Team Dynamics 33:00 Discord Q&A 39:18 Teasing New Features: Deep
40:50

After many months, a lot of model releases and even more Amp releases, here it is: A new episode of Raising An Agent with Quinn Slack and Thorsten Ball. They discuss: - Why Gemini 3 might have been the inflection point, not Opus 4.5 - What changed over Christmas and why everybody talks about agents now - "The assistant is dead, long live the factory" - How codebases need to adapt for agents - Why small/local models don't give you an impression of the frontier - What does it mean for a codebase to be agent-friendly? - New things coming to Amp Enjoy! And happy hacking! Timestamps: 1:51 The Impact of Gemini 3 and Opus 4.5 5:28 Shifting Perceptions of AI Agents 10:17 Adapting Codebases for AI Efficiency 14:48 The Future of Software Development with AI Agents 19:29 Challenges and Opportunities Ahead 24:00 The Importance of Frontier Models 25:12 Adapting to AI-Driven Workflows 26:57 The Future of Coding Agents 28:07 Building an Agentic Code Base 30:22 Rethinking Development Tools 31:44 Amp's Evolution and Team Dynamics 33:00 Discord Q&A 39:18 Teasing New Features: Deep

Amp

36,150 görüntüleme • 6 ay önce

No project has gotten more traction in such a short time than by Peter Steinberger 🦞 But how is he building it? Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • Statsig — ⁠The unified platform for flags, analytics, experiments, and more. Join us at The Pragmatic Summit I’m hosting with Statsig, on 11 February: • Sonar – The makers of SonarQube, the industry standard for automated code review. Join me online at the Sonar Summit, on 3rd March: • WorkOS – Everything you need to make your app enterprise ready. If you're in SF on 9 February, stop by at the WorkOS AI Night with The Pragmatic Engineer (free to register):
1:08

No project has gotten more traction in such a short time than by Peter Steinberger 🦞 But how is he building it? Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • Statsig — ⁠The unified platform for flags, analytics, experiments, and more. Join us at The Pragmatic Summit I’m hosting with Statsig, on 11 February: • Sonar – The makers of SonarQube, the industry standard for automated code review. Join me online at the Sonar Summit, on 3rd March: • WorkOS – Everything you need to make your app enterprise ready. If you're in SF on 9 February, stop by at the WorkOS AI Night with The Pragmatic Engineer (free to register):

Gergely Orosz

225,804 görüntüleme • 6 ay önce

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (Boris Cherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations 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. Proactively find and fix issues in real-time with the SonarQube MCP Server: • WorkOS – Everything you need to make your app enterprise ready. Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”
1:37:58

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (Boris Cherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations 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. Proactively find and fix issues in real-time with the SonarQube MCP Server: • WorkOS – Everything you need to make your app enterprise ready. Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”

Gergely Orosz

490,123 görüntüleme • 5 ay önce

It's always energizing to do a podcast with Steve Yegge (Steve Yegge, engineer+author, formerly at Amazon+Google, creator of Gas Town). Timestamps: 00:00 Intro 01:43 Steve’s latest projects 02:27 Important blog posts 04:48 Shifts in what engineers need to know 10:46 Steve’s current AI stance 13:23 Steve’s book Vibe Coding 18:25 Layoffs and disruption in tech 31:13 Gas Town 40:10 New ways of working 51:08 The problem of too many people 54:45 Why AI results lag in business 59:57 Gamification and product stickiness 1:04:54 The ‘Bitter Lesson’ explained 1:07:14 The future of software development 1:23:06 Where languages stand 1:24:47 Adapting to change 1:27:32 Steve’s predictions 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. • WorkOS – Everything you need to make your app enterprise ready. Three interesting thoughts from Steve that we talked about in this conversation: 1. Reading ability is becoming a blocker for wider AI adoption. Some struggle with walls of text that current AI tools produce, and Steve predicts that in the very near future, most people will program by talking to a visual avatar, not reading terminal output because he observes that five paragraphs is already a lot to read for many devs. 2. What software engineers need to know keeps changing. In the 1990s, any decent software engineer knew Assembly, and today almost no decent developer knows it because Assembly has long been superseded by technical progress. What engineers “need” to know these days is different from the ‘90s and that process continues with AI, changing the parts of the craft that are essential for devs. We grumble about this but that won’t change anything by itself. 3. There’s a “Dracula Effect” where AI-augmented work drains engineers faster than traditional work. This is because AI automates the easy tasks, meaning that engineers are stuck doing high-intensity thinking all day. Steve says you may only get three daily productive hours at max speed, but during that time, you could produce 100x more output than before.
1:31:59

It's always energizing to do a podcast with Steve Yegge (Steve Yegge, engineer+author, formerly at Amazon+Google, creator of Gas Town). Timestamps: 00:00 Intro 01:43 Steve’s latest projects 02:27 Important blog posts 04:48 Shifts in what engineers need to know 10:46 Steve’s current AI stance 13:23 Steve’s book Vibe Coding 18:25 Layoffs and disruption in tech 31:13 Gas Town 40:10 New ways of working 51:08 The problem of too many people 54:45 Why AI results lag in business 59:57 Gamification and product stickiness 1:04:54 The ‘Bitter Lesson’ explained 1:07:14 The future of software development 1:23:06 Where languages stand 1:24:47 Adapting to change 1:27:32 Steve’s predictions 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. • WorkOS – Everything you need to make your app enterprise ready. Three interesting thoughts from Steve that we talked about in this conversation: 1. Reading ability is becoming a blocker for wider AI adoption. Some struggle with walls of text that current AI tools produce, and Steve predicts that in the very near future, most people will program by talking to a visual avatar, not reading terminal output because he observes that five paragraphs is already a lot to read for many devs. 2. What software engineers need to know keeps changing. In the 1990s, any decent software engineer knew Assembly, and today almost no decent developer knows it because Assembly has long been superseded by technical progress. What engineers “need” to know these days is different from the ‘90s and that process continues with AI, changing the parts of the craft that are essential for devs. We grumble about this but that won’t change anything by itself. 3. There’s a “Dracula Effect” where AI-augmented work drains engineers faster than traditional work. This is because AI automates the easy tasks, meaning that engineers are stuck doing high-intensity thinking all day. Steve says you may only get three daily productive hours at max speed, but during that time, you could produce 100x more output than before.

Gergely Orosz

41,987 görüntüleme • 5 ay önce

OpenClaw - the agentic software spreading like wildfire - was built on top of Pi, a minimalist, self-modifying agent. I sat down with Pi's creator, Mario Zechner and longtime Pi user (+ the creator of Flask) Armin Ronacher ⇌ to talk Pi, and their (very grounded!) takes on building with AI. Timestamps: 00:00 Intro 07:30 How Mario, Armin, and Peter Steinberger met 15:15 How 30 dev teams use AI agents: learnings 21:50 The importance of judgment 24:26 Challenges when non-engineers write code 28:30 Downsides of over-automation 32:18 Pi 48:09 OpenClaw + Pi 50:54 “Clankers” 57:32 Open source and AI 1:00:22 Complexity as the enemy 1:02:50 Building an AI-native startup 1:11:52 “Slow the F down” 1:16:40 MCPs vs. CLI 1:25:03 Predictions and staying up to date • YouTube: • Spotify: • Apple: Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar — The makers of SonarQube, the industry standard for code verification and automated code review. Try it out for yourself. • WorkOS – WorkOS gives you APIs to ship enterprise features – SSO, directory sync, RBAC, audit logs – in days, not months. Visit learn more. --- Three parts I found especially interesting in this discussion: 1. New trend: AI makes it harder for senior engineers to reject pointless complexity. Historically, senior engineers kept software complexity at bay simply by saying “no” a lot. But Armin observes that these days, more junior engineers and product managers deploy agent-scripted counterarguments when a senior colleague kicks an idea to the curb. This makes decision-making exhausting, and more bad ideas make it into production as a result. 2. It should be MUCH easier to build specialized tools for specific tasks. Different projects need different harness types because, as Mario points out, the same hammer is not ideal for every single construction job. As such, Pi is built with the goal of allowing the creation of specialized harnesses. It can modify itself so that a user can create the bespoke harness needed for any task. Mario believes it’s a preview of how self-modifiable software might look in the future. 3. Automation bias is one of the biggest risks of working with AI agents. Once devs confirm that an AI agent can produce acceptable code, they start to review its output less often, even though agents can – and do! – produce slop. Mario advises being far more sceptical with agents, and cautions that the quality of their output isn’t guaranteed, however well they performed previously.
1:33:55

OpenClaw - the agentic software spreading like wildfire - was built on top of Pi, a minimalist, self-modifying agent. I sat down with Pi's creator, Mario Zechner and longtime Pi user (+ the creator of Flask) Armin Ronacher ⇌ to talk Pi, and their (very grounded!) takes on building with AI. Timestamps: 00:00 Intro 07:30 How Mario, Armin, and Peter Steinberger met 15:15 How 30 dev teams use AI agents: learnings 21:50 The importance of judgment 24:26 Challenges when non-engineers write code 28:30 Downsides of over-automation 32:18 Pi 48:09 OpenClaw + Pi 50:54 “Clankers” 57:32 Open source and AI 1:00:22 Complexity as the enemy 1:02:50 Building an AI-native startup 1:11:52 “Slow the F down” 1:16:40 MCPs vs. CLI 1:25:03 Predictions and staying up to date • YouTube: • Spotify: • Apple: Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar — The makers of SonarQube, the industry standard for code verification and automated code review. Try it out for yourself. • WorkOS – WorkOS gives you APIs to ship enterprise features – SSO, directory sync, RBAC, audit logs – in days, not months. Visit learn more. --- Three parts I found especially interesting in this discussion: 1. New trend: AI makes it harder for senior engineers to reject pointless complexity. Historically, senior engineers kept software complexity at bay simply by saying “no” a lot. But Armin observes that these days, more junior engineers and product managers deploy agent-scripted counterarguments when a senior colleague kicks an idea to the curb. This makes decision-making exhausting, and more bad ideas make it into production as a result. 2. It should be MUCH easier to build specialized tools for specific tasks. Different projects need different harness types because, as Mario points out, the same hammer is not ideal for every single construction job. As such, Pi is built with the goal of allowing the creation of specialized harnesses. It can modify itself so that a user can create the bespoke harness needed for any task. Mario believes it’s a preview of how self-modifiable software might look in the future. 3. Automation bias is one of the biggest risks of working with AI agents. Once devs confirm that an AI agent can produce acceptable code, they start to review its output less often, even though agents can – and do! – produce slop. Mario advises being far more sceptical with agents, and cautions that the quality of their output isn’t guaranteed, however well they performed previously.

Gergely Orosz

172,822 görüntüleme • 3 ay önce

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."
2:04

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,011 görüntüleme • 2 ay önce

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 görüntüleme • 6 ay önce

The end of coding? *Epic* conversation with Guillermo Rauch of Vercel on vibe coding, MCP, agents and building products in the AI era. (00:00) - Intro: Guillermo's Story (02:08) - What is v0 and Why Did It Take Off So Fast? (04:10) - Building a hit product with < people (07:51) - Cursor, Replit, etc: v0 vs Other AI Coding Tools (10:35) - Everyone can cook - What is Vibe Coding? (17:05) - Is v0 Just Frontend? Moving Toward Full Stack 19:40 - How to Become a Great Vibe Coder (23:35) - A GUI for AI: The Future of Interfaces (29:46) - Developer Love vs Agent Love (33:41) - The Importance of Taste in the AI Era (39:10) - MCP: The Protocol for AI-to-AI Communication (43:11) - Security and the Risks of Agentic Web (45:25) - Are Enterprises Ready for the Agentic Future? (49:42) - Building a Data Flywheel (56:06) - The Vercel AI Cloud: From Pixels to Tokens (1:10:14) - Adapting to a Non-Developer Persona (1:13:47) - Retention, Margins, and the Business of AI (1:16:51) - The Secret Behind Vercel Last Year Growth (1:24:15) - The importance of Online Presence (1:30:49) - Everything, Everywhere, All at Once: Keeping your Sanity as a CEO (1:34:59) - Guillermo's Advice to Younger Self
1:45:40

The end of coding? *Epic* conversation with Guillermo Rauch of Vercel on vibe coding, MCP, agents and building products in the AI era. (00:00) - Intro: Guillermo's Story (02:08) - What is v0 and Why Did It Take Off So Fast? (04:10) - Building a hit product with < people (07:51) - Cursor, Replit, etc: v0 vs Other AI Coding Tools (10:35) - Everyone can cook - What is Vibe Coding? (17:05) - Is v0 Just Frontend? Moving Toward Full Stack 19:40 - How to Become a Great Vibe Coder (23:35) - A GUI for AI: The Future of Interfaces (29:46) - Developer Love vs Agent Love (33:41) - The Importance of Taste in the AI Era (39:10) - MCP: The Protocol for AI-to-AI Communication (43:11) - Security and the Risks of Agentic Web (45:25) - Are Enterprises Ready for the Agentic Future? (49:42) - Building a Data Flywheel (56:06) - The Vercel AI Cloud: From Pixels to Tokens (1:10:14) - Adapting to a Non-Developer Persona (1:13:47) - Retention, Margins, and the Business of AI (1:16:51) - The Secret Behind Vercel Last Year Growth (1:24:15) - The importance of Online Presence (1:30:49) - Everything, Everywhere, All at Once: Keeping your Sanity as a CEO (1:34:59) - Guillermo's Advice to Younger Self

Matt Turck

86,153 görüntüleme • 1 yıl önce

In 2025, it was rational to be skeptical about whether AI would change the future of software development. In 2026, it's not, anymore. With Charity Majors: Timestamps: 00:00 Intro 02:56 How Parse led to Honeycomb 06:00 The limits of individual productivity metrics 09:08 How Charity’s perspective on AI has evolved 13:50 Rewriting code vs. editing code 19:20 Production as a stage of development 22:14 Code reviews 26:56 Non-deterministic systems 31:11 Sensible uses of AI 37:41 The two AI camps 44:40 Why AI works so well for building software 49:42 DevOps 55:13 Modern observability 1:00:40 Handling context overload 1:01:56 What’s new in Observability Engineering’s 2nd edition 1:07:45 What effective leadership looks like 1:10:25 Engineering management: what is changing? 1:16:31 Junior engineers 1:18:01 AI fatigue 1:21:39 Book recommendations Brought to you by: • Antithesis — turbocharge testing of your systems by running your whole system under aggressive fault injection. Teams like Jane Street, and the etcd community rely on Antithesis. • Buildkite — the CI platform trusted by OpenAI, Anthropic, Cursor, Meta, Uber, NVIDIA, Airbnb and many more. Engineered to absorb whatever your coding agents throw at the build queue. • WorkOS — make your app and agents Enterprise Ready, with SSO, SCIM, RBAC, and more. 1. The question engineers need to answer: what would it take for you to be fully comfortable shipping code you have not read? Charity believes it is a “when” and not an “if” that professional software engineers will ship code they never looked at – and thus do not understand – to production. Engineering is building the systems that validate this code, and allow shipping with full confidence. 2. AI could have the software industry go through the “pets” to “cattle” change that compute infra went through in the 2010s. Up to now, writing software from scratch was far more expensive than editing existing software. But now, generating hundreds of variants of a function can be done faster than how long it would take you to hand-write it once. Charity believes that we might be at the beginning of the transition from “pets” to “cattle” that happened at the hardware infrastructure layer. Before the 2010s, configuring and repairing individual servers was commonly done. But with tools like Terraform and Kubernetes, individual servers having issues are no longer fixed up: they are re-created instead. Charity thinks the same might happen with code, sooner rather than later. When there’s an issue with the code, generate new code that solves it, and is verifyably correct.​ 3. Non-deterministic systems require more engineering discipline versus before. With code written by AI, we’re reducing the trust in the code (because we no longer wrote it), so we need to increase trust at the other part of the development process. Specifically, at validation: with things like tests, evals, and conformance testing.
1:26:22

In 2025, it was rational to be skeptical about whether AI would change the future of software development. In 2026, it's not, anymore. With Charity Majors: Timestamps: 00:00 Intro 02:56 How Parse led to Honeycomb 06:00 The limits of individual productivity metrics 09:08 How Charity’s perspective on AI has evolved 13:50 Rewriting code vs. editing code 19:20 Production as a stage of development 22:14 Code reviews 26:56 Non-deterministic systems 31:11 Sensible uses of AI 37:41 The two AI camps 44:40 Why AI works so well for building software 49:42 DevOps 55:13 Modern observability 1:00:40 Handling context overload 1:01:56 What’s new in Observability Engineering’s 2nd edition 1:07:45 What effective leadership looks like 1:10:25 Engineering management: what is changing? 1:16:31 Junior engineers 1:18:01 AI fatigue 1:21:39 Book recommendations Brought to you by: • Antithesis — turbocharge testing of your systems by running your whole system under aggressive fault injection. Teams like Jane Street, and the etcd community rely on Antithesis. • Buildkite — the CI platform trusted by OpenAI, Anthropic, Cursor, Meta, Uber, NVIDIA, Airbnb and many more. Engineered to absorb whatever your coding agents throw at the build queue. • WorkOS — make your app and agents Enterprise Ready, with SSO, SCIM, RBAC, and more. 1. The question engineers need to answer: what would it take for you to be fully comfortable shipping code you have not read? Charity believes it is a “when” and not an “if” that professional software engineers will ship code they never looked at – and thus do not understand – to production. Engineering is building the systems that validate this code, and allow shipping with full confidence. 2. AI could have the software industry go through the “pets” to “cattle” change that compute infra went through in the 2010s. Up to now, writing software from scratch was far more expensive than editing existing software. But now, generating hundreds of variants of a function can be done faster than how long it would take you to hand-write it once. Charity believes that we might be at the beginning of the transition from “pets” to “cattle” that happened at the hardware infrastructure layer. Before the 2010s, configuring and repairing individual servers was commonly done. But with tools like Terraform and Kubernetes, individual servers having issues are no longer fixed up: they are re-created instead. Charity thinks the same might happen with code, sooner rather than later. When there’s an issue with the code, generate new code that solves it, and is verifyably correct.​ 3. Non-deterministic systems require more engineering discipline versus before. With code written by AI, we’re reducing the trust in the code (because we no longer wrote it), so we need to increase trust at the other part of the development process. Specifically, at validation: with things like tests, evals, and conformance testing.

Gergely Orosz

26,623 görüntüleme • 3 gün önce

Sonnet 4.5 & the AI Plateau Myth — epic conversation with Sholto Douglas of Anthropic 0:00 - Intro 1:09 - What's Behind The Rapid Pace of AI Releases at Anthropic 2:49 - Opus, Sonnet, and Haiku Model Tiers 4:14 - Sholto's Story: From Australian Fencer to AI Researcher 12:01 - The YouTube Effect: Mastery Through Observation 16:16 - Breaking Into AI Research Without Traditional Academic Signals 18:29 - DeepMind, Gemini, and Building Inference Stacks 23:05 - Why Anthropic? Culture and Mission Differences Amongst AI Research Labs 25:08 - What Is "Taste" in AI Research? 31:46 - This Week's Big Launch: Sonnet 4.5, Best Coding Model in the World 36:40 - From 7 Hours to 30 Hours: The Long-Running AI Agent Breakthrough 38:41 - How AI Agents Self-Correct and Maintain Coherence 43:13 - The Role of Memory in Extended Coding Sessions 47:42 - Pre-Training vs. RL: Textbooks vs. Worked Problems 52:11 - Test-Time Compute & Reinforcement Learning 55:55 - Why RL Finally Started Working on LLMs in 2024 59:38 - The Path to AGI 1:02:05 - Are We Hitting a Plateau in AI? So Many Low Hanging Fruits 1:03:41 - Beyond Coding: GDPVal & Impact Economic Sectors 1:05:47 - Preparing for 10-100x Individual Leverage & The Upcoming Robotics Explosion
1:10:03

Sonnet 4.5 & the AI Plateau Myth — epic conversation with Sholto Douglas of Anthropic 0:00 - Intro 1:09 - What's Behind The Rapid Pace of AI Releases at Anthropic 2:49 - Opus, Sonnet, and Haiku Model Tiers 4:14 - Sholto's Story: From Australian Fencer to AI Researcher 12:01 - The YouTube Effect: Mastery Through Observation 16:16 - Breaking Into AI Research Without Traditional Academic Signals 18:29 - DeepMind, Gemini, and Building Inference Stacks 23:05 - Why Anthropic? Culture and Mission Differences Amongst AI Research Labs 25:08 - What Is "Taste" in AI Research? 31:46 - This Week's Big Launch: Sonnet 4.5, Best Coding Model in the World 36:40 - From 7 Hours to 30 Hours: The Long-Running AI Agent Breakthrough 38:41 - How AI Agents Self-Correct and Maintain Coherence 43:13 - The Role of Memory in Extended Coding Sessions 47:42 - Pre-Training vs. RL: Textbooks vs. Worked Problems 52:11 - Test-Time Compute & Reinforcement Learning 55:55 - Why RL Finally Started Working on LLMs in 2024 59:38 - The Path to AGI 1:02:05 - Are We Hitting a Plateau in AI? So Many Low Hanging Fruits 1:03:41 - Beyond Coding: GDPVal & Impact Economic Sectors 1:05:47 - Preparing for 10-100x Individual Leverage & The Upcoming Robotics Explosion

Matt Turck

93,678 görüntüleme • 10 ay önce

I asked Dan Martell to walk me through every level of making money with AI. He gave me the most simple, practical advice I've ever heard on this subject. Level 1 - Making $0 - $100k Level 2 - Making $1m - $10m Level 3 - Building a $10m++ enterprise. 0:00 Only 5% of the World Has Ever Paid for AI 0:46 The Easiest Thing to Sell With AI Right Now 1:56 The Marcus and Sophie Framework 4:24 Theory of Constraints (Right Problem to Solve) 5:33 What Is the Number One Business Constraint 7:13 How to Leave Your Job and Go All In 8:27 Business Is Simple Find a Problem and Solve It 9:08 Stop Getting Ready to Get Ready 9:33 The Sarah Story One Text and $10K 9:53 Pull Up Your Phone and Message Your Contacts 11:05 Dan's Son Gets His First Client at $800/Month 12:41 Best Employee vs. Best Employer 13:59 What Other Services Can You Sell With AI 14:44 Sales Is Not Talking It's Asking 17:01 What to Do When You Hate Your Business 18:40 Pain and Pleasure Are the Only Two Motivators 19:13 They Haven't Made It a Must Yet 20:29 Make It a Must Not a Nice to Have 21:06 The Jen Story and the Gasping Moment 22:17 How to Find Your First 10 to 15 Clients 28:38 The Personal Brand Play 33:06 Vision Is What AI Cannot Do 34:55 Hard for Computers Easy for Humans 36:13 Level 2 Making Your First Million With AI 37:18 The Replacement Ladder Framework 37:39 Admin First Then Delivery Then Marketing 39:09 Why Marketing Is the Biggest AI Category 39:32 Why You Should Keep Sales for Yourself 40:00 Level 5 Leadership and AI Agents 41:41 What a Fully AI Systems Business Looks Like 43:13 The Gym Owner With Three Locations 46:16 Shutting Down the Company for Two Days 46:37 Teaching the Whole Team to Code in Claude 49:28 Wayne the 62 Year Old Who Made $12K a Month 52:38 I Only Share What Actually Works 53:21 Whisper Flow and Talking to Your AI 56:41 Claude Chat Claude Coworker and Claude Code 57:57 The Claude Browser Extension 58:49 Claude Code Is Not Just for Developers 1:00:06 How to Migrate Your AI Memory Across Tools 1:01:08 Level 3 $1M to $10M and the Brand Play 1:02:05 Nobody Buys AI They Buy Trust 1:03:25 Brand Is Association and Association Is Trust 1:05:12 A Million Followers Is $10M in Activated Revenue 1:07:03 How to Keep AI From Becoming Slop 1:07:42 Human in the Loop 1:08:16 The 10 80 10 Rule and Why AI Is Now the 80 1:10:01 The Team FIRED Themselves 1:11:45 Dan's Free AI Curriculum for Your Team
1:13:20

I asked Dan Martell to walk me through every level of making money with AI. He gave me the most simple, practical advice I've ever heard on this subject. Level 1 - Making $0 - $100k Level 2 - Making $1m - $10m Level 3 - Building a $10m++ enterprise. 0:00 Only 5% of the World Has Ever Paid for AI 0:46 The Easiest Thing to Sell With AI Right Now 1:56 The Marcus and Sophie Framework 4:24 Theory of Constraints (Right Problem to Solve) 5:33 What Is the Number One Business Constraint 7:13 How to Leave Your Job and Go All In 8:27 Business Is Simple Find a Problem and Solve It 9:08 Stop Getting Ready to Get Ready 9:33 The Sarah Story One Text and $10K 9:53 Pull Up Your Phone and Message Your Contacts 11:05 Dan's Son Gets His First Client at $800/Month 12:41 Best Employee vs. Best Employer 13:59 What Other Services Can You Sell With AI 14:44 Sales Is Not Talking It's Asking 17:01 What to Do When You Hate Your Business 18:40 Pain and Pleasure Are the Only Two Motivators 19:13 They Haven't Made It a Must Yet 20:29 Make It a Must Not a Nice to Have 21:06 The Jen Story and the Gasping Moment 22:17 How to Find Your First 10 to 15 Clients 28:38 The Personal Brand Play 33:06 Vision Is What AI Cannot Do 34:55 Hard for Computers Easy for Humans 36:13 Level 2 Making Your First Million With AI 37:18 The Replacement Ladder Framework 37:39 Admin First Then Delivery Then Marketing 39:09 Why Marketing Is the Biggest AI Category 39:32 Why You Should Keep Sales for Yourself 40:00 Level 5 Leadership and AI Agents 41:41 What a Fully AI Systems Business Looks Like 43:13 The Gym Owner With Three Locations 46:16 Shutting Down the Company for Two Days 46:37 Teaching the Whole Team to Code in Claude 49:28 Wayne the 62 Year Old Who Made $12K a Month 52:38 I Only Share What Actually Works 53:21 Whisper Flow and Talking to Your AI 56:41 Claude Chat Claude Coworker and Claude Code 57:57 The Claude Browser Extension 58:49 Claude Code Is Not Just for Developers 1:00:06 How to Migrate Your AI Memory Across Tools 1:01:08 Level 3 $1M to $10M and the Brand Play 1:02:05 Nobody Buys AI They Buy Trust 1:03:25 Brand Is Association and Association Is Trust 1:05:12 A Million Followers Is $10M in Activated Revenue 1:07:03 How to Keep AI From Becoming Slop 1:07:42 Human in the Loop 1:08:16 The 10 80 10 Rule and Why AI Is Now the 80 1:10:01 The Team FIRED Themselves 1:11:45 Dan's Free AI Curriculum for Your Team

Grant

167,546 görüntüleme • 1 ay önce

🎧🍌 New The Peel with Ankur Goyal Ankur is the Founder and CEO of @braintrustdata, the end to end developer platform for building the world's best AI products. Their customers include companies like Instacart, Zapier, Notion, Airtable, Replit, and more. We hit on the importance of LLM evals, advice for building AI products, why the best companies have two AI product roadmaps, how he hates meetings, and all his non-conventional advice for founders. Watch below or links in the replies! Timestamps: 04:04 Why everyone’s now an AI company 06:03 Reasons LLM evals are so important 09:19 Replacing vibe checks with Braintrust 10:37 Making OpenAI’s protocols the standard 11:27 Why the best companies have two AI roadmaps 13:06 Build your product so each LLM release makes it better 14:54 Predicting AGI is impossible 15:54 Why people who work with LLMs aren’t worried about AI safety 16:52 The best developers are all-in on co-pilots 18:11 How AI is changing software development 21:09 Combining IDE, CI/DC, and observability in one product 27:18 Are models more like CPU’s or relational databases? 30:14 How to pick an LLM 33:00 Advice for staying on top of new AI developments 34:30 Why tool calling is so important 38:02 Advice for young software engineers 40:25 Learning to code doing linear algebra homework 42:36 Lack of purpose interning in big tech 44:07 Working at MemSQL learning to be a founder 47:52 How to get a job at a startup 50:43 Building his first startups product on an flight 52:39 Three lessons from his first failed startup 54:46 Don’t delegate what you’re good at 55:46 Why you should be careful listening to VCs advice 57:34 Tactics for successful delegation 59:36 Why Ankur hates meetings 1:02:42 The importance of self-service in unlocking certain customer segments 1:05:14 How Braintrust got started 1:07:45 Advice on picking your target customers 1:10:35 How Braintrust hires with work trials 1:15:21 Balancing security with a modern UI 1:17:49 Why it’s hard to sell non-AI products right now 1:19:21 Advice for selling to large enterprises 1:23:10 Ankur’s favorite AI products
1:27:03

🎧🍌 New The Peel with Ankur Goyal Ankur is the Founder and CEO of @braintrustdata, the end to end developer platform for building the world's best AI products. Their customers include companies like Instacart, Zapier, Notion, Airtable, Replit, and more. We hit on the importance of LLM evals, advice for building AI products, why the best companies have two AI product roadmaps, how he hates meetings, and all his non-conventional advice for founders. Watch below or links in the replies! Timestamps: 04:04 Why everyone’s now an AI company 06:03 Reasons LLM evals are so important 09:19 Replacing vibe checks with Braintrust 10:37 Making OpenAI’s protocols the standard 11:27 Why the best companies have two AI roadmaps 13:06 Build your product so each LLM release makes it better 14:54 Predicting AGI is impossible 15:54 Why people who work with LLMs aren’t worried about AI safety 16:52 The best developers are all-in on co-pilots 18:11 How AI is changing software development 21:09 Combining IDE, CI/DC, and observability in one product 27:18 Are models more like CPU’s or relational databases? 30:14 How to pick an LLM 33:00 Advice for staying on top of new AI developments 34:30 Why tool calling is so important 38:02 Advice for young software engineers 40:25 Learning to code doing linear algebra homework 42:36 Lack of purpose interning in big tech 44:07 Working at MemSQL learning to be a founder 47:52 How to get a job at a startup 50:43 Building his first startups product on an flight 52:39 Three lessons from his first failed startup 54:46 Don’t delegate what you’re good at 55:46 Why you should be careful listening to VCs advice 57:34 Tactics for successful delegation 59:36 Why Ankur hates meetings 1:02:42 The importance of self-service in unlocking certain customer segments 1:05:14 How Braintrust got started 1:07:45 Advice on picking your target customers 1:10:35 How Braintrust hires with work trials 1:15:21 Balancing security with a modern UI 1:17:49 Why it’s hard to sell non-AI products right now 1:19:21 Advice for selling to large enterprises 1:23:10 Ankur’s favorite AI products

Turner Novak 🍌🧢

44,280 görüntüleme • 2 yıl önce

Nat Eliason’s (Nat Eliason) career arc is borderline absurd—but it works. He’ll spot a new tool or trend, master it, build a business around it, and move on. Nat’s pulled it off with the note-taking wave ($600k in sales from a Roam Research course), real estate (6x return flipping property in Austin), and crypto (published his insider story with Random House). Now it’s AI: he’s running a viral course on building apps with AI—$200k in pre-sales in just a week, 800 students and counting. I’ve known Nat for a long time and I think he has a great sense for where the puck is headed. He was one of the first guests I had on the podcast and I was delighted to have him on again. Here are a few takeaways from our conversation: - Coding with AI has become orders of magnitude easier for non-technical people over the last 2 years—Nat rarely has to help students fix bugs; they troubleshoot in Cursor on their own. - AI coding assistants are creating new behaviours in programming, like using a speech-to-text model to talk to an agent and having it write code for you. - The traditional learning curve of coding is flattening because AI tools let beginners build and iterate in faster feedback loops. - AI has given Nat leverage in spades—it increases his ability to be a creator while also building a robust business with as few people to manage as possible. He demos an AI book editor he coded for his sci-fi novel. - In the age of AI, software is becoming content and the barriers to create are lower than ever—but custom software for everything isn’t the answer. Nat’s model is that personalized tools make sense for that one thing you care the most about. - Nat believes that the future of writing with AI is a Cursor-style interface with a model that’s trained on your style and voice. This episode is a must-watch for writers, creators, and anyone interested in the future of product building. Watch below! Timestamps: Introduction: 00:01:45 The origins of Nat’s viral course on building apps with AI: 00:11:45 How coding with AI has evolved over the last two years: 00:18:46 Nat creates an app using Composer, Cursor’s AI assistant: 00:22:22 Tactical tips for coding with Cursor: 00:26:06 How coding with AI is creating new behaviours in programming: 00:29:06 What excites Nat the most about the future of AI: 00:32:41 A demo of Hubbard, the AI editor Nat built for his science fiction writing: 00:38:58 When does it makes sense to build custom software: 00:44:52 Nat’s take on the future of writing with AI: 00:49:18
1:00:52

Nat Eliason’s (Nat Eliason) career arc is borderline absurd—but it works. He’ll spot a new tool or trend, master it, build a business around it, and move on. Nat’s pulled it off with the note-taking wave ($600k in sales from a Roam Research course), real estate (6x return flipping property in Austin), and crypto (published his insider story with Random House). Now it’s AI: he’s running a viral course on building apps with AI—$200k in pre-sales in just a week, 800 students and counting. I’ve known Nat for a long time and I think he has a great sense for where the puck is headed. He was one of the first guests I had on the podcast and I was delighted to have him on again. Here are a few takeaways from our conversation: - Coding with AI has become orders of magnitude easier for non-technical people over the last 2 years—Nat rarely has to help students fix bugs; they troubleshoot in Cursor on their own. - AI coding assistants are creating new behaviours in programming, like using a speech-to-text model to talk to an agent and having it write code for you. - The traditional learning curve of coding is flattening because AI tools let beginners build and iterate in faster feedback loops. - AI has given Nat leverage in spades—it increases his ability to be a creator while also building a robust business with as few people to manage as possible. He demos an AI book editor he coded for his sci-fi novel. - In the age of AI, software is becoming content and the barriers to create are lower than ever—but custom software for everything isn’t the answer. Nat’s model is that personalized tools make sense for that one thing you care the most about. - Nat believes that the future of writing with AI is a Cursor-style interface with a model that’s trained on your style and voice. This episode is a must-watch for writers, creators, and anyone interested in the future of product building. Watch below! Timestamps: Introduction: 00:01:45 The origins of Nat’s viral course on building apps with AI: 00:11:45 How coding with AI has evolved over the last two years: 00:18:46 Nat creates an app using Composer, Cursor’s AI assistant: 00:22:22 Tactical tips for coding with Cursor: 00:26:06 How coding with AI is creating new behaviours in programming: 00:29:06 What excites Nat the most about the future of AI: 00:32:41 A demo of Hubbard, the AI editor Nat built for his science fiction writing: 00:38:58 When does it makes sense to build custom software: 00:44:52 Nat’s take on the future of writing with AI: 00:49:18

Dan Shipper 📧

27,207 görüntüleme • 1 yıl önce

My conversation with Jesse Zhang Decagon is building a customer service agent with AI, with plans for much more than that. It’s one of the more successful early AI applications, with tons of lessons for the rest of the market. I love how Jesse developed which problem to solve first, a set of lessons applicable to all entrepreneurs Enjoy Timestamps: 0:00 Intro 2:00 Competing in the AI Era 11:35 Finding Product-Market Fit 14:25 Anatomy of a Great Customer Interview 17:37 Everyone’s Wrong Until You Talk to Customers 19:25 AI Agents Replacing Human Labor 21:55 Why Customer Service 23:30 Coding vs. Customer Service 35:44 The Future of Voice and the Human UI 38:54 Why Voice-to-Voice Is So Hard 43:18 Learning from Customer Data 44:36 How CEOs Should Think About AI 47:06 The ROI of Coding and Productivity Tools 48:20 Every Brand Will Talk to You Through AI 56:00 Recruiting, Capital, and Demand 1:00:42 Investor Frenzy 1:22:17 The Long-Term Vision for Decagon 1:25:05 Kindest Thing
1:26:12

My conversation with Jesse Zhang Decagon is building a customer service agent with AI, with plans for much more than that. It’s one of the more successful early AI applications, with tons of lessons for the rest of the market. I love how Jesse developed which problem to solve first, a set of lessons applicable to all entrepreneurs Enjoy Timestamps: 0:00 Intro 2:00 Competing in the AI Era 11:35 Finding Product-Market Fit 14:25 Anatomy of a Great Customer Interview 17:37 Everyone’s Wrong Until You Talk to Customers 19:25 AI Agents Replacing Human Labor 21:55 Why Customer Service 23:30 Coding vs. Customer Service 35:44 The Future of Voice and the Human UI 38:54 Why Voice-to-Voice Is So Hard 43:18 Learning from Customer Data 44:36 How CEOs Should Think About AI 47:06 The ROI of Coding and Productivity Tools 48:20 Every Brand Will Talk to You Through AI 56:00 Recruiting, Capital, and Demand 1:00:42 Investor Frenzy 1:22:17 The Long-Term Vision for Decagon 1:25:05 Kindest Thing

Patrick OShaughnessy

49,418 görüntüleme • 10 ay önce

Why did Uber build thousands of microservices? No better person to answer than Uber's first CTO, Thuan Pham. Timestamps: 00:00 Intro 05:32 Getting into tech 16:09 The dot-com bust 20:42 VMware 26:29 Getting hired by Travis at Uber 33:22 Early days at Uber and scaling challenges 40:57 Uber’s China launch 47:12 The platform and program split 50:26 From monolith to microservices 53:38 Internal tools at Uber 57:05 Helix: Uber’s mobile app rewrite 59:55 Thuan’s email about naming 1:02:03 Org structure changes under 1:06:34 Thuan’s work philosophy 1:12:23 The “three tours of duty” at Uber 1:15:37 Why Thuan left Uber 1:17:34 Coupang and Nubank 1:21:59 Faire 1:25:31 How Faire uses AI 1:28:24 AI’s impact on software engineering 1:31:09 The role of the CTO 1:35:13 Career advice Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • WorkOS – Everything you need to make your app enterprise ready. • Sonar – The makers of SonarQube, the industry standard for automated code review. Check out SonarQube Advanced Security: Three interesting parts from this conversation: 1. The program/platform split came before microservices. The concept of cross-functional “program” teams and dedicated “platform” teams became necessary because an org split across backend, frontend and mobile engineers slowed down in execution speed when Uber grew to around 100 engineers. Every feature required negotiating bandwidth across the mobile, backend, and dispatch teams. Thuan, Travis Kalanick, and Jeff Holden literally used color-coded sticky notes with people’s names to reorganize into self-sufficient teams. We cover more about this split in this The Pragmatic Engineer deepdive, The Platform and Program split at Uber: 2. Expect multiple rewrites during hypergrowth. The right architecture depends on how fast a product and company are growing. At Uber, repeated rewrites were common because each one “bought” another window of survival for the company. Thuan’s recommendation is to understand that a rewrite simply means a company is outrunning its existing architecture: this is not necessarily a bad thing! 3. Uber is the only major company that had a “Senior 1” and “Senior 2” level – and Thuan is unapologetic. Thuan introduced the Senior 1 (L5A) and Senior 2 (L5B) levels because the jump from senior (L5) to Staff (L6) became very big, and larger than between previous levels. One problem this split level created was that Uber’s L5B was akin to Google’s and Facebook’s L6/E6. Thuan resisted the title inflation of just renaming L5B to ‘Staff’.
1:39:34

Why did Uber build thousands of microservices? No better person to answer than Uber's first CTO, Thuan Pham. Timestamps: 00:00 Intro 05:32 Getting into tech 16:09 The dot-com bust 20:42 VMware 26:29 Getting hired by Travis at Uber 33:22 Early days at Uber and scaling challenges 40:57 Uber’s China launch 47:12 The platform and program split 50:26 From monolith to microservices 53:38 Internal tools at Uber 57:05 Helix: Uber’s mobile app rewrite 59:55 Thuan’s email about naming 1:02:03 Org structure changes under 1:06:34 Thuan’s work philosophy 1:12:23 The “three tours of duty” at Uber 1:15:37 Why Thuan left Uber 1:17:34 Coupang and Nubank 1:21:59 Faire 1:25:31 How Faire uses AI 1:28:24 AI’s impact on software engineering 1:31:09 The role of the CTO 1:35:13 Career advice Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • WorkOS – Everything you need to make your app enterprise ready. • Sonar – The makers of SonarQube, the industry standard for automated code review. Check out SonarQube Advanced Security: Three interesting parts from this conversation: 1. The program/platform split came before microservices. The concept of cross-functional “program” teams and dedicated “platform” teams became necessary because an org split across backend, frontend and mobile engineers slowed down in execution speed when Uber grew to around 100 engineers. Every feature required negotiating bandwidth across the mobile, backend, and dispatch teams. Thuan, Travis Kalanick, and Jeff Holden literally used color-coded sticky notes with people’s names to reorganize into self-sufficient teams. We cover more about this split in this The Pragmatic Engineer deepdive, The Platform and Program split at Uber: 2. Expect multiple rewrites during hypergrowth. The right architecture depends on how fast a product and company are growing. At Uber, repeated rewrites were common because each one “bought” another window of survival for the company. Thuan’s recommendation is to understand that a rewrite simply means a company is outrunning its existing architecture: this is not necessarily a bad thing! 3. Uber is the only major company that had a “Senior 1” and “Senior 2” level – and Thuan is unapologetic. Thuan introduced the Senior 1 (L5A) and Senior 2 (L5B) levels because the jump from senior (L5) to Staff (L6) became very big, and larger than between previous levels. One problem this split level created was that Uber’s L5B was akin to Google’s and Facebook’s L6/E6. Thuan resisted the title inflation of just renaming L5B to ‘Staff’.

Gergely Orosz

69,369 görüntüleme • 4 ay önce

How have the fundamentals of building large, distributed software systems changed the last decade? A conversation with Martin Kleppmann (author of Designing Data-Intensive Applications) - given that the second, updated edition of the book was just released. Timestamps: 00:00 Early career 05:46 Building Rapportive 10:47 Working at LinkedIn 14:09 Writing Designing Data-Intensive Applications 23:00 Reliability, scalability, and repeatability 26:24 DDIA: the second edition 30:50 Tradeoffs of using cloud services 39:02 How the cloud changed scaling 42:53 The trouble with distributed systems 49:02 Ethics for software engineers 52:45 Formal verification 1:00:12 Academia vs. industry 1:03:50 Local-first software 1:09:50 Computer science education 1:18:32 Martin’s current research and advice Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for code verification and automated code review. Check out Sonar's new architecture management capabilities that ensure both humans and AI agents respect your system’s blueprint. • WorkOS – Ship enterprise features – SSO, directory sync, RBAC, audit logs – in days, not months. Three things worth considering, as discussed with Martin, in this episode: 1. Multi-region and multi-cloud are risk/cost trade-offs, not best practices. Martin does not believe that there is a “best practice” in deciding whether to go multi-region or multi-cloud. This decision is a tradeoff between risk and costs. It’s a business decision to be made. Designing Data-Intensive Applications gives engineers the vocabulary to articulate the tradeoffs, not to dictate answers. 2. Replication for fault tolerance is more relevant for most engineers these days than sharding. Though the book has a full chapter on sharding, Martin said that the cloud has reduced the need for manual sharding for the majority of teams. This is also because machines are increasingly bigger, and more workloads fit on a single machine. Sharding across machines is increasingly a specialist concern; replication for fault tolerance, however, is still relevant at every scale. 3. Knowing system internals as a superpower for application developers. Martin maintains that Designing Data-Intensive Applications is not a book for people who build databases or even infrastructure, but it’s helpful for application developers to develop an intuition for making good design decisions and debugging performance issues we will eventually encounter.
1:25:48

How have the fundamentals of building large, distributed software systems changed the last decade? A conversation with Martin Kleppmann (author of Designing Data-Intensive Applications) - given that the second, updated edition of the book was just released. Timestamps: 00:00 Early career 05:46 Building Rapportive 10:47 Working at LinkedIn 14:09 Writing Designing Data-Intensive Applications 23:00 Reliability, scalability, and repeatability 26:24 DDIA: the second edition 30:50 Tradeoffs of using cloud services 39:02 How the cloud changed scaling 42:53 The trouble with distributed systems 49:02 Ethics for software engineers 52:45 Formal verification 1:00:12 Academia vs. industry 1:03:50 Local-first software 1:09:50 Computer science education 1:18:32 Martin’s current research and advice Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for code verification and automated code review. Check out Sonar's new architecture management capabilities that ensure both humans and AI agents respect your system’s blueprint. • WorkOS – Ship enterprise features – SSO, directory sync, RBAC, audit logs – in days, not months. Three things worth considering, as discussed with Martin, in this episode: 1. Multi-region and multi-cloud are risk/cost trade-offs, not best practices. Martin does not believe that there is a “best practice” in deciding whether to go multi-region or multi-cloud. This decision is a tradeoff between risk and costs. It’s a business decision to be made. Designing Data-Intensive Applications gives engineers the vocabulary to articulate the tradeoffs, not to dictate answers. 2. Replication for fault tolerance is more relevant for most engineers these days than sharding. Though the book has a full chapter on sharding, Martin said that the cloud has reduced the need for manual sharding for the majority of teams. This is also because machines are increasingly bigger, and more workloads fit on a single machine. Sharding across machines is increasingly a specialist concern; replication for fault tolerance, however, is still relevant at every scale. 3. Knowing system internals as a superpower for application developers. Martin maintains that Designing Data-Intensive Applications is not a book for people who build databases or even infrastructure, but it’s helpful for application developers to develop an intuition for making good design decisions and debugging performance issues we will eventually encounter.

Gergely Orosz

79,406 görüntüleme • 3 ay önce

Claude Code cracked something open for us Every 🧱. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12
1:10:11

Claude Code cracked something open for us Every 🧱. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12

Dan Shipper 📧

57,619 görüntüleme • 9 ay önce

Here’s DHH (Creator of Ruby on Rails & Omarchy, cofounder of 37 Signals) on why using AI agents does not feel like being a Project Manager: “When I was on that Lex interview last summer, I was saying: I don't want to be a project manager for agents because I had the mental model of a project manager of humans, and that's not what I enjoy. I don't want to be that far away from the production. I want to be in the mix. I want to have my hands in the code. What I failed to realise at the time was that running a bunch of agents feels less like being a project manager for agents and more like stepping into this super mech suit, where suddenly I don't just have two arms, I have 12. I can now look at seven screens at the same time, running five keyboards. I'm still the one doing it, even if I'm not typing ‘this’ as a keyword in a program. I have been hyper accelerated as a programmer. It's a different kind of programmer, but it still has the same affinity to aesthetics, at least when I'm producing Ruby code, and I'm able to combine that while being vastly more productive on a bunch of things.”
1:19

Here’s DHH (Creator of Ruby on Rails & Omarchy, cofounder of 37 Signals) on why using AI agents does not feel like being a Project Manager: “When I was on that Lex interview last summer, I was saying: I don't want to be a project manager for agents because I had the mental model of a project manager of humans, and that's not what I enjoy. I don't want to be that far away from the production. I want to be in the mix. I want to have my hands in the code. What I failed to realise at the time was that running a bunch of agents feels less like being a project manager for agents and more like stepping into this super mech suit, where suddenly I don't just have two arms, I have 12. I can now look at seven screens at the same time, running five keyboards. I'm still the one doing it, even if I'm not typing ‘this’ as a keyword in a program. I have been hyper accelerated as a programmer. It's a different kind of programmer, but it still has the same affinity to aesthetics, at least when I'm producing Ruby code, and I'm able to combine that while being vastly more productive on a bunch of things.”

The Pragmatic Engineer

29,308 görüntüleme • 4 ay önce