Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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...

GergelyOrosz's profile picture

Gergely Orosz

343,525 subscribers

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

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below
2:15

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

182,466 görüntüleme • 1 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,568 görüntüleme • 8 ay önce

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code
1:00:16

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 görüntüleme • 11 ay önce

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below
17:28

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 görüntüleme • 1 ay önce

Claude Code creator: "At Anthropic, 90% of our engineers are running agents with self-improving loops. in 3-6 months, everyone will be running /loops - this is the future of engineering" in a 1-hour podcast, Boris Cherny reveals the best tips for building Claude Code automations. Claude + loops + routines + dynamic workflows - that’s the secret. Watch the talk, then read how to apply and build the same setup in the article below.
1:23:07

Claude Code creator: "At Anthropic, 90% of our engineers are running agents with self-improving loops. in 3-6 months, everyone will be running /loops - this is the future of engineering" in a 1-hour podcast, Boris Cherny reveals the best tips for building Claude Code automations. Claude + loops + routines + dynamic workflows - that’s the secret. Watch the talk, then read how to apply and build the same setup in the article below.

Movez

268,678 görüntüleme • 1 ay önce

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below
51:00

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below

Anatoli Kopadze

20,003 görüntüleme • 1 ay önce

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below
50:12

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,176 görüntüleme • 1 ay önce

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below
1:22:03

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below

Anatoli Kopadze

22,412 görüntüleme • 1 ay önce

Boris Cherny, the creator of Claude Code at Anthropic, just explained how he runs thousands of agents from his phone while he sleeps in this talk he breaks down exactly how he manages thousands of agents from his phone: - the 14% you lose to CLAUDE.md before typing a word - the architecture behind running a few thousand agents overnight - why the system matters more than the tool - the knowledge structure that makes everything findable, connected, and useful if you've been using Claude for months and every conversation still starts from scratch with zero memory and zero context, you don't have a system. you have a chat history instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below
57:23

Boris Cherny, the creator of Claude Code at Anthropic, just explained how he runs thousands of agents from his phone while he sleeps in this talk he breaks down exactly how he manages thousands of agents from his phone: - the 14% you lose to CLAUDE.md before typing a word - the architecture behind running a few thousand agents overnight - why the system matters more than the tool - the knowledge structure that makes everything findable, connected, and useful if you've been using Claude for months and every conversation still starts from scratch with zero memory and zero context, you don't have a system. you have a chat history instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below

Khairallah AL-Awady

86,247 görüntüleme • 1 ay önce

💥NEW AI CODING TUTORIAL: 12 Months of Claude Code Lessons in 46 Minutes Claude Code just turned 1. So here's 52 lessons on how to get the most out of Claude Code, organized into 3 levels: Beginner, Intermediate, and Master. TIMESTAMPS 00:00 12 Months of building with Claude Code 02:01 LEVEL 1: Beginner 02:09 Installation and Setup 04:55 Models and Modes 09:04 CLAUDE.md (and what to put in) 10:30 Context Management 11:31 Debugging with Claude 12:22 Version control 14:12 Prompting, Just ask Claude 16:01 LEVEL 2: Intermediate 16:24 Customizations (Skills, Plugins, MCPs) 24:42 Workflows: Plan, Build, Test 29:52 Verifying and Documenting with Claude 33:10 LEVEL 3: Master 34:17 Multi-Agent Development (multi-clauding with git worktrees) 37:07 Self-improving Systems 38:45 Ralph Wiggum Agent Loops 40:11 Async Task Delegation 42:00 Agent Teams, Pre-configure permissions, Hooks 44:42 Continue your learning
45:47

💥NEW AI CODING TUTORIAL: 12 Months of Claude Code Lessons in 46 Minutes Claude Code just turned 1. So here's 52 lessons on how to get the most out of Claude Code, organized into 3 levels: Beginner, Intermediate, and Master. TIMESTAMPS 00:00 12 Months of building with Claude Code 02:01 LEVEL 1: Beginner 02:09 Installation and Setup 04:55 Models and Modes 09:04 CLAUDE.md (and what to put in) 10:30 Context Management 11:31 Debugging with Claude 12:22 Version control 14:12 Prompting, Just ask Claude 16:01 LEVEL 2: Intermediate 16:24 Customizations (Skills, Plugins, MCPs) 24:42 Workflows: Plan, Build, Test 29:52 Verifying and Documenting with Claude 33:10 LEVEL 3: Master 34:17 Multi-Agent Development (multi-clauding with git worktrees) 37:07 Self-improving Systems 38:45 Ralph Wiggum Agent Loops 40:11 Async Task Delegation 42:00 Agent Teams, Pre-configure permissions, Hooks 44:42 Continue your learning

Avthar

62,263 görüntüleme • 4 ay önce

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.
20:58

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,028 görüntüleme • 1 ay önce

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below
29:10

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

102,529 görüntüleme • 1 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

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below
28:49

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,504 görüntüleme • 1 ay önce

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,179 görüntüleme • 3 ay önce

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."
0:36

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."

Lenny Rachitsky

369,830 görüntüleme • 1 yıl ö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 • 5 ay önce

An MCP server that detects production-grade code quality issues in real-time! Even though AI is now generating code at light speed, the engineering bottleneck has just moved from writing to reviewing, and now devs spend 90% of their debugging time on AI-generated code. AI reviewers aren't that reliable either because they share the same fundamental blind spots as AI generators do: - They pattern match, not proof check. - They validate syntax, not system behavior. - They review code, not consequences. I have been using the SonarQube MCP Server (by Sonar) to solve this. It produces enterprise-grade code analysis and returns instant feedback on bugs, vulnerabilities, and code smells right where you're working (Claude Code, Cursor, etc.). Its capabilities have emerged from the 750B+ lines of code SonarQube processes daily, so it has seen every bug pattern that exists. This includes: - Security vulnerabilities (SQL injection, XSS, hardcoded secrets) - Code smells and technical debt - Test coverage gaps - Maintainability issues The setup is simple: - Install the SonarQube MCP server - Add it to your AI assistant's config Done! SonarQube is now part of your AI coding workflow. I have shared the GitHub repo in the replies! P.S. Thanks to Sonar for working with me today.
0:28

An MCP server that detects production-grade code quality issues in real-time! Even though AI is now generating code at light speed, the engineering bottleneck has just moved from writing to reviewing, and now devs spend 90% of their debugging time on AI-generated code. AI reviewers aren't that reliable either because they share the same fundamental blind spots as AI generators do: - They pattern match, not proof check. - They validate syntax, not system behavior. - They review code, not consequences. I have been using the SonarQube MCP Server (by Sonar) to solve this. It produces enterprise-grade code analysis and returns instant feedback on bugs, vulnerabilities, and code smells right where you're working (Claude Code, Cursor, etc.). Its capabilities have emerged from the 750B+ lines of code SonarQube processes daily, so it has seen every bug pattern that exists. This includes: - Security vulnerabilities (SQL injection, XSS, hardcoded secrets) - Code smells and technical debt - Test coverage gaps - Maintainability issues The setup is simple: - Install the SonarQube MCP server - Add it to your AI assistant's config Done! SonarQube is now part of your AI coding workflow. I have shared the GitHub repo in the replies! P.S. Thanks to Sonar for working with me today.

Avi Chawla

28,027 görüntüleme • 7 ay önce

A designer who can ship code is one of the most valuable hires in tech today. Here's my new episode with Felix Lee (CEO of ADPList) where he showed me how to use Claude Code and Figma MCP to go from: ✅ Figma → Code: Design to website in 15 min ✅ Code → Figma: App back to editable design Felix also demoed a few apps he's designed and built in Claude Code, including a 3D globe website and a landing page analyzer. Some takeaways from Felix: 1. Stop pasting screenshots into Claude Code. Instead, use Figma MCP to pull in all your assets, icons, and images automatically. 2. You can use the same MCP to convert code back into editable Figma layers to explore more variations. 3. An underrated way to build: Use FigJam to plan a flowchart of your app first, then paste the link into Claude Code with the MCP. 📌 Watch now: Thanks to our sponsors: Replit ⠕: Plan, design, and build with AI agents Linear: The AI agent platform for modern teams
0:48

A designer who can ship code is one of the most valuable hires in tech today. Here's my new episode with Felix Lee (CEO of ADPList) where he showed me how to use Claude Code and Figma MCP to go from: ✅ Figma → Code: Design to website in 15 min ✅ Code → Figma: App back to editable design Felix also demoed a few apps he's designed and built in Claude Code, including a 3D globe website and a landing page analyzer. Some takeaways from Felix: 1. Stop pasting screenshots into Claude Code. Instead, use Figma MCP to pull in all your assets, icons, and images automatically. 2. You can use the same MCP to convert code back into editable Figma layers to explore more variations. 3. An underrated way to build: Use FigJam to plan a flowchart of your app first, then paste the link into Claude Code with the MCP. 📌 Watch now: Thanks to our sponsors: Replit ⠕: Plan, design, and build with AI agents Linear: The AI agent platform for modern teams

Peter Yang

77,115 görüntüleme • 4 ay önce

This guy literally broke down everything to build a 21 agent dev team in Claude Code: 0:00 - Why one prompt = AI slop 1:55 - Claude Code as your full startup 2:43 - The 21-agent team 4:57 - Inside the system analyst agent 5:52 - Live demo: 0 → TestFlight 8:42 - Define a "good" system analyst first 11:53 - The system analyst workflow 12:17 - Why Confluence + Jira + MCPs matter 15:30 - Classic PM skills > vibe coding 19:15 - The scaffolding that kills spaghetti code 22:10 - Setting up agents inside Claude Code 26:19 - The longest dictation prompt this podcast has seen 35:29 - Why dictation beats typing for AI specs 47:30 - Brand guidelines in Figma Make 55:59 - Idea → prompt → design → app 1:06:27 - Claude Code builds the Figma screens 1:23:59 - Frontend tickets appear in Jira (with Figma links) 1:48:49 - The hockey rules AI app goes live 1:53:56 - Full recap: Claude, Confluence, Figma, Jira, Simulator, TestFlight 2:03:17 - Should PMs get AI PM certificates? 2:08:15 - How to build a PM portfolio that lands FAANG offers 2:13:25 - How to get started this week
2:15:18

This guy literally broke down everything to build a 21 agent dev team in Claude Code: 0:00 - Why one prompt = AI slop 1:55 - Claude Code as your full startup 2:43 - The 21-agent team 4:57 - Inside the system analyst agent 5:52 - Live demo: 0 → TestFlight 8:42 - Define a "good" system analyst first 11:53 - The system analyst workflow 12:17 - Why Confluence + Jira + MCPs matter 15:30 - Classic PM skills > vibe coding 19:15 - The scaffolding that kills spaghetti code 22:10 - Setting up agents inside Claude Code 26:19 - The longest dictation prompt this podcast has seen 35:29 - Why dictation beats typing for AI specs 47:30 - Brand guidelines in Figma Make 55:59 - Idea → prompt → design → app 1:06:27 - Claude Code builds the Figma screens 1:23:59 - Frontend tickets appear in Jira (with Figma links) 1:48:49 - The hockey rules AI app goes live 1:53:56 - Full recap: Claude, Confluence, Figma, Jira, Simulator, TestFlight 2:03:17 - Should PMs get AI PM certificates? 2:08:15 - How to build a PM portfolio that lands FAANG offers 2:13:25 - How to get started this week

Aakash Gupta

178,026 görüntüleme • 2 ay önce