Загрузка видео...

Не удалось загрузить видео

На главную

What can us, engineers else learn from designers and design engineers? Turns out there’s lots, based on talking with one of the best design engineers in the industry, Maggie Appleton. Timestamps: 00:00 Intro 03:24 From anthropology to tech 10:18 What does a designer do? 18:23 How Maggie works 24:55...

GergelyOrosz's profile picture

Gergely Orosz

357,908 subscribers

64,127 просмотров • 2 дней назад •via X (Twitter)

ОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 11

Фото профиля Gergely Orosz
Gergely Orosz2 дней назад

Also watch / listen at: • YouTube: • Spotify: • Apple: And a super relevant tactic from Maggie: she regularly builds her personal Figma called “Jigs,” which is also the name of a woodworking device that helps with a specific job. She regularly asks a coding agent to build a prototype that has sliders and color pickers so she can tweak it in realtime, like having a personal Figma! Eg here's one jig she created:

Фото профиля Marco Hefti
Marco Hefti2 дней назад

The amount of cognitive load caused by interrupting someones daily workflow is so true There's so many things I'd like to change in my software that make it not feel like every other app, but then I'm like.. standards exist for a reason and this is what people are used to 😅 So it really is a balancing act of taking established principles and tweaking them just a little bit at a time It also reminds me of every time theres a redesign everyone complains, but after a few weeks no one talks about it anymore because everyone has already gotten used to it!

Фото профиля Viber · fireply.ai
Viber · fireply.ai2 дней назад

@Mappletons one dev twenty four agents zero alignment sounds like my weekend except i'm the only agent and i still lose track

Фото профиля Deep
Deep2 дней назад

@Mappletons i steal two things from designers: clear naming and empty states. my agent demos got easier to explain once the buttons said what happens next.

Фото профиля Ash Designs
Ash Designs2 дней назад

@Mappletons The Craft and AI tells chapter is the one I'm jumping to first. Shipping is cheap now, so the small tells are what separate a product from a template...

Фото профиля Ricci Research
Ricci Research2 дней назад

@Mappletons "Capability gaslighting" deserves its own episode, and the woodworking chapter might be the secret thesis: wood is the one material with no Cmd+Z, which is exactly the constraint two dozen agents will never learn.

Фото профиля Soliman
Soliman2 дней назад

@Mappletons One person steering many agents with no shared picture of what each one is allowed to change is what Zero Alignment looks like in practice.

Фото профиля Gibson Han
Gibson Han2 дней назад

@Mappletons We are going back to wireframing on pen and paper hahaha

Фото профиля Crushed Between
Crushed Between2 дней назад

@Mappletons The designers on my team showed up with a working screen. We showed up with an estimate.

Фото профиля Simon Späti 🏔️
Simon Späti 🏔️2 дней назад

@Mappletons I'm looking forward to that. I love the work Maggie did and is doing on second brain and web community.

Фото профиля Lorenzo Price
Lorenzo Price2 дней назад

@Mappletons The Figma timestamp plus GitHub Next's two-dozen-agent alignment problem is an excellent syllabus for engineers.

Похожие видео

If you use Codex, Tibo needs no introduction. We talked 100% about Codex (fun fact: he started building it!), and 0% about resets. Timestamps: 00:00 Intro 07:21 Working at Google 12:41 What drew Tibo to OpenAI 15:19 The early days of Codex 18:20 Why Codex was built in Rust 21:15 Why Codex is open source 25:50 Codex plays nice with other models: why? 32:09 How the harness works 36:44 Harness and model improvements 41:19 The SDLC behind Codex 46:39 Code reviews at Codex 52:09 Maintenance and architecture 56:43 How AI tools expand what engineers can do 1:02:30 The Merge: ChatGPT + Codex 1:07:16 How Tibo uses Codex and ChatGPT 1:10:44 Advice for engineers who want to work in AI Brought to you by: • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Entire – Git hosting, rebuilt for the agentic era. Entire hosts your code in-region, and is up to 89x faster than any other competitor. Oh, and to those still reading and wondering about resets: there was one yesterday already 😅
1:14:22

If you use Codex, Tibo needs no introduction. We talked 100% about Codex (fun fact: he started building it!), and 0% about resets. Timestamps: 00:00 Intro 07:21 Working at Google 12:41 What drew Tibo to OpenAI 15:19 The early days of Codex 18:20 Why Codex was built in Rust 21:15 Why Codex is open source 25:50 Codex plays nice with other models: why? 32:09 How the harness works 36:44 Harness and model improvements 41:19 The SDLC behind Codex 46:39 Code reviews at Codex 52:09 Maintenance and architecture 56:43 How AI tools expand what engineers can do 1:02:30 The Merge: ChatGPT + Codex 1:07:16 How Tibo uses Codex and ChatGPT 1:10:44 Advice for engineers who want to work in AI Brought to you by: • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Entire – Git hosting, rebuilt for the agentic era. Entire hosts your code in-region, and is up to 89x faster than any other competitor. Oh, and to those still reading and wondering about resets: there was one yesterday already 😅

Gergely Orosz

80,608 просмотров • 16 дней назад

Pretty incredible how the skills repo by Matt Pocock is only 6 months old, and has more stars than the React one. We had to sit down and talk. Timestamps: 00:00 Intro 05:48 How Matt got into tech 10:14 How Matt got into open source 12:58 Joining Vercel 18:39 Total TypeScript 23:21 AI’s impact on technical education 30:32 Building reusable skills for AI coding agents 40:46 The “smart zone” vs the “dumb zone” 45:02 The wayfinder skill 47:52 Why agents excel at software engineering 50:54 “Leading words” 1:01:10 Learning the fundamentals 1:09:17 Local vs. cloud agents 1:12:36 Planning vs. course-correcting 1:18:13 TDD and agents 1:23:06 Living in the UK 1:24:21 Teaching: the human part 1:28:36 Advice for junior engineers 1:31:07 Gardeners and great engineers 1:34:01 Book recommendation Brought to you by: • turbopuffer – vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Linear – the product development system trusted by 40,000+ teams to plan and ship. Get six months of Linear Business for free: • WorkOS – The fastest AI-native teams have to slow down for the hard problems. WorkOS makes sure auth, for your app and your agents, is never one of them. Thanks for the convo Matt Pocock!
1:36:36

Pretty incredible how the skills repo by Matt Pocock is only 6 months old, and has more stars than the React one. We had to sit down and talk. Timestamps: 00:00 Intro 05:48 How Matt got into tech 10:14 How Matt got into open source 12:58 Joining Vercel 18:39 Total TypeScript 23:21 AI’s impact on technical education 30:32 Building reusable skills for AI coding agents 40:46 The “smart zone” vs the “dumb zone” 45:02 The wayfinder skill 47:52 Why agents excel at software engineering 50:54 “Leading words” 1:01:10 Learning the fundamentals 1:09:17 Local vs. cloud agents 1:12:36 Planning vs. course-correcting 1:18:13 TDD and agents 1:23:06 Living in the UK 1:24:21 Teaching: the human part 1:28:36 Advice for junior engineers 1:31:07 Gardeners and great engineers 1:34:01 Book recommendation Brought to you by: • turbopuffer – vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • Linear – the product development system trusted by 40,000+ teams to plan and ship. Get six months of Linear Business for free: • WorkOS – The fastest AI-native teams have to slow down for the hard problems. WorkOS makes sure auth, for your app and your agents, is never one of them. Thanks for the convo Matt Pocock!

Gergely Orosz

132,099 просмотров • 8 дней назад

Why is the creator of OpenCode pretty skeptical about AI productivity gains, and the hype around AI? A very conversation dax (and lots of truth bombs:) Timestamps: 00:00 Intro 07:03 Dax’s path into tech 09:04 Early startup experience 13:16 Getting involved with open source 16:13 OpenCode 23:17 Anthropic banning OpenCode 30:34 From terminal to GUI 32:34 OpenCode’s business model 36:33 Why inference is profitable 39:11 GPU bottlenecks 40:54 AI hype 45:50 AI spending 48:47 Dax’s memo 55:41 Dax’s skepticism of predictions 58:58 Engineering culture at OpenCode 1:02:38 How building works at OpenCode 1:05:36 Taste and quality 1:11:32 Dax’s work setup 1:12:35 The role of engineers and EMs 1:15:50 Advice for engineers 1:18:12 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 Three interesting thoughts from Dax: 1. No AI-native coding agent company is “winning” by being better with AI. Dax says that none of OpenCode’s competitors are crushing them, and that nobody is using AI so well that others cannot compete. 2. Most software engineers profit from AI as time gained, not increased output — unless you change incentives! Dax says the natural way for software engineers to “cash out” their AI tooling gains is with time savings, by doing the same work as before, but faster. Until compensation and motivation structures change, most teams should expect output to stay flat while engineers go home earlier. There’s nothing wrong with this, but AI vendors sell a different outcome to CFOs: increased output. 3. AI code generation mutes the “guilt” of doing the wrong thing, but this builds up tech debt. Pre-AI, writing a hack felt bad, the second time it felt really bad, and by the third time you’d often just refactor in order to fix up the code. Now, the agent hides the hack, which skews devs’ judgment and results in less tech debt being cleaned up.
1:21:01

Why is the creator of OpenCode pretty skeptical about AI productivity gains, and the hype around AI? A very conversation dax (and lots of truth bombs:) Timestamps: 00:00 Intro 07:03 Dax’s path into tech 09:04 Early startup experience 13:16 Getting involved with open source 16:13 OpenCode 23:17 Anthropic banning OpenCode 30:34 From terminal to GUI 32:34 OpenCode’s business model 36:33 Why inference is profitable 39:11 GPU bottlenecks 40:54 AI hype 45:50 AI spending 48:47 Dax’s memo 55:41 Dax’s skepticism of predictions 58:58 Engineering culture at OpenCode 1:02:38 How building works at OpenCode 1:05:36 Taste and quality 1:11:32 Dax’s work setup 1:12:35 The role of engineers and EMs 1:15:50 Advice for engineers 1:18:12 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 Three interesting thoughts from Dax: 1. No AI-native coding agent company is “winning” by being better with AI. Dax says that none of OpenCode’s competitors are crushing them, and that nobody is using AI so well that others cannot compete. 2. Most software engineers profit from AI as time gained, not increased output — unless you change incentives! Dax says the natural way for software engineers to “cash out” their AI tooling gains is with time savings, by doing the same work as before, but faster. Until compensation and motivation structures change, most teams should expect output to stay flat while engineers go home earlier. There’s nothing wrong with this, but AI vendors sell a different outcome to CFOs: increased output. 3. AI code generation mutes the “guilt” of doing the wrong thing, but this builds up tech debt. Pre-AI, writing a hack felt bad, the second time it felt really bad, and by the third time you’d often just refactor in order to fix up the code. Now, the agent hides the hack, which skews devs’ judgment and results in less tech debt being cleaned up.

Gergely Orosz

232,004 просмотров • 4 месяцев назад

There are few people who have impacted the software engineering industry like Kent Beck 🌻 has. He'd never before told his career story from start to today in one sitting - until now. What a treat. Timestamps: 00:00 Intro 03:47 Human engineers aren’t going away 08:00 Kent's path into tech 13:50 Undergraduate and graduate studies 17:21 Kent’s first programming job 18:54 The rise and fall of Smalltalk 27:04 Working with Ward Cunningham 37:36 Design patterns 44:05 Working at Apple 51:08 CRC Cards 59:29 Testing tools in the language 1:04:22 The C3 project with Martin Fowler 1:09:54 Extreme Programming 1:16:25 Developing TDD 1:25:07 Writing the Agile Manifesto 1:30:00 Agile’s impact 1:32:40 Agile’s downside 1:37:32 The Dotcom Bust 1:44:30 Lessons from working at Facebook 1:59:44 Kent’s ‘Good to Great’ program at Facebook 2:06:07 Soft skills engineers need to learn 2:09:30 AI and the challenges of acceleration 2:15:53 Explore, expand, extract 2:22:33 What Kent is excited about Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable • WorkOS – everything you need to make your app enterprise ready Kent shared so many previously untold stories - like how he was fired from Apple (!!), how he and Ward Cunningham used a thesaurus to find the right words, how the Agile Manifesto came together. My favorite reflection from is this though: The human part is the most important one in software engineering. As Kent explained: “This is the biggest cosmic, practical joke ever. As young people, we were promised: “Okay, here’s this computer and once you’ve completely understand this computer, you’ll be fine. That’s all you need to do.” So I set out the first part of my career just to become the best programmer that I could be because that’s what it would take to be successful. And then you realize: sorry, there’s this whole human side. Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings. And those are exactly the skills that I thought I didn’t need to learn! So I was promised: just understand the computer and you’ll be successful. And then someone went “just kidding, understand people!” And now I was in a position of being ten years behind.”
2:28:43

There are few people who have impacted the software engineering industry like Kent Beck 🌻 has. He'd never before told his career story from start to today in one sitting - until now. What a treat. Timestamps: 00:00 Intro 03:47 Human engineers aren’t going away 08:00 Kent's path into tech 13:50 Undergraduate and graduate studies 17:21 Kent’s first programming job 18:54 The rise and fall of Smalltalk 27:04 Working with Ward Cunningham 37:36 Design patterns 44:05 Working at Apple 51:08 CRC Cards 59:29 Testing tools in the language 1:04:22 The C3 project with Martin Fowler 1:09:54 Extreme Programming 1:16:25 Developing TDD 1:25:07 Writing the Agile Manifesto 1:30:00 Agile’s impact 1:32:40 Agile’s downside 1:37:32 The Dotcom Bust 1:44:30 Lessons from working at Facebook 1:59:44 Kent’s ‘Good to Great’ program at Facebook 2:06:07 Soft skills engineers need to learn 2:09:30 AI and the challenges of acceleration 2:15:53 Explore, expand, extract 2:22:33 What Kent is excited about Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable • WorkOS – everything you need to make your app enterprise ready Kent shared so many previously untold stories - like how he was fired from Apple (!!), how he and Ward Cunningham used a thesaurus to find the right words, how the Agile Manifesto came together. My favorite reflection from is this though: The human part is the most important one in software engineering. As Kent explained: “This is the biggest cosmic, practical joke ever. As young people, we were promised: “Okay, here’s this computer and once you’ve completely understand this computer, you’ll be fine. That’s all you need to do.” So I set out the first part of my career just to become the best programmer that I could be because that’s what it would take to be successful. And then you realize: sorry, there’s this whole human side. Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings. And those are exactly the skills that I thought I didn’t need to learn! So I was promised: just understand the computer and you’ll be successful. And then someone went “just kidding, understand people!” And now I was in a position of being ten years behind.”

Gergely Orosz

26,602 просмотров • 2 месяцев назад

AI isn't just changing the tools designers use. It's changing how they build, ship, and stand out. In this episode of Design Review, Stephen Haney, founder of AI-native design tool Paper, joins YC's Aaron Epstein to demo the agent-first workflow that's making Paper one of the fastest-growing design tools since Figma. Using live redesigns of user-submitted websites as examples, they break down the most common AI design tells, show how to fix them in seconds, and explain why the biggest risk for founders isn't moving too slow, it's shipping something that looks like everyone else. 01:04 - What is Paper and why build it? 03:17 - What makes Paper agent-native 05:11 - Demo: Shaders, image generation, and brand design 11:32 - Design-to-code and the new agent stack 16:48 - Design Review: Legion Health 24:11 - How to avoid AI design slop 28:26 - Design Review: Sytex 32:42 - The biggest tells of AI-generated design 37:39 - Design Review: Moreta 41:11 - Can AI learn taste? 43:56 - How Paper uses agents internally 46:52 - Building a community around Paper 49:15 - Lessons from Steven’s first startup 53:30 - What’s next for design and Paper
56:01

AI isn't just changing the tools designers use. It's changing how they build, ship, and stand out. In this episode of Design Review, Stephen Haney, founder of AI-native design tool Paper, joins YC's Aaron Epstein to demo the agent-first workflow that's making Paper one of the fastest-growing design tools since Figma. Using live redesigns of user-submitted websites as examples, they break down the most common AI design tells, show how to fix them in seconds, and explain why the biggest risk for founders isn't moving too slow, it's shipping something that looks like everyone else. 01:04 - What is Paper and why build it? 03:17 - What makes Paper agent-native 05:11 - Demo: Shaders, image generation, and brand design 11:32 - Design-to-code and the new agent stack 16:48 - Design Review: Legion Health 24:11 - How to avoid AI design slop 28:26 - Design Review: Sytex 32:42 - The biggest tells of AI-generated design 37:39 - Design Review: Moreta 41:11 - Can AI learn taste? 43:56 - How Paper uses agents internally 46:52 - Building a community around Paper 49:15 - Lessons from Steven’s first startup 53:30 - What’s next for design and Paper

Y Combinator

115,134 просмотров • 1 месяц назад

There’s a popular theory that AI will finally make formal verification mainstream because mathematical proof of correctness will be needed when machines write most or all of the code. But will this happen? Hillel Wayne is one of the best people to answer. Timestamps: 00:00 Intro 04:32 The Crossover Project 11:37 What software engineering does better 15:30 What traditional engineering does better 18:17 Formal methods 29:32 TLA+: what it is and demo 36:58 TLA+ at Amazon 38:10 Ways distributed systems break 41:03 Formal methods and systems thinking 46:20 The value of learning math 50:23 What TLA+ is good for and isn’t 52:50 Alloy: a declarative language for software modeling 58:53 Other formal methods tools 1:01:24 Property-based testing 1:05:31 AI and the need for formal verification 1:12:29 Logic for programmers 1:14:35 Hillel’s 2025 prediction on AI’s impact 1:21:30 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • WorkOS – everything you need to make your app enterprise ready. Two things I found especially interesting, talking with Hillel: 1. Amazon used TLA+ to find a bug almost impossible to locate without formal methods. In the paper How AWS uses formal methods, the AWS team shared that they’d found a complicated bug for which the shortest error trace to exhibit was 35 steps (!!). The bug passed unnoticed through extensive design review, code reviews, and testing. AWS concluded they wouldn’t have uncovered it if they’d stuck to conventional testing approaches. 2. Why not use formal verification for everything, then? It’s because specs in the real world are a nightmare to write. Even a simple problem like “find the file in a directory that has the most lines” gets complicated when modeled with formal methods. We would have to answer questions like: ‘do we look at ASCII or UTF-8 new line characters, what about unreadable files, and Symlinks?’ Without formal methods, we can write a simple verification that is right in 99%+ of cases. Formal methods require a lot of extra effort for the less than 1% of exotic use cases!
1:24:52

There’s a popular theory that AI will finally make formal verification mainstream because mathematical proof of correctness will be needed when machines write most or all of the code. But will this happen? Hillel Wayne is one of the best people to answer. Timestamps: 00:00 Intro 04:32 The Crossover Project 11:37 What software engineering does better 15:30 What traditional engineering does better 18:17 Formal methods 29:32 TLA+: what it is and demo 36:58 TLA+ at Amazon 38:10 Ways distributed systems break 41:03 Formal methods and systems thinking 46:20 The value of learning math 50:23 What TLA+ is good for and isn’t 52:50 Alloy: a declarative language for software modeling 58:53 Other formal methods tools 1:01:24 Property-based testing 1:05:31 AI and the need for formal verification 1:12:29 Logic for programmers 1:14:35 Hillel’s 2025 prediction on AI’s impact 1:21:30 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. • WorkOS – everything you need to make your app enterprise ready. Two things I found especially interesting, talking with Hillel: 1. Amazon used TLA+ to find a bug almost impossible to locate without formal methods. In the paper How AWS uses formal methods, the AWS team shared that they’d found a complicated bug for which the shortest error trace to exhibit was 35 steps (!!). The bug passed unnoticed through extensive design review, code reviews, and testing. AWS concluded they wouldn’t have uncovered it if they’d stuck to conventional testing approaches. 2. Why not use formal verification for everything, then? It’s because specs in the real world are a nightmare to write. Even a simple problem like “find the file in a directory that has the most lines” gets complicated when modeled with formal methods. We would have to answer questions like: ‘do we look at ASCII or UTF-8 new line characters, what about unreadable files, and Symlinks?’ Without formal methods, we can write a simple verification that is right in 99%+ of cases. Formal methods require a lot of extra effort for the less than 1% of exotic use cases!

Gergely Orosz

34,759 просмотров • 1 месяц назад

AI isn't just changing the tools designers use. It's changing the way they think, prototype, and build. In this episode of Design Review, YC Head of Design eve joins Aaron Epstein to share the AI-first workflow she uses to design products, websites, and events. Using projects like Paxel, STATE OF THE ART, and YC Startup School as examples, she explains how coding agents are transforming everything from rapid prototyping and branding to design systems, and why the biggest bottleneck is no longer software. It's imagination. 00:00 - Eve's AI-First Design Workflow 01:27 - Why She Designs With Her Voice 03:44 - Paxel: Spotify Wrapped for Coding Sessions 07:13 - Building Tools for Yourself 11:01 - Turning Coding Transcripts Into Feedback 12:53 - The Story Behind SOTA Zine 16:57 - Designing With Context, Not Prompts 21:07 - How to Get Better AI Design Outputs 23:20 - Building an Interactive Map of San Francisco 25:17 - Behind Startup School's Visual Identity 29:59 - The Future of Design
30:54

AI isn't just changing the tools designers use. It's changing the way they think, prototype, and build. In this episode of Design Review, YC Head of Design eve joins Aaron Epstein to share the AI-first workflow she uses to design products, websites, and events. Using projects like Paxel, STATE OF THE ART, and YC Startup School as examples, she explains how coding agents are transforming everything from rapid prototyping and branding to design systems, and why the biggest bottleneck is no longer software. It's imagination. 00:00 - Eve's AI-First Design Workflow 01:27 - Why She Designs With Her Voice 03:44 - Paxel: Spotify Wrapped for Coding Sessions 07:13 - Building Tools for Yourself 11:01 - Turning Coding Transcripts Into Feedback 12:53 - The Story Behind SOTA Zine 16:57 - Designing With Context, Not Prompts 21:07 - How to Get Better AI Design Outputs 23:20 - Building an Interactive Map of San Francisco 25:17 - Behind Startup School's Visual Identity 29:59 - The Future of Design

Y Combinator

103,657 просмотров • 2 месяцев назад

THE LIBRARY OF MINDS: EPISODE 3 - Soleio Cuervo (Soleio) Early designer at Facebook & Dropbox, co-inventor of the Like button, and design-driven investor behind Figma, Perplexity, and Delphi. We discuss: • The untold story of the Facebook Like button • Defining the role of “Product Designer” at Facebook • Building world-class design cultures at scale • Balancing speed vs. excellence in product teams • When intuition fails - and data saves you Plus: Lessons in hybrid designer-engineers, hackathon culture, trust & safety, and how AI is redefining great UX. Bonus: Soleio on utility vs. beauty, system-centric design, and why digital minds might be the next design frontier. (00:00) - Intro (01:00) - Who is Soleio Cuervo (02:00) - Early web days: The origins of product design (04:37) - Inventing the ‘product designer’ role at Facebook (07:43) - Culture of speed, ownership, and building at Facebook (11:45) - Shipping fast: The story of Facebook’s Like button (13:54) - When to persist and when to quit: Loonshots, ‘false fails’, and user onboarding at Facebook (17:49) - Transitioning cultures: From Facebook’s speed to Dropbox’s trust (20:54) - Balancing speed with excellence: Lessons for AI-era startups (22:28) - Is speed or quality a stronger differentiator in today’s tech world? (24:35) - Can design be a moat in the age of AI? (27:35) - Rethinking UX in an AI-native world (29:08) - Why Soleio invested in Delphi: The “Oprahbot” idea and digital minds
33:00

THE LIBRARY OF MINDS: EPISODE 3 - Soleio Cuervo (Soleio) Early designer at Facebook & Dropbox, co-inventor of the Like button, and design-driven investor behind Figma, Perplexity, and Delphi. We discuss: • The untold story of the Facebook Like button • Defining the role of “Product Designer” at Facebook • Building world-class design cultures at scale • Balancing speed vs. excellence in product teams • When intuition fails - and data saves you Plus: Lessons in hybrid designer-engineers, hackathon culture, trust & safety, and how AI is redefining great UX. Bonus: Soleio on utility vs. beauty, system-centric design, and why digital minds might be the next design frontier. (00:00) - Intro (01:00) - Who is Soleio Cuervo (02:00) - Early web days: The origins of product design (04:37) - Inventing the ‘product designer’ role at Facebook (07:43) - Culture of speed, ownership, and building at Facebook (11:45) - Shipping fast: The story of Facebook’s Like button (13:54) - When to persist and when to quit: Loonshots, ‘false fails’, and user onboarding at Facebook (17:49) - Transitioning cultures: From Facebook’s speed to Dropbox’s trust (20:54) - Balancing speed with excellence: Lessons for AI-era startups (22:28) - Is speed or quality a stronger differentiator in today’s tech world? (24:35) - Can design be a moat in the age of AI? (27:35) - Rethinking UX in an AI-native world (29:08) - Why Soleio invested in Delphi: The “Oprahbot” idea and digital minds

Dara

75,367 просмотров • 11 месяцев назад

Once you understand that world events are influenced by supernatural forces, what seems bizarre begins to make sense. Filmmaker Sean Stone on our leaders and the occult. 0:00 Why Do Leaders Commune With the Supernatural? 5:02 Demonology, Rituals, and Demonic Possession 23:57 What Masonry Is and Fallen Angels 29:13 The Book of Enoch, the Nephilim, and Adrenochrome 41:04 Sean’s Phone Calls from Demons 45:28 What Feeds Demons and the Empire of Fear 53:26 Can Nations Make Deals with the Supernatural? 58:49 The Spiritual Economy of Evil 1:02:57 Where Does This Put the United States? 1:06:25 The Pentagon and the Power of Symbolism 1:13:57 The Darkness of Hollywood and Pointless Wars 1:24:53 Social Media’s Design to Inspire Fear and Hate 1:28:26 AI, UFOs, and the War on Terror 1:38:12 Those in Power’s Obsession with Genetics 1:43:40 Why Is This All Happening at Once?
1:49:22

Once you understand that world events are influenced by supernatural forces, what seems bizarre begins to make sense. Filmmaker Sean Stone on our leaders and the occult. 0:00 Why Do Leaders Commune With the Supernatural? 5:02 Demonology, Rituals, and Demonic Possession 23:57 What Masonry Is and Fallen Angels 29:13 The Book of Enoch, the Nephilim, and Adrenochrome 41:04 Sean’s Phone Calls from Demons 45:28 What Feeds Demons and the Empire of Fear 53:26 Can Nations Make Deals with the Supernatural? 58:49 The Spiritual Economy of Evil 1:02:57 Where Does This Put the United States? 1:06:25 The Pentagon and the Power of Symbolism 1:13:57 The Darkness of Hollywood and Pointless Wars 1:24:53 Social Media’s Design to Inspire Fear and Hate 1:28:26 AI, UFOs, and the War on Terror 1:38:12 Those in Power’s Obsession with Genetics 1:43:40 Why Is This All Happening at Once?

Tucker Carlson

1,022,946 просмотров • 4 месяцев назад

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

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

Matt Turck

49,691 просмотров • 4 месяцев назад

NEW: Dylan Field (Dylan Field), CEO of Figma (NYSE: FIG) How to Escape the "Permanent Underclass of Zero Taste" › Why AI prompts only get you the average › Why the market has design backwards Plus, Founders Fund's Mafia & Thiel Fellowship class behind Figma + Anthropic Recorded at Day 0 of Config 2026, San Francisco We Cover: › Vibe Mathing › Elon: Products vs Logos › AI's trust issue › Agents vs Employees › Engineers coding design › American Enterprise > › IQ ≠ Judgment or taste › What actually is a jailbreak? This was SO much fun!!! Can confirm Config-pilled. 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Dylan Field, Co-Founder & CEO at Figma (00:57) Day Zero begins: backstage at Config (01:44) The "Coachella for Design" is real (02:35) Why Dylan started Config back in 2020 (03:47) Why "design is dead" is completely wrong (06:11) How Figma turned engineers into designers (06:54) Inside Config before the crowd arrives (07:55) The Config speakers Dylan can't wait to watch (11:34) Inside the exclusive Pantone Lounge (12:00) The one question every designer gets asked (13:16) Getting killed in every single game of Mafia (15:33) How to escape the permanent underclass of zero taste (19:51) Why execution is cheap but taste is everything (22:25) What actually builds a trusted brand (25:51) How AI agents are rewiring company structure (28:54) The AI safety debate happening right now (31:57) Why deep curiosity is Dylan's secret weapon (34:53) The real lesson from being a Thiel fellow (36:52) Rapid fire: Elad Gil's wildest question (38:04) What people are missing about AI & enterprise software (40:16) Where Figma goes next (41:21) Why Dylan is bullish on SpaceX (42:43) Elon Musk's logo theory (43:26) The mentors who shaped Dylan Field (45:20) Alan Kay, VR, and the future of human-computer interaction
47:33

NEW: Dylan Field (Dylan Field), CEO of Figma (NYSE: FIG) How to Escape the "Permanent Underclass of Zero Taste" › Why AI prompts only get you the average › Why the market has design backwards Plus, Founders Fund's Mafia & Thiel Fellowship class behind Figma + Anthropic Recorded at Day 0 of Config 2026, San Francisco We Cover: › Vibe Mathing › Elon: Products vs Logos › AI's trust issue › Agents vs Employees › Engineers coding design › American Enterprise > › IQ ≠ Judgment or taste › What actually is a jailbreak? This was SO much fun!!! Can confirm Config-pilled. 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Dylan Field, Co-Founder & CEO at Figma (00:57) Day Zero begins: backstage at Config (01:44) The "Coachella for Design" is real (02:35) Why Dylan started Config back in 2020 (03:47) Why "design is dead" is completely wrong (06:11) How Figma turned engineers into designers (06:54) Inside Config before the crowd arrives (07:55) The Config speakers Dylan can't wait to watch (11:34) Inside the exclusive Pantone Lounge (12:00) The one question every designer gets asked (13:16) Getting killed in every single game of Mafia (15:33) How to escape the permanent underclass of zero taste (19:51) Why execution is cheap but taste is everything (22:25) What actually builds a trusted brand (25:51) How AI agents are rewiring company structure (28:54) The AI safety debate happening right now (31:57) Why deep curiosity is Dylan's secret weapon (34:53) The real lesson from being a Thiel fellow (36:52) Rapid fire: Elad Gil's wildest question (38:04) What people are missing about AI & enterprise software (40:16) Where Figma goes next (41:21) Why Dylan is bullish on SpaceX (42:43) Elon Musk's logo theory (43:26) The mentors who shaped Dylan Field (45:20) Alan Kay, VR, and the future of human-computer interaction

Molly O’Shea

430,052 просмотров • 2 месяцев назад

In this episode of Design Review, Aaron Epstein sits down with Jorn van Dijk, the CEO and Co-founder of Framer. Together they unpack the brutal “gray zone” between early revenue and real product-market fit, the pivot that reignited their growth, and how to adapt as AI reshapes how we build and design software. 00:00 - Intro to Jorn van Dijk, the CEO and co-founder of Framer 00:34 - Framer’s Scale: $2B Valuation, 120 People around the globe 01:06 - Jorn’s Design Roots 01:49 - Why Dutch Design Culture Is So Strong 03:43 - Sofa: The Studio That Shaped Jorn (and His Co-Founder) 04:39 - Building Mac Products: Checkout, Versions, Kaleidoscope 06:13 - Apple Design Awards And A Game Changing Email 07:24 - Facebook Acquisition: Why They Wanted Designers 09:27 - Culture Shock: From 15-Person Studio to Facebook Scale 10:27 - Leaving Facebook: Intentionally Learning to Build a Big Company 13:12 - Early Experiments: Bitcoin App, Fashion App, Framer Prototype Tool 18:37 - The Plateau: Why Framer Studio Hit a Ceiling Around $4–5M ARR 23:52 - The Decision: Sell, Quit, or Pivot 25:30 - The Big Insight: People Hate Rebuilding 34:55 - AI + Design: What’s Changing & What Isn’t
44:25

In this episode of Design Review, Aaron Epstein sits down with Jorn van Dijk, the CEO and Co-founder of Framer. Together they unpack the brutal “gray zone” between early revenue and real product-market fit, the pivot that reignited their growth, and how to adapt as AI reshapes how we build and design software. 00:00 - Intro to Jorn van Dijk, the CEO and co-founder of Framer 00:34 - Framer’s Scale: $2B Valuation, 120 People around the globe 01:06 - Jorn’s Design Roots 01:49 - Why Dutch Design Culture Is So Strong 03:43 - Sofa: The Studio That Shaped Jorn (and His Co-Founder) 04:39 - Building Mac Products: Checkout, Versions, Kaleidoscope 06:13 - Apple Design Awards And A Game Changing Email 07:24 - Facebook Acquisition: Why They Wanted Designers 09:27 - Culture Shock: From 15-Person Studio to Facebook Scale 10:27 - Leaving Facebook: Intentionally Learning to Build a Big Company 13:12 - Early Experiments: Bitcoin App, Fashion App, Framer Prototype Tool 18:37 - The Plateau: Why Framer Studio Hit a Ceiling Around $4–5M ARR 23:52 - The Decision: Sell, Quit, or Pivot 25:30 - The Big Insight: People Hate Rebuilding 34:55 - AI + Design: What’s Changing & What Isn’t

Y Combinator

19,897 просмотров • 7 месяцев назад

PGX Ideas with Aravind Srinivas, Co-founder and CEO of Perplexity - What does it mean to be intelligent? Why humans wonder. Why we create. Whether AI understands anything at all or is it merely mimicking intelligence. And the deeper questions that follow from that. We spoke about emergence, India’s competitive culture, China, behaviorism, memory, learning, hardware, and the question of where this all leads. The AI Hindi-dubbed version of this episode is also attached in this thread. Enjoy. Timestamps 00:00 - How did Aravind get into AI? 13:05 - India’s competitive culture 15:05 - Talent problem or system failure? 16:25 - How can India evolve? 17:45 - China’s approach to research 21:02 - What’s cutting-edge in AI today? 25:02 - What creates value in an economy? 28:45 - What is the internet built on? 32:48 - Can AI assist humans? 35:25 - Why do humans wonder? 37:25 - Why do humans create? 40:50 - Does memory still matter? 43:15 - Does curiosity create knowledge? 45:40 - Biological vs artificial intelligence 51:24 - Is curiosity uniquely human? 58:55 - Can AI shape human thinking? 1:05:24 - Do we understand intelligence? 1:10:50 - Meaning beyond behaviorism 1:21:48 - How do kids learn to learn? 1:25:43 - Why is hardware innovation hard? 1:31:19 - Can AI feel? 1:47:35 - Questions for me
1:45:37

PGX Ideas with Aravind Srinivas, Co-founder and CEO of Perplexity - What does it mean to be intelligent? Why humans wonder. Why we create. Whether AI understands anything at all or is it merely mimicking intelligence. And the deeper questions that follow from that. We spoke about emergence, India’s competitive culture, China, behaviorism, memory, learning, hardware, and the question of where this all leads. The AI Hindi-dubbed version of this episode is also attached in this thread. Enjoy. Timestamps 00:00 - How did Aravind get into AI? 13:05 - India’s competitive culture 15:05 - Talent problem or system failure? 16:25 - How can India evolve? 17:45 - China’s approach to research 21:02 - What’s cutting-edge in AI today? 25:02 - What creates value in an economy? 28:45 - What is the internet built on? 32:48 - Can AI assist humans? 35:25 - Why do humans wonder? 37:25 - Why do humans create? 40:50 - Does memory still matter? 43:15 - Does curiosity create knowledge? 45:40 - Biological vs artificial intelligence 51:24 - Is curiosity uniquely human? 58:55 - Can AI shape human thinking? 1:05:24 - Do we understand intelligence? 1:10:50 - Meaning beyond behaviorism 1:21:48 - How do kids learn to learn? 1:25:43 - Why is hardware innovation hard? 1:31:19 - Can AI feel? 1:47:35 - Questions for me

Prakhar Gupta

32,104 просмотров • 9 месяцев назад

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

168,385 просмотров • 3 месяцев назад

WHY THE BEST DESIGNERS MAKE THE WORST EMPLOYEES Simon Corry (Simon Corry), design leader now at Basis, joins Khushi (khushi) and me to talk about how he's built his career on his own terms, why he hires spiky builders, and what agents taught him building a game solo. 00:53 From call center manager to designer 03:39 Why he's the worst employee 10:21 How he hires for spiky, interesting people 13:51 How his agents decided to build a game engine 20:06 AI brain rot & untested agent code in prod 23:52 Design, eng, and product collapsing into one 26:29 Ramp Labs as a blueprint for experiments 31:08 Building out a neolab Basis 32:19 New media and testing the bleeding edge Dry Run
37:06

WHY THE BEST DESIGNERS MAKE THE WORST EMPLOYEES Simon Corry (Simon Corry), design leader now at Basis, joins Khushi (khushi) and me to talk about how he's built his career on his own terms, why he hires spiky builders, and what agents taught him building a game solo. 00:53 From call center manager to designer 03:39 Why he's the worst employee 10:21 How he hires for spiky, interesting people 13:51 How his agents decided to build a game engine 20:06 AI brain rot & untested agent code in prod 23:52 Design, eng, and product collapsing into one 26:29 Ramp Labs as a blueprint for experiments 31:08 Building out a neolab Basis 32:19 New media and testing the bleeding edge Dry Run

Eshita

10,776 просмотров • 1 месяц назад

Few people care more about software performance than Casey Muratori. Give him a few minutes of your attention with this episode, and he'll convince you to learn to read Assembly (no, really, I finally started to read it, it's really not that scary, esp with an AI that can help explain the sequences). Timestamps: 00:00 Intro 05:17 Games at Microsoft 12:52 Building games 16:00 Why performance matters 27:12 Why you should learn to read assembly 30:36 Designing for optimization 42:51 How to get better at writing performant software 49:04 Understanding how the CPU works 55:53 Building games then and now 1:05:56 How game engines changed building games 1:10:48 Why new games compete with old games 1:13:25 GTA 6: why is it taking so long? 1:16:59 Casey's critique of clean code 1:21:48 Casey's take on TDD 1:24:30 What is good code? 1:27:32 What makes a good software engineer? 1:33:56 Why Casey doesn't code with AI 1:39:01 AI's impact on the game industry 1:44:43 AI and burnout 1:50:21 Why you should read papers Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • Sentry – application monitoring software considered “not bad” by millions of developers • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting things we talked about: 1. Is performance starting to matter to businesses? Enterprise software buyers care mainly about cost, compliance, and capabilities – but not performance. Even so, there are some products gaining major popularity and market share due to their performance, such as File Pilot (next-gen file explorer) and the Blick video editor. Is the tide turning? 2. Profiler-driven performance optimization is the wrong way to optimize The standard way of optimizing is to profile the application, tweak hotspots, then check if the stats have improved. But this only finds a local minimum; Casey says every engineer he’s worked with who was a great “optimizer” began by establishing what the hardware could theoretically do, and then did not stop until they’d closed the gap to that performance level. 3. Take a grain of salt with conventional wisdom that premature optimization is the “root of all evil” Many devs use it as an excuse to delay performance optimization, but Casey says that not optimizing in time could mean that only performance hotspots can be fixed later, and not the architectural issues that create poor performance. Architect your system to be performant, or you’ll have trouble solving problems without a rewrite!
1:53:58

Few people care more about software performance than Casey Muratori. Give him a few minutes of your attention with this episode, and he'll convince you to learn to read Assembly (no, really, I finally started to read it, it's really not that scary, esp with an AI that can help explain the sequences). Timestamps: 00:00 Intro 05:17 Games at Microsoft 12:52 Building games 16:00 Why performance matters 27:12 Why you should learn to read assembly 30:36 Designing for optimization 42:51 How to get better at writing performant software 49:04 Understanding how the CPU works 55:53 Building games then and now 1:05:56 How game engines changed building games 1:10:48 Why new games compete with old games 1:13:25 GTA 6: why is it taking so long? 1:16:59 Casey's critique of clean code 1:21:48 Casey's take on TDD 1:24:30 What is good code? 1:27:32 What makes a good software engineer? 1:33:56 Why Casey doesn't code with AI 1:39:01 AI's impact on the game industry 1:44:43 AI and burnout 1:50:21 Why you should read papers Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • Sentry – application monitoring software considered “not bad” by millions of developers • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting things we talked about: 1. Is performance starting to matter to businesses? Enterprise software buyers care mainly about cost, compliance, and capabilities – but not performance. Even so, there are some products gaining major popularity and market share due to their performance, such as File Pilot (next-gen file explorer) and the Blick video editor. Is the tide turning? 2. Profiler-driven performance optimization is the wrong way to optimize The standard way of optimizing is to profile the application, tweak hotspots, then check if the stats have improved. But this only finds a local minimum; Casey says every engineer he’s worked with who was a great “optimizer” began by establishing what the hardware could theoretically do, and then did not stop until they’d closed the gap to that performance level. 3. Take a grain of salt with conventional wisdom that premature optimization is the “root of all evil” Many devs use it as an excuse to delay performance optimization, but Casey says that not optimizing in time could mean that only performance hotspots can be fixed later, and not the architectural issues that create poor performance. Architect your system to be performant, or you’ll have trouble solving problems without a rewrite!

Gergely Orosz

97,977 просмотров • 1 месяц назад

LIVE NOW - Tempo Mainnet: The Race to Agentic Commerce Tempo is live, and the big bet is clear: AI agents need a native payment layer. Georgios Konstantopoulos and Brendan Ryan join Bankless to explore: - why Tempo launched with agentic payments front and center, - how MPP turns payments into auth, - why “give the agent the wallet” could unlock a new internet economy, - where MPP fits against x402, - what Tempo’s L1 design makes possible for builders. Enjoy the episode. --- TIMESTAMPS 0:00 Tempo Mainnet goes live 1:18 Why the launch is focused on agents 3:58 What MPP actually is 6:30 MPP vs x402 15:28 Why agentic commerce matters 20:08 The “original sin” of the internet 26:04 MCP, NLWeb, and the emerging agent stack 34:07 The onboarding flow: wallets for agents 37:11 How Tempo’s wallet security works 40:11 Tempo chain design and specs 51:13 Why build an L1 instead of an Ethereum L2? 56:10 The Ethereum tension 1:05:01 Agent identity, reputation, and ERC-8004 1:06:53 TIP20, stablecoins, and what can be built on Tempo 1:12:36 Builder opportunity in the agentic web
1:21:50

LIVE NOW - Tempo Mainnet: The Race to Agentic Commerce Tempo is live, and the big bet is clear: AI agents need a native payment layer. Georgios Konstantopoulos and Brendan Ryan join Bankless to explore: - why Tempo launched with agentic payments front and center, - how MPP turns payments into auth, - why “give the agent the wallet” could unlock a new internet economy, - where MPP fits against x402, - what Tempo’s L1 design makes possible for builders. Enjoy the episode. --- TIMESTAMPS 0:00 Tempo Mainnet goes live 1:18 Why the launch is focused on agents 3:58 What MPP actually is 6:30 MPP vs x402 15:28 Why agentic commerce matters 20:08 The “original sin” of the internet 26:04 MCP, NLWeb, and the emerging agent stack 34:07 The onboarding flow: wallets for agents 37:11 How Tempo’s wallet security works 40:11 Tempo chain design and specs 51:13 Why build an L1 instead of an Ethereum L2? 56:10 The Ethereum tension 1:05:01 Agent identity, reputation, and ERC-8004 1:06:53 TIP20, stablecoins, and what can be built on Tempo 1:12:36 Builder opportunity in the agentic web

Bankless

23,815 просмотров • 6 месяцев назад

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 просмотров • 7 месяцев назад