Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

AI-generated code moves fast. Sometimes vulnerabilities do too. Most security tools check code after the work is done. By then, the context behind a change is already fading. Security feedback should arrive while that context is still fresh. Meet Qoder Security 👇

Qoder

10,034 subscribers

49,576 views • 25 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

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

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 views • 7 months ago

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:

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,674 views • 17 days ago

Introducing Asterisk MCP - An MCP server that fixes security vulnerabilities while you vibe code. Supports Cursor, Windsurf, Cline, Claude, and any IDE that supports the model context protocol. It can perform codebase-wide scans, analyze snippets in your conversation history, and verify changes/fixes for security issues. mcp dot asterisk dot so

Introducing Asterisk MCP - An MCP server that fixes security vulnerabilities while you vibe code. Supports Cursor, Windsurf, Cline, Claude, and any IDE that supports the model context protocol. It can perform codebase-wide scans, analyze snippets in your conversation history, and verify changes/fixes for security issues. mcp dot asterisk dot so

mufeed vh

14,353 views • 1 year ago

introducing greptile security agent it combines static analysis, sca, and ai agents to efficiently catch security flaws before merge. why did we build this? - coding agents have caused the frequency of security incidents to explode - neither agents nor deterministic methods alone are sufficient for detecting vulnerabilities - security review is best done in conjunction with regular code review because many vulns are really just logical issues with security consequences security review is turned on by default for free for all greptile users.

introducing greptile security agent it combines static analysis, sca, and ai agents to efficiently catch security flaws before merge. why did we build this? - coding agents have caused the frequency of security incidents to explode - neither agents nor deterministic methods alone are sufficient for detecting vulnerabilities - security review is best done in conjunction with regular code review because many vulns are really just logical issues with security consequences security review is turned on by default for free for all greptile users.

Daksh Gupta

33,973 views • 18 days ago

$OpenAI Greg Brockman says the fraction of code not written by AI is vanishing With the right context and structure, the actual coding is already better handled by AI than by humans "what's left for human experts is the architecture" But the actual writing of code is essentially all AI now$

OpenAI Greg Brockman says the fraction of code not written by AI is vanishing With the right context and structure, the actual coding is already better handled by AI than by humans "what's left for human experts is the architecture" But the actual writing of code is essentially all AI now

Haider.

11,078 views • 3 months ago

Creator of C++, Bjarne Stroustrup: AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate "senior developers are already retiring rather than deal with it" The problem is that even a small prompt change can shift the entire codebase in unpredictable ways

Creator of C++, Bjarne Stroustrup: AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate "senior developers are already retiring rather than deal with it" The problem is that even a small prompt change can shift the entire codebase in unpredictable ways

Haider.

1,749,780 views • 2 months ago

Anthropic CISO just told you that 90% of their code is written by Claude. Then he explained how they protect their own secrets while doing it. Why your .env file is the weakest link in your entire AI workflow? Watch it, then grab the full security config below👇

Anthropic CISO just told you that 90% of their code is written by Claude. Then he explained how they protect their own secrets while doing it. Why your .env file is the weakest link in your entire AI workflow? Watch it, then grab the full security config below👇

darkzodchi

451,023 views • 3 months ago

We've been tracking AI code review tools across OSS, and a new category is emerging. We're calling it "Deep Review": → Standard AI review: PR-level, fast, human in the loop → Deep Review: repo-wide context, runs autonomously in the background 🧵👇

We've been tracking AI code review tools across OSS, and a new category is emerging. We're calling it "Deep Review": → Standard AI review: PR-level, fast, human in the loop → Deep Review: repo-wide context, runs autonomously in the background 🧵👇

Martian

40,887 views • 4 months ago

Never done eval-driven-development? It's an incredible dev loop that gives you instant feedback on how good your context engineering is. Watch me work on a Claude Code-style askForClarification tool:

Never done eval-driven-development? It's an incredible dev loop that gives you instant feedback on how good your context engineering is. Watch me work on a Claude Code-style askForClarification tool:

Matt Pocock

88,711 views • 9 months ago

$CRWD launched Project QuiltWorks which is an AI security coalition with $IBM, OpenAI and Accenture focused on securing production code from AI-driven threats. Software is getting built faster which means the attack surface is scaling faster too and security has to keep up.

$CRWD launched Project QuiltWorks which is an AI security coalition with $IBM, OpenAI and Accenture focused on securing production code from AI-driven threats. Software is getting built faster which means the attack surface is scaling faster too and security has to keep up.

Shay Boloor

19,228 views • 3 months ago

Anthropic's head of security: "90% of our code is written by Claude. If yours is too and nobody's reviewing it, you're shipping bugs you'll never notice." In 28 minutes he shows the exact security setup Anthropic uses internally to protect their own projects. Watch the full interview, then save the config below 👇

Anthropic's head of security: "90% of our code is written by Claude. If yours is too and nobody's reviewing it, you're shipping bugs you'll never notice." In 28 minutes he shows the exact security setup Anthropic uses internally to protect their own projects. Watch the full interview, then save the config below 👇

darkzodchi

535,705 views • 2 months ago

Web3 security is due for an upgrade - only 1 in 20 protocols run 𝐫𝐞𝐚𝐥-𝐭𝐢𝐦𝐞 𝐦𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠. While audits catch code issues, most attacks exploit protocols 𝐩𝐨𝐬𝐭-𝐝𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭. We built Guardrail as the real-time security platform for web3 👇

Web3 security is due for an upgrade - only 1 in 20 protocols run 𝐫𝐞𝐚𝐥-𝐭𝐢𝐦𝐞 𝐦𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠. While audits catch code issues, most attacks exploit protocols 𝐩𝐨𝐬𝐭-𝐝𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭. We built Guardrail as the real-time security platform for web3 👇

Guardrail

42,679,938 views • 1 year ago

OpenAI is focused on “AI safety” while falling very short on AI security. This incident is a *security* problem that requires *security* solutions. And if there’s anything to learn from it, we need the audit log.

OpenAI is focused on “AI safety” while falling very short on AI security. This incident is a security problem that requires security solutions. And if there’s anything to learn from it, we need the audit log.

Zack Korman

17,258 views • 23 days ago

COP29 is a chance for Britain to show climate leadership on the global stage. This government believes that climate security is national security. Behind the scenes earlier this week 👇

COP29 is a chance for Britain to show climate leadership on the global stage. This government believes that climate security is national security. Behind the scenes earlier this week 👇

Ed Miliband

326,824 views • 1 year ago

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

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,861 views • 7 months ago

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.

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 views • 8 months ago

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:

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,570 views • 10 months ago

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.

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 views • 8 months ago

Head of Engineering Shopify: "AI writes the code, AI reviews the code. Your job is just to write the loops around it." 26 minutes on how AI changed the way 3,000 engineers work inside a single company. Ignoring it while everyone else uses AI to do more is the fastest way to fall behind. Watch it, then read the step by step guide on loops below.

Head of Engineering Shopify: "AI writes the code, AI reviews the code. Your job is just to write the loops around it." 26 minutes on how AI changed the way 3,000 engineers work inside a single company. Ignoring it while everyone else uses AI to do more is the fastest way to fall behind. Watch it, then read the step by step guide on loops below.

Anatoli Kopadze

714,336 views • 1 month ago