Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

svpino's profile picture

Santiago

453,023 subscribers

296,570 görüntüleme • 10 ay önce •via X (Twitter)

Bilim & TeknolojiHaberler & PolitikaEğitim
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.
3:25

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,425 görüntüleme • 8 ay önce

Stage is a code review platform designed to help engineers understand AI-generated code. Your team is drowning in an endless backlog of PRs. Stage turns code review into a guided process and enables you to review changes faster than using GitHub. Congrats on the launch, Charles Pan and Dean Stratakos!
0:50

Stage is a code review platform designed to help engineers understand AI-generated code. Your team is drowning in an endless backlog of PRs. Stage turns code review into a guided process and enables you to review changes faster than using GitHub. Congrats on the launch, Charles Pan and Dean Stratakos!

Y Combinator

1,063,634 görüntüleme • 2 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,628 görüntüleme • 8 ay önce

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

After reaching AI-native terminal velocity we are swamped in code review. The core insight is that as long as you can write code in parallel you will continue to be stuck until you can review it in parallel. I was surprised by how quickly this became my daily driver for not just review code, but writing it as well.
0:30

After reaching AI-native terminal velocity we are swamped in code review. The core insight is that as long as you can write code in parallel you will continue to be stuck until you can review it in parallel. I was surprised by how quickly this became my daily driver for not just review code, but writing it as well.

Evan Boyle

23,986 görüntüleme • 6 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

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna 👩🏽‍💻✨, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:
1:39

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna 👩🏽‍💻✨, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:

DeepLearning.AI

53,175 görüntüleme • 11 gün önce

I installed a new Visual Studio Code extension to help me write code. But this extension doesn't get in your way. It doesn't try to write code for you. It only gives you hints and recommendations about your code. I like that. Like a second pair of eyes, looking over my shoulder and telling me how I can do things better. The extension is Traycer. You can install it directly from inside Visual Studio Code. It's free forever for anyone working on open-source projects (and if you aren't, you can use it for free until the end of June.) I recorded a super-duper-quick video to show you how this extension works. I know code generation is a huge thing, but I really appreciate tools that help me do what I do better. Thanks to the Traycer team for helping me with the extension and collaborating with me on this post!
2:56

I installed a new Visual Studio Code extension to help me write code. But this extension doesn't get in your way. It doesn't try to write code for you. It only gives you hints and recommendations about your code. I like that. Like a second pair of eyes, looking over my shoulder and telling me how I can do things better. The extension is Traycer. You can install it directly from inside Visual Studio Code. It's free forever for anyone working on open-source projects (and if you aren't, you can use it for free until the end of June.) I recorded a super-duper-quick video to show you how this extension works. I know code generation is a huge thing, but I really appreciate tools that help me do what I do better. Thanks to the Traycer team for helping me with the extension and collaborating with me on this post!

Santiago

101,068 görüntüleme • 2 yıl önce

Software Engineering Expectations for 2026 - The majority of your code should be written by AI now - Cursor/Codex/Claude Code/Gemini/etc - You should try all the tooling and switch between them, as each one gets an edge over the others depending on the release cycle. - You should be using AI to check the code that is written by AI - Have AI write tests - Have AI read logs - Have AI navigate your browser - I don't do this every time because sometimes it's simple enough to check it myself - You should still skim code changes - This can be a lighter skim on internal tools and a heavier read through on customer facing code - Use AI to help you define specs
4:12

Software Engineering Expectations for 2026 - The majority of your code should be written by AI now - Cursor/Codex/Claude Code/Gemini/etc - You should try all the tooling and switch between them, as each one gets an edge over the others depending on the release cycle. - You should be using AI to check the code that is written by AI - Have AI write tests - Have AI read logs - Have AI navigate your browser - I don't do this every time because sometimes it's simple enough to check it myself - You should still skim code changes - This can be a lighter skim on internal tools and a heavier read through on customer facing code - Use AI to help you define specs

Ben Awad

534,705 görüntüleme • 7 ay önce

Claude Code has had TONS of secret updates over the past month They COMPLETELY change how you use Claude Code In this video I go over EVERY update, and show you how to use them, even if you've never used Claude Code before If you care about AI, this is a must watch:
14:26

Claude Code has had TONS of secret updates over the past month They COMPLETELY change how you use Claude Code In this video I go over EVERY update, and show you how to use them, even if you've never used Claude Code before If you care about AI, this is a must watch:

Alex Finn

54,942 görüntüleme • 7 ay önce

prompting tip: How to write hybrid english & code prompts while building custom GPTs -Turn on code interpreter -"write code to ..." -Regenerate a few times until you get one you like -Copy paste it back into your prompt -tweak it to improve Now your ai can write consistent code Plus, you can add & combine with all sorts of english rules on top. Essentially adding english code logic "If the user asks for ..., then run this code" "If the user needs help with ..., use this code snippet and ask the user for all required information" Guess what thats a working if statement in english! if userAsksFor { // run this code } Prompts are code! English is a coding language Prompt-gramming is abstract coding
0:57

prompting tip: How to write hybrid english & code prompts while building custom GPTs -Turn on code interpreter -"write code to ..." -Regenerate a few times until you get one you like -Copy paste it back into your prompt -tweak it to improve Now your ai can write consistent code Plus, you can add & combine with all sorts of english rules on top. Essentially adding english code logic "If the user asks for ..., then run this code" "If the user needs help with ..., use this code snippet and ask the user for all required information" Guess what thats a working if statement in english! if userAsksFor { // run this code } Prompts are code! English is a coding language Prompt-gramming is abstract coding

Nick Dobos

117,034 görüntüleme • 2 yıl önce

“Math is code. And code is math.” Carina Hong CEO Axiom on why that idea matters for AI: “For centuries, mathematicians reasoned in natural language. But because of the Curry–Howard correspondence, a proof can also be a program.” “You can translate natural-language math into formal code using systems like Lean. Lean is both a theorem-proving language and a programming language.” “That means you can generate solutions as code and then formally verify them. You can even use the same system to verify programs themselves.” “This creates a flywheel of generation and verification, where AI can both write solutions and prove that they’re correct.”
2:25

“Math is code. And code is math.” Carina Hong CEO Axiom on why that idea matters for AI: “For centuries, mathematicians reasoned in natural language. But because of the Curry–Howard correspondence, a proof can also be a program.” “You can translate natural-language math into formal code using systems like Lean. Lean is both a theorem-proving language and a programming language.” “That means you can generate solutions as code and then formally verify them. You can even use the same system to verify programs themselves.” “This creates a flywheel of generation and verification, where AI can both write solutions and prove that they’re correct.”

Forward Future

24,729 görüntüleme • 5 ay önce

"The one thing that's going to be truly future proof is judgment. What is the biggest challenge when you have a thousand AI engineers writing code? AI slop. In an era when you can do everything, the question is which of these things matter. On the engineer side, it is evaluating the code. Which of this code is even valuable? You can have AI engineers writing beautiful code that could be wrong, that could have bugs in it, that could be vulnerable. Someone needs to review it. Make sure to have a human review at some point, especially critical code that is in the core of your system. On the product side is judgment around what needs to be built and evaluating. And similarly in design, you have to have judgment around, does it make sense in the broader design system. I think this judgment is the number one thing that humans are going to bring in an era of infinite productivity."
1:12

"The one thing that's going to be truly future proof is judgment. What is the biggest challenge when you have a thousand AI engineers writing code? AI slop. In an era when you can do everything, the question is which of these things matter. On the engineer side, it is evaluating the code. Which of this code is even valuable? You can have AI engineers writing beautiful code that could be wrong, that could have bugs in it, that could be vulnerable. Someone needs to review it. Make sure to have a human review at some point, especially critical code that is in the core of your system. On the product side is judgment around what needs to be built and evaluating. And similarly in design, you have to have judgment around, does it make sense in the broader design system. I think this judgment is the number one thing that humans are going to bring in an era of infinite productivity."

Patrick OShaughnessy

24,818 görüntüleme • 6 ay önce

I force Claude Code to review every single line of code it generates for security vulnerabilities. This is table stakes. Companies shouldn't allow their developers to commit any code without doing this first. (MCP is an amazing way to improve Claude Code's capabilities and generate code that's 10x better than what you get out of the box.)
7:03

I force Claude Code to review every single line of code it generates for security vulnerabilities. This is table stakes. Companies shouldn't allow their developers to commit any code without doing this first. (MCP is an amazing way to improve Claude Code's capabilities and generate code that's 10x better than what you get out of the box.)

Santiago

81,625 görüntüleme • 10 ay önce

For those of you tired of yet another AI-based IDE: Check out Traycer. It's a Visual Studio Code extension (free forever for anyone working on open-source repositories), and it does something different from everyone else. You write a high-level prompt outlining the changes you want to make to your codebase, and the extension generates a plan for you before you touch the code. (It reminds me of GitHub Copilot Workspaces.) You can review the plan, understand exactly the changes the extension will make to your code, and make any modifications. When you are ready, you execute the plan, and Traycer stages all of the changes so you have a new opportunity to review everything. Only then does Traycer apply the changes. This is ideal for large codebases where you'd rather study the changes the AI plans to make before they make it into your code. Look at the video I recorded to see how it works. Thanks to the Traycer team for collaborating with me on this post!
7:27

For those of you tired of yet another AI-based IDE: Check out Traycer. It's a Visual Studio Code extension (free forever for anyone working on open-source repositories), and it does something different from everyone else. You write a high-level prompt outlining the changes you want to make to your codebase, and the extension generates a plan for you before you touch the code. (It reminds me of GitHub Copilot Workspaces.) You can review the plan, understand exactly the changes the extension will make to your code, and make any modifications. When you are ready, you execute the plan, and Traycer stages all of the changes so you have a new opportunity to review everything. Only then does Traycer apply the changes. This is ideal for large codebases where you'd rather study the changes the AI plans to make before they make it into your code. Look at the video I recorded to see how it works. Thanks to the Traycer team for collaborating with me on this post!

Santiago

84,497 görüntüleme • 1 yıl önce

Let's face it: AI can check your code 100x faster and catch 10x more issues than you can. "Code reviews" as a widespread practice is not coming back. There are only two reasons we should consider code reviews today: 1. To transfer knowledge within a team. 2. To ensure AI didn't miss critical aspects in the code. We are getting closer to a point where manually reviewing code will be as relevant as punching holes in a punch card. Here is one idea for you:
0:40

Let's face it: AI can check your code 100x faster and catch 10x more issues than you can. "Code reviews" as a widespread practice is not coming back. There are only two reasons we should consider code reviews today: 1. To transfer knowledge within a team. 2. To ensure AI didn't miss critical aspects in the code. We are getting closer to a point where manually reviewing code will be as relevant as punching holes in a punch card. Here is one idea for you:

Santiago

48,783 görüntüleme • 1 yıl önce

Claude Code UI is now available in VSCode via CodeGPT extension! 🙌 You can now run Claude Code directly in your editor and control the planning process. You can pause it, edit tasks, or add new ones while Claude is working. This helps keep Claude on track and makes it way more effective since you can adjust things as it goes. Setup: - Download the extensión - Click the Claude Code OAuth - Authorize the extension - Paste your account code to link Claude Code directly - Done ✅ Works on VSCode and JetBrains editors (Android Studio, IntelliJ, PyCharm, etc.) VSCode : Jetbrains:
0:48

Claude Code UI is now available in VSCode via CodeGPT extension! 🙌 You can now run Claude Code directly in your editor and control the planning process. You can pause it, edit tasks, or add new ones while Claude is working. This helps keep Claude on track and makes it way more effective since you can adjust things as it goes. Setup: - Download the extensión - Click the Claude Code OAuth - Authorize the extension - Paste your account code to link Claude Code directly - Done ✅ Works on VSCode and JetBrains editors (Android Studio, IntelliJ, PyCharm, etc.) VSCode : Jetbrains:

Daniel San

106,169 görüntüleme • 11 ay önce

The new Screenshot to Code from Vercel v0 is insane. I just took a screenshot of a pricing table and it was converted into code using AI in seconds! It even outputs the code and allows you to modify any specific parts.
0:20

The new Screenshot to Code from Vercel v0 is insane. I just took a screenshot of a pricing table and it was converted into code using AI in seconds! It even outputs the code and allows you to modify any specific parts.

Alvaro Cintas

378,020 görüntüleme • 2 yıl önce

Zerve has been the best platform for writing data science code for a while. It's 100x better than Jupyter notebooks. Now, they have a specialized, fine-tuned AI assistant who knows all about data science code and how to use the platform. This is a killer feature. A generalist model will never be better than a specialized one. Watch the video. I promise you'll be jealous in 3 minutes. Some other features, in case you've never used Zerve: 1. It's web-based 2. You can share and work with your team on the same canvas 3. You can deploy your code with a click 4. Blocks are the center of attention. Promotes code modularity 5. You can combine multiple languages in a single canvas 6. You can run code blocks in parallel Zerve organizes your code as a DAG. Each block inherits the state of every block before it. Everything runs in a serverless architecture. By the way, you can use Zerve for FREE. Visit this link: Thanks to the team for partnering with me on this post.
5:24

Zerve has been the best platform for writing data science code for a while. It's 100x better than Jupyter notebooks. Now, they have a specialized, fine-tuned AI assistant who knows all about data science code and how to use the platform. This is a killer feature. A generalist model will never be better than a specialized one. Watch the video. I promise you'll be jealous in 3 minutes. Some other features, in case you've never used Zerve: 1. It's web-based 2. You can share and work with your team on the same canvas 3. You can deploy your code with a click 4. Blocks are the center of attention. Promotes code modularity 5. You can combine multiple languages in a single canvas 6. You can run code blocks in parallel Zerve organizes your code as a DAG. Each block inherits the state of every block before it. Everything runs in a serverless architecture. By the way, you can use Zerve for FREE. Visit this link: Thanks to the team for partnering with me on this post.

Santiago

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