Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

AI has changed software engineering more in the last 3 years than it has changed in the previous 30. What’s needed is not a debate about whether it’s going away—instead it’s a serious discussion about its future: What are the new primitives, techniques, and best practices for software engineering...

34,753 görüntüleme • 8 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

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

Guillermo Rauch (Guillermo Rauch) is one of the most prolific coders of this generation. But he doesn’t think of himself as a coder anymore. Coding, he says, is a specific skill that AI is becoming great at. Instead, he thinks the future of coding is more holistic, full-stack engineers who can ideate, design, and execute all together. Guillermo is the founder and CEO of Vercel (Vercel), the creator of NextJS, and SocketIO. We spent an hour talking about the future of software development in an AI world—and the meta-skills that are essential for the coders of today to master—in order to use tomorrow’s tools to their fullest extent. Here are a few takeaways: - One of the most important keys to his success is taste—and developing taste is all about paying better attention to everything you experience day to day. - He’s great at recognizing bleeding-edge technologies with extremely practical applications but that have bad user experiences. If you can learn to recognize those and build with them, you might build the next NextJs or SocketIO. - Why prototype cultures are becoming common in AI—and the benefits of written cultures like Amazon vs. prototype cultures like Apple for different kinds of companies. - For developers building frameworks, always put the product first; a framework in isolation without a “customer zero” is never going to be a good tool. - The theory of “recursive founder mode”—if you want to build a scalable business, you have to scale yourself by creating an atmosphere that nurtures talent and ambition. - AI tools are shifting software toward consumption-based billing models, making us capital allocators who decide how much compute the AI consumes. - The future of AI is agents with the taste, knowledge, and tools to perform specialized tasks. Watch below! Timestamps: Introduction: 00:01:33 How to spot trends early: 00:03:18 Why you should be your own customer: 00:07:34 How to create an ecosystem of talent and ambition: 00:14:55 Why Guillermo doesn't identify as a coder: 00:17:29 AI is gearing us toward an allocation economy: 00:20:50 How Vercel’s copilot compares with other coding agents: 00:28:34 Guillermo’s advice on having better taste: 00:40:35 The future of AI agents is specialized: 00:42:46 How AI startups can compete with big tech: 00:47:50

Dan Shipper 📧

186,927 görüntüleme • 1 yıl önce

SaaS isn’t dead, it just needs to become agent-native. Linear (Linear) is a great example of how: They pivoted the product to be used by both humans and agents, and that has made them one of the premier software tools in the agent-native era. I had Linear’s cofounder and CEO Karri Saarinen on Every 📧's AI & I to talk about how a product management tool for human software developers became an agent-native tool—and how Linear’s trajectory reveals a bright future for SaaS businesses: - Speed means decisions matter more, not less. AI makes it easy to have an idea and build it without considering whether its existence is justified. When ChatGPT was released, SaaS companies were launching their own chatbots left, right, and center. Instead of jumping on the bandwagon, Linear stopped to consider whether the application was useful. (It wasn’t.) - Just because the technology has changed doesn’t mean your mission should. Karri attributes Linear’s success to never losing sight of what matters: helping teams develop great software. Instead of chasing trends, Linear focused on understanding how AI was impacting its customers’ workflows—and updating its product accordingly. - Agents are now first-class users. Linear never tried to change what it was or did well; it just expanded the user base. Companies can now kick off agents inside Linear, manage them, and track what they're working on alongside the humans on the team, which explains why Codex, Coinbase, and Brex all run their agents on Linear. This is a must watch for anyone interested in how an agent-native SaaS company operates. Watch below! Timestamps: Introduction and how Every first discovered Linear: 00:00:39 Why Linear waited to ship AI features instead of rushing to chatbots: 00:02:00 Linear's agent platform and becoming the system that guides AI agents: 00:05:06 Why "SaaS is dead" is a simplistic narrative: 00:07:42 How Linear adopted AI coding tools internally: 00:12:18 AI's impact on product building workflows—speed versus thoughtfulness: 00:17:45 The value of conceptual work and thinking before shipping: 00:22:18 How AI is reshaping Linear's product strategy: 00:29:30 Demo: Linear's agent skills, shared context, and code review workflow: 00:37:18 The future of product development and the enduring role of human judgment: 00:47:48

Dan Shipper 📧

36,288 görüntüleme • 2 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

Dan Shipper 📧

57,540 görüntüleme • 7 ay önce

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper 📧

66,256 görüntüleme • 1 ay önce