Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

. Kent Beck 🌻 is a legend in software engineering: and after coding for 52 years, he's never had more fun than now, he told me. Why? Because AI agents brought back the joy of creating software without the stuff that he's started to hate about coding for so...

GergelyOrosz's profile picture

Gergely Orosz

349,665 subscribers

42,529 Aufrufe • vor 1 Jahr •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

10 Kommentare

Profilbild von Kevin Henrikson
Kevin Henriksonvor 1 Jahr

Incredible to hear. If someone like Kent Beck is having more fun coding after 50+ years, it says a lot about where this tooling is headed. Honestly, this is a fresh perspective for me. A lot of people that I know are still hesitant, skeptic and defensive regarding the developments that we have right now.

Profilbild von Andrei Maxim
Andrei Maximvor 1 Jahr

@KentBeck "Currently, Kent is building a server in Smalltalk (that he’s been wanting to do for many years) and a Language Server Protocol (LSP) for Smalltalk" OMG

Profilbild von Ryan | 🇬🇧 🇳🇱 🇪🇺| ❤️🇺🇦 | 🖕🇷🇺
Ryan | 🇬🇧 🇳🇱 🇪🇺| ❤️🇺🇦 | 🖕🇷🇺vor 1 Jahr

@KentBeck And Facebook being broken - it was, constantly - didn't matter. That random internet nerds could read your PMs or see your "private" albums or get your contact details never had any consequences. That's the advantage of building your business around something frivolous.

Profilbild von Robbie
Robbievor 1 Jahr

@KentBeck VERY excited for this one

Profilbild von Bitclaw
Bitclawvor 1 Jahr

@KentBeck hahaha I have to watch the full episode, I've run into the same thing. Another thing LLMs have done to me is change the implementation to make the test pass 😂

Profilbild von Ray Quant
Ray Quantvor 1 Jahr

@KentBeck Joy matters in creation.

Profilbild von Rich
Richvor 1 Jahr

@KentBeck If you listen to what he's saying in this clip it's that he has to write tests so the LLM doesn't repeatedly shit all over the code. Writing your code manually doesn't have this constant challenge - write tests, write code, done.

Profilbild von somecontextsuburbia
somecontextsuburbiavor 1 Jahr

@KentBeck Most software engineers hate marketing grand standing. Like go to any conference, the MBAs will spiel canned demos , and the DevOps engineers standing next to the podium will be sweating bullets.

Profilbild von Achille
Achillevor 1 Jahr

@KentBeck AI coding tools are a game changer for seasoned devs like Beck, reigniting creativity while shedding the mundane! As for Facebook’s method? It's high-stakes but effective with feature flags and staged rollouts ensuring smooth sailing. High risk, high reward!

Profilbild von Mi Caves®
Mi Caves®vor 1 Jahr

Legendary reflections. 🙌 AI agents have unlocked a new rhythm for software creators, no doubt. But while most are still using agents to build code, some of us are building the environment where intelligence just acts. We skipped the stack entirely. Not just agentic tools, agentic infrastructure. Not shipped. Lived. ⭕️ #AgenticInfrastructure #PostCode #OwnTheSignal

Ähnliche Videos

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.
3:44

We've built a massive verification bottleneck: • 72% of developers use AI to generate code every day • 96% of them don't fully trust it Writing code is now free. All the work now is verifying that the code does what it's supposed to. According to a new State of Code Survey, almost half of the respondents believe the number one skill that will matter most in the coming years is "reviewing and validating AI-generated code for quality and security". Not prompt engineering or vibe-coding, but checking AI's work.

Santiago

16,299 Aufrufe • vor 7 Monaten

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,920 Aufrufe • vor 1 Jahr

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!
3:40

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!

Andrew Ng

1,225,244 Aufrufe • vor 2 Jahren

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.
0:31

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

Akshay 🚀

30,859 Aufrufe • vor 1 Jahr

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

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:
4:42

Nobody is writing 90% of their code using AI. Here's the uncomfortable truth: The real productivity gain from using AI to write code is closer to 10%, nowhere near the 90% people claim. Sundar Pichai said in 2024 that 30% of the new code at Google was AI-generated. However, he went on to admit, during Lex Friedman's podcast, that engineering velocity had only increased by about 10%. AI-generated code isn't free code. It still has to be reviewed, tested, and made production-ready. Optimizing a single step (code generation) doesn't boost output if bottlenecks shift elsewhere (code reviews). It doesn't matter how much code you generate if you can't keep up the review process. The solution: Automate as much as you can the review and verification of your code. I'm working with Sonar, who is sponsoring this post, and they will take care of the code quality and security analysis of your code: • They review over 300B lines of code every single day • They cover reliability, security, and maintainability for your code • You can integrate them into your CI/CD pipeline • You can install them in your IDE (I use their VSCode extension) • Support for more than 30 languages Here is a link so you can check them out:

Santiago

296,637 Aufrufe • vor 10 Monaten

Old software engineering patterns are coming back because of coding agents. Dax Raad(dax), co-founder of AI coding agent OpenCode, on why DDD is becoming more relevant and less painful: “I think it's the same problem as always, which is how do you make code bases that are easy to work in, scalable, that can flex to new requirements. A lot of the old patterns for me are coming back. We've always been a big domain-driven design company. We did it in a very light way. We're now doing it in a much heavier way because we find that these, kind of boring, enterprisey patterns end up being pretty useful because you have a bunch of idiots on your team now. Coding agents are a bunch of idiots. They are going to work 24/7 and they're going to ship a lot of stuff so you need way more guardrails than you used to. What's nice is some of these old patterns we hated because they were very verbose, they produced reliable code that was modular and safe but they were very verbose and annoying to type out… you're not typing it out anymore. Now you can get the benefits of these patterns without the downsides."
1:03

Old software engineering patterns are coming back because of coding agents. Dax Raad(dax), co-founder of AI coding agent OpenCode, on why DDD is becoming more relevant and less painful: “I think it's the same problem as always, which is how do you make code bases that are easy to work in, scalable, that can flex to new requirements. A lot of the old patterns for me are coming back. We've always been a big domain-driven design company. We did it in a very light way. We're now doing it in a much heavier way because we find that these, kind of boring, enterprisey patterns end up being pretty useful because you have a bunch of idiots on your team now. Coding agents are a bunch of idiots. They are going to work 24/7 and they're going to ship a lot of stuff so you need way more guardrails than you used to. What's nice is some of these old patterns we hated because they were very verbose, they produced reliable code that was modular and safe but they were very verbose and annoying to type out… you're not typing it out anymore. Now you can get the benefits of these patterns without the downsides."

The Pragmatic Engineer

175,050 Aufrufe • vor 2 Monaten

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

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

Gergely Orosz

225,804 Aufrufe • vor 7 Monaten

🎙️ New Deployed episode with Ryan Carson, "Builder in Residence" at Amp. It's a great convo about building code agents and building as a solo founder at the same time, and it's refreshingly honest. Case in point, on evals for coding agents: "We do not have a set of evals that we programmatically run to decide if GPT-5 is better than Sonnet-4 yet... everybody in the trenches building these agentic coding tools understands that it is so dynamic, and so frustrating." Great conversation about building with AI, developer experience, and what happens when everyone can code. Check it out. 👇
2:02

🎙️ New Deployed episode with Ryan Carson, "Builder in Residence" at Amp. It's a great convo about building code agents and building as a solo founder at the same time, and it's refreshingly honest. Case in point, on evals for coding agents: "We do not have a set of evals that we programmatically run to decide if GPT-5 is better than Sonnet-4 yet... everybody in the trenches building these agentic coding tools understands that it is so dynamic, and so frustrating." Great conversation about building with AI, developer experience, and what happens when everyone can code. Check it out. 👇

Ian Cairns

250,866 Aufrufe • vor 11 Monaten

In May 2023, a live streaming world record was set with 32 million concurrent viewers watching the finale of the IPL cricket game. How was this system built? Ashutosh Agrawal was the architect behind this system, and he walks us through how live streaming at scale works, how the system was built and tested, and other interesting learnings. Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by our wonderful sponsors: • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half (use the code PRAGMATIC to get one month free) • Augment Code — AI coding assistant that pro engineering teams love --- Three of my biggest takeaways: 1. The architecture behind live streaming systems is surprisingly logical. In the episode, Ashutosh explains how the live streaming system works, starting from the physical cameras on-site, through the production control room (PCR), streams being sliced-and-diced, and the HLS protocol (HTTP Live Streaming) used. 2. There are a LOT of tradeoffs you can play with when live streaming! The tradeoffs between server load, latency, server resources vs client caching are hard decisions to make. Want to reduce the server load? Serve longer chunks to clients, resulting in fewer requests per minute, per client… at the expense of clients potentially lagging more behind. This is just one of many possible decisions to make. 3. “Game day” is such a neat load testing concept. The team at Jio would simulate “game day” load months before the event. They did tell teams when the load test will start: but did not share anything else! Preparing for a “Game day” test is a lot of work, but it can pay off to find parts of the system that shutter under extreme load. See more takeaways and a summary here: Thanks Ashutosh for all these behind-the-scene details!
0:30

In May 2023, a live streaming world record was set with 32 million concurrent viewers watching the finale of the IPL cricket game. How was this system built? Ashutosh Agrawal was the architect behind this system, and he walks us through how live streaming at scale works, how the system was built and tested, and other interesting learnings. Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by our wonderful sponsors: • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half (use the code PRAGMATIC to get one month free) • Augment Code — AI coding assistant that pro engineering teams love --- Three of my biggest takeaways: 1. The architecture behind live streaming systems is surprisingly logical. In the episode, Ashutosh explains how the live streaming system works, starting from the physical cameras on-site, through the production control room (PCR), streams being sliced-and-diced, and the HLS protocol (HTTP Live Streaming) used. 2. There are a LOT of tradeoffs you can play with when live streaming! The tradeoffs between server load, latency, server resources vs client caching are hard decisions to make. Want to reduce the server load? Serve longer chunks to clients, resulting in fewer requests per minute, per client… at the expense of clients potentially lagging more behind. This is just one of many possible decisions to make. 3. “Game day” is such a neat load testing concept. The team at Jio would simulate “game day” load months before the event. They did tell teams when the load test will start: but did not share anything else! Preparing for a “Game day” test is a lot of work, but it can pay off to find parts of the system that shutter under extreme load. See more takeaways and a summary here: Thanks Ashutosh for all these behind-the-scene details!

Gergely Orosz

50,632 Aufrufe • vor 1 Jahr

Mark Zuckerberg says the future of coding is closer than we think: AI agents inside Meta are being built not as generic developer tools, but to push Llama research forward — fully integrated into their workflow. He predicts that within 12–18 months, most of the code for these efforts could be written by AI itself — not simple autocomplete, but systems that take goals, run tests, fix bugs, improve performance, and even write higher-quality code than many skilled engineers. The real takeaway? This is only one part of a massive AI landscape, and no single company will dominate it all. Meta is building its own internal agents designed specifically to advance Llama research — deeply connected to their toolchain rather than built for enterprise customers. He expects that within the next year to year-and-a-half, AI will be writing most of the code in these projects, going far beyond autocomplete — understanding goals, running experiments, finding issues, and continuously improving systems. And according to him, this shift will become a core driver of how AI itself evolves. Meta is investing heavily in coding and research agents deeply integrated into their own systems, focused on advancing Llama rather than building broad enterprise tools. He expects AI will soon move beyond autocomplete to fully goal-driven coding — testing, debugging, improving, and producing high-quality results. But in his view, the AI revolution is too big for any single winner — multiple players and approaches will shape the future.
2:36

Mark Zuckerberg says the future of coding is closer than we think: AI agents inside Meta are being built not as generic developer tools, but to push Llama research forward — fully integrated into their workflow. He predicts that within 12–18 months, most of the code for these efforts could be written by AI itself — not simple autocomplete, but systems that take goals, run tests, fix bugs, improve performance, and even write higher-quality code than many skilled engineers. The real takeaway? This is only one part of a massive AI landscape, and no single company will dominate it all. Meta is building its own internal agents designed specifically to advance Llama research — deeply connected to their toolchain rather than built for enterprise customers. He expects that within the next year to year-and-a-half, AI will be writing most of the code in these projects, going far beyond autocomplete — understanding goals, running experiments, finding issues, and continuously improving systems. And according to him, this shift will become a core driver of how AI itself evolves. Meta is investing heavily in coding and research agents deeply integrated into their own systems, focused on advancing Llama rather than building broad enterprise tools. He expects AI will soon move beyond autocomplete to fully goal-driven coding — testing, debugging, improving, and producing high-quality results. But in his view, the AI revolution is too big for any single winner — multiple players and approaches will shape the future.

Ian Miles Cheong

20,561 Aufrufe • vor 6 Monaten

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,327 Aufrufe • vor 1 Jahr

HIS VIBE CODING APP WAS HACKED and he almost lost $10,000 because of it After analyzing why this happened, we managed to find 3 most common mistakes that appear in the majority of vibe coding projects: • Misconfigured RLS • No backend rate limits • AI calls made from the frontend And vibe coding is actually not dangerous, you just need to pay more attention to these points when creating a project: • Protecting access to data • Limiting resource usage • Hiding all secrets on the backend • Controlling costs • Regularly doing security reviews It’s also important from the very beginning to give AI tools for improving code security And I talked about them in the article below👇
16:14

HIS VIBE CODING APP WAS HACKED and he almost lost $10,000 because of it After analyzing why this happened, we managed to find 3 most common mistakes that appear in the majority of vibe coding projects: • Misconfigured RLS • No backend rate limits • AI calls made from the frontend And vibe coding is actually not dangerous, you just need to pay more attention to these points when creating a project: • Protecting access to data • Limiting resource usage • Hiding all secrets on the backend • Controlling costs • Regularly doing security reviews It’s also important from the very beginning to give AI tools for improving code security And I talked about them in the article below👇

TolyaDV

45,570 Aufrufe • vor 2 Monaten

lee from cursor JUST showed me the future of coding in this 29 min tutorial. what if instead of thinking about coding as you sitting alone in front of a screen , you started to think about it as you and a swarm of agents each taking on very specific roles, each showing up exactly when you need them, each running in the background without ever needing a coffee break. imagine a bugbot that doesn’t just review your pull request but triages the issue instantly, leaves intelligent comments, and in some cases even proposes a fix before a teammate has had the chance to read the description. imagine a security agent that quietly scans your code for vulnerabilities and flags them long before they become liabilities. imagine an agent dedicated to software culture, enforcing the little rules your team has decided matter, whether that’s never skipping loading states, banning certain lazy marketing phrases in your code comments, or making sure tests are always included. lee walked me through how all of this already exists inside cursor. he spun up custom commands like /code-review or /security-review that behave less like toys and more like trusted coworkers who have internalized the way your team thinks about quality. and when he combined that with rails, type safety, linters, formatting rules, test suites.... the agents learned to check themselves against the rails and fix mistakes automatically. you end up with a system where the codebase begins to feel alive, constantly watching itself, constantly healing. another thing i learned from lee was watching how he doesn’t pile everything into one giant context and hope for magic. he creates new chats for every new task, sometimes twenty or more in a single day, each one a fresh brain that isn’t bogged down by yesterday’s details. it’s a discipline that keeps the agents sharp and the outputs clean. pro tip, thanks Lee Robinson. this was a cool glimpse into the future of coding and some tips on how to squeeze the most out of cursor. anything is possible.
29:41

lee from cursor JUST showed me the future of coding in this 29 min tutorial. what if instead of thinking about coding as you sitting alone in front of a screen , you started to think about it as you and a swarm of agents each taking on very specific roles, each showing up exactly when you need them, each running in the background without ever needing a coffee break. imagine a bugbot that doesn’t just review your pull request but triages the issue instantly, leaves intelligent comments, and in some cases even proposes a fix before a teammate has had the chance to read the description. imagine a security agent that quietly scans your code for vulnerabilities and flags them long before they become liabilities. imagine an agent dedicated to software culture, enforcing the little rules your team has decided matter, whether that’s never skipping loading states, banning certain lazy marketing phrases in your code comments, or making sure tests are always included. lee walked me through how all of this already exists inside cursor. he spun up custom commands like /code-review or /security-review that behave less like toys and more like trusted coworkers who have internalized the way your team thinks about quality. and when he combined that with rails, type safety, linters, formatting rules, test suites.... the agents learned to check themselves against the rails and fix mistakes automatically. you end up with a system where the codebase begins to feel alive, constantly watching itself, constantly healing. another thing i learned from lee was watching how he doesn’t pile everything into one giant context and hope for magic. he creates new chats for every new task, sometimes twenty or more in a single day, each one a fresh brain that isn’t bogged down by yesterday’s details. it’s a discipline that keeps the agents sharp and the outputs clean. pro tip, thanks Lee Robinson. this was a cool glimpse into the future of coding and some tips on how to squeeze the most out of cursor. anything is possible.

GREG ISENBERG

47,160 Aufrufe • vor 11 Monaten