Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

1/ Reviewing agent-written code usually comes down to reading a diff and hoping. That is the part of the workflow nobody solved. The models got very good at producing code, and the burden quietly moved to the person who has to decide whether it is safe to merge. You...

kimmonismus's profile picture

Chubby♨️

134,618 subscribers

14,436 görüntüleme • 2 gün önce •via X (Twitter)

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

The part people sleep on: ask your agent to help manage the portfolio after it's built. Set conditions, run it on a schedule, have it flag anything worth your attention. You get a push notification every time it trades and real-time P&L in the app, so you're never out of the loop.
0:50

The part people sleep on: ask your agent to help manage the portfolio after it's built. Set conditions, run it on a schedule, have it flag anything worth your attention. You get a push notification every time it trades and real-time P&L in the app, so you're never out of the loop.

Robinhood

83,270 görüntüleme • 1 ay önce

XBOW raised $117M to build AI hacking agents. Now someone just open-sourced it for FREE. Strix deploys autonomous AI agents that act like real hackers - they run your code dynamically, find vulnerabilities, and validate them through actual proof-of-concepts. Why it matters: The biggest problem with traditional security testing is that it doesn't keep up with development speed. Strix solves this by integrating directly into your workflow: ↳ Run it in CI/CD to catch vulnerabilities before production ↳ Get real proof-of-concepts, not false positives from static analysis ↳ Test everything: injection attacks, access control, business logic flaws The best part? You don't need to be a security expert. Strix includes a complete hacker toolkit - HTTP proxy, browser automation, and Python runtime for exploit development. It's like having a security team that works at the speed of your CI/CD pipeline. The best part is that the tool runs locally in Docker containers, so your code never leaves your environment. Getting started is simple: - pipx install strix-agent - Point it at your codebase (app, repo, or directory) Everything is 100% open-source! I've shared link to the GitHub repo in the replies!
0:23

XBOW raised $117M to build AI hacking agents. Now someone just open-sourced it for FREE. Strix deploys autonomous AI agents that act like real hackers - they run your code dynamically, find vulnerabilities, and validate them through actual proof-of-concepts. Why it matters: The biggest problem with traditional security testing is that it doesn't keep up with development speed. Strix solves this by integrating directly into your workflow: ↳ Run it in CI/CD to catch vulnerabilities before production ↳ Get real proof-of-concepts, not false positives from static analysis ↳ Test everything: injection attacks, access control, business logic flaws The best part? You don't need to be a security expert. Strix includes a complete hacker toolkit - HTTP proxy, browser automation, and Python runtime for exploit development. It's like having a security team that works at the speed of your CI/CD pipeline. The best part is that the tool runs locally in Docker containers, so your code never leaves your environment. Getting started is simple: - pipx install strix-agent - Point it at your codebase (app, repo, or directory) Everything is 100% open-source! I've shared link to the GitHub repo in the replies!

Akshay 🚀

96,762 görüntüleme • 9 ay önce

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch
35:25

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

193,721 görüntüleme • 4 ay önce

You probably know OpenClaw🦞, one of the fastest-growing open-source projects around. An OpenClaw harness lets you build, code, analyze, and take real control of your machine. But the more access an agent has to your machine, the more it matters where your data goes & who can see it. With QVAC, you can run your OpenClaw agent fully on your own machine in a few minutes. Nothing leaves your computer. Full setup guide on the blog, see first comment below. 💡 Pro tip: already running OpenClaw? Send the blog article to your agent and let the it do the set up.
1:44

You probably know OpenClaw🦞, one of the fastest-growing open-source projects around. An OpenClaw harness lets you build, code, analyze, and take real control of your machine. But the more access an agent has to your machine, the more it matters where your data goes & who can see it. With QVAC, you can run your OpenClaw agent fully on your own machine in a few minutes. Nothing leaves your computer. Full setup guide on the blog, see first comment below. 💡 Pro tip: already running OpenClaw? Send the blog article to your agent and let the it do the set up.

QVAC

15,019,651 görüntüleme • 2 ay önce

Build it once. Earn every time someone uses it. Wrap your workflow with input and output nodes, hit publish, and your one-click app goes live to millions of creators. You choose how it lives: Keep it private, share with your team, or let the whole community run it. And every single time someone runs your app? Credits land in your account. No extra work. No maintenance. Just your creativity quietly paying you back, on repeat. Your workflow. Your rules. Your credits.
0:40

Build it once. Earn every time someone uses it. Wrap your workflow with input and output nodes, hit publish, and your one-click app goes live to millions of creators. You choose how it lives: Keep it private, share with your team, or let the whole community run it. And every single time someone runs your app? Credits land in your account. No extra work. No maintenance. Just your creativity quietly paying you back, on repeat. Your workflow. Your rules. Your credits.

ImagineArt

323,644 görüntüleme • 3 ay önce

The biggest marketplace on Earth won't be the assets humans own. It'll be the data AI needs. Everything that can be digitised is getting pulled in to train the next models. Every scientific dataset, every piece of research sitting in a university, every sensor reading off every John Deere tractor in a field. All of it feeds the machine, and almost none of it is visible to us. What comes out is an agentic economy running at machine speed. You plug your data into a vault, and agents monetise it on your behalf, trading with other agents in real time, in a marketplace we never see. The company sitting on proprietary data becomes part of it without even knowing. This is what the Economic Singularity actually looks like from the inside. The real economy stops being the one we can see and price, and moves somewhere we can't follow. You own a piece of it, or you get priced out of it. Jordi Visser.
1:27

The biggest marketplace on Earth won't be the assets humans own. It'll be the data AI needs. Everything that can be digitised is getting pulled in to train the next models. Every scientific dataset, every piece of research sitting in a university, every sensor reading off every John Deere tractor in a field. All of it feeds the machine, and almost none of it is visible to us. What comes out is an agentic economy running at machine speed. You plug your data into a vault, and agents monetise it on your behalf, trading with other agents in real time, in a marketplace we never see. The company sitting on proprietary data becomes part of it without even knowing. This is what the Economic Singularity actually looks like from the inside. The real economy stops being the one we can see and price, and moves somewhere we can't follow. You own a piece of it, or you get priced out of it. Jordi Visser.

Raoul Pal

79,047 görüntüleme • 28 gün önce

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below
36:48

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anatoli Kopadze

28,042 görüntüleme • 2 ay önce

Your AI agent is writing code nobody reviewed and running it on your machine. Most teams answer "where does it run" with a container and a hope. Introducing CreateOS Sandbox. Run code you cannot trust, with the networking, egress control, and self-hosting you need. 🧵
0:20

Your AI agent is writing code nobody reviewed and running it on your machine. Most teams answer "where does it run" with a container and a hope. Introducing CreateOS Sandbox. Run code you cannot trust, with the networking, egress control, and self-hosting you need. 🧵

CreateOS

13,874 görüntüleme • 1 ay önce

If you're new to apps, you need to use XcodeBuildMCP. It takes all the rough edges out of working with Codex or Claude Code and Xcode. Your agent can build and run your app, and even check the UI to see if it looks good via Apple Accessibility APIs.
51:52

If you're new to apps, you need to use XcodeBuildMCP. It takes all the rough edges out of working with Codex or Claude Code and Xcode. Your agent can build and run your app, and even check the UI to see if it looks good via Apple Accessibility APIs.

Paul Solt

53,825 görüntüleme • 7 ay önce

Comfy MCP is now local and open-source! The #1 ask after Comfy Cloud MCP shipped in June. Your agent sees your actual install. So every node, custom nodes included, and every model on disk. It fetches files, starts your instance, gets a workflow to the point where it runs. It is now the easiest way to help with your local Minimax H3 workflows! Cloud MCP still does everything it did. Tell your agent where a job goes, or let it decide.
0:20

Comfy MCP is now local and open-source! The #1 ask after Comfy Cloud MCP shipped in June. Your agent sees your actual install. So every node, custom nodes included, and every model on disk. It fetches files, starts your instance, gets a workflow to the point where it runs. It is now the easiest way to help with your local Minimax H3 workflows! Cloud MCP still does everything it did. Tell your agent where a job goes, or let it decide.

ComfyUI

154,765 görüntüleme • 2 gün ö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 • 3 ay önce

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.
1:54

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.

Milind S

12,409 görüntüleme • 1 ay önce

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.
1:03

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.

Steve (Builder.io)

148,260 görüntüleme • 1 ay önce

We're making a 90-min feature film. Real actors, real sets, real crew, and AI filling in only what the budget can't cover. The one thing we don't have yet is a script. If you've written one, polished it, pitched it, and watched it go nowhere, we want to read it. If we love it, we buy it, and you're in on the whole thing. We want to build it with people who care about it, as much as we do. The whole production runs in public - every workflow, every breakthrough, every failure. The script you stopped pitching might be the one that finally gets made. Don't let it sit in a drawer. Send it over.
0:53

We're making a 90-min feature film. Real actors, real sets, real crew, and AI filling in only what the budget can't cover. The one thing we don't have yet is a script. If you've written one, polished it, pitched it, and watched it go nowhere, we want to read it. If we love it, we buy it, and you're in on the whole thing. We want to build it with people who care about it, as much as we do. The whole production runs in public - every workflow, every breakthrough, every failure. The script you stopped pitching might be the one that finally gets made. Don't let it sit in a drawer. Send it over.

Invideo

68,626 görüntüleme • 1 ay önce

Do you read a lot of books but feel like nothing in your life has changed? If so do this: Every time you finish a chapter, write down 1 key lesson you learned and apply it within the week. Keep it simple and aim to apply one lesson at a time. Trying to apply too many lessons at once can get overwhelming and cause you to give up on all of them. Remember the goal of reading is knowledge application NOT knowledge acquisition. As Alex Hormozi says, "If you read something, and your behavior doesn’t change, it means you didn’t learn anything." What do you think about this reading tip?
0:37

Do you read a lot of books but feel like nothing in your life has changed? If so do this: Every time you finish a chapter, write down 1 key lesson you learned and apply it within the week. Keep it simple and aim to apply one lesson at a time. Trying to apply too many lessons at once can get overwhelming and cause you to give up on all of them. Remember the goal of reading is knowledge application NOT knowledge acquisition. As Alex Hormozi says, "If you read something, and your behavior doesn’t change, it means you didn’t learn anything." What do you think about this reading tip?

Alex & Books 📚

129,500 görüntüleme • 3 yıl önce

PulseX is so cool! For those of you that didn't know. PulseX is one of the most decentralized DEXs in existence. You can literally run it locally on your own machine and it's so simple to set up. Running it on your own machine makes it faster, more secure, safer, more censorship resistant and protects your privacy. There's no reason you should be using the web version when you have the desktop version available. I made a short video showing you how to download it. Here is the link to the PulseX download page (always triple check links, even from me)
4:10

PulseX is so cool! For those of you that didn't know. PulseX is one of the most decentralized DEXs in existence. You can literally run it locally on your own machine and it's so simple to set up. Running it on your own machine makes it faster, more secure, safer, more censorship resistant and protects your privacy. There's no reason you should be using the web version when you have the desktop version available. I made a short video showing you how to download it. Here is the link to the PulseX download page (always triple check links, even from me)

SHILL GATES

31,941 görüntüleme • 1 yıl önce

"There's a time when the operation of the machine becomes so odious, makes you so sick at heart, that you can't take part. You can't even passively take part." "And you've got to put your bodies upon the gears and upon the wheels, upon the levers, upon all the apparatus, and you've got to make it stop." "And you've got to indicate to the people who run it, to the people who own it, that unless you're free, the machine will be prevented from working at all."
0:26

"There's a time when the operation of the machine becomes so odious, makes you so sick at heart, that you can't take part. You can't even passively take part." "And you've got to put your bodies upon the gears and upon the wheels, upon the levers, upon all the apparatus, and you've got to make it stop." "And you've got to indicate to the people who run it, to the people who own it, that unless you're free, the machine will be prevented from working at all."

illuminatibot

33,052 görüntüleme • 10 ay önce

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