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.

The first open-source implementation of the paper that will change automatic test generation is now available! In February, Meta published a paper introducing a tool to automatically increase test coverage, guaranteeing improvements over an existing code base. This is a big deal, but Meta didn't release the code. Fortunately,... we now have Cover-Agent, an open-source tool you can install that implements Meta's paper to generate unit tests automatically: I recorded a quick video showing Cover-Agent in action. There are two things I want to mention: 1. Automatically generating unit tests is not new, but doing it right is difficult. If you ask ChatGPT to do it, you'll get duplicate, non-working, and meaningless tests that don't improve your code. Meta's solution only generates unique tests that run and increase code coverage. 2. People who write tests before writing the code (TDD) will find this less helpful. That's okay. Not everyone does TDD, but we all need to improve test coverage. There are many good and bad applications of AI, but this is one I'm looking forward to make part of my life.show more

Santiago

452,940 subscribers

774,554 views • 2 years ago •via X (Twitter)

Science & Technology Education Health & Wellness

Anya Rossi• Live Now

Private livecam show

10 Comments

Itamar Friedman2 years ago

Hey 👋, one of the Cover-Agent creators here. I've recorded 5 minutes video explaining and reviewing TestGen-LLM and Cover-Agent:

Santiago2 years ago

Great job and thank you!

Sam Francisco2 years ago

It's 630 why are you giving me more work already Santiago I haven't even had my coffee yet

Santiago2 years ago

lol

Alex Dillon | Quality Advocate2 years ago

As someone very much involved in testing, this is quite interesting to me. I want to look more into it and explore the quality of the tests. Though, I’m a bit skeptical that this will be replacing someone having to write these tests, the hope is that it at least provides a good starting point for someone.

Graham Cox (@grahamcox82.bsky.social)2 years ago

I'm curious - how does the tool know what the correct behaviour is? Or does it assume that the current implementation is already correct? (Which, to be fair, is how things like Jest snapshots work anyway)

Shikhar Srivastava2 years ago

As someone who doesn’t like TDD..

Pradeep Gowda2 years ago

@ponnappa fyi

Markus Odenthal2 years ago

This can be especially helpful for ML projects. I usually write tests when I bring my product to production, not when starting the project. So this would be a huge time-saver, thanks for sharing.

SwissTechMind2 years ago

So, if I understand correctly, the primary purpose of these tests is to safeguard against unintentional changes, right?

Related Videos

🚀 Introducing Cover-Agent 🧪 An open-source tool that includes a reimplementation of Meta's TestGen-LLM for automatically enhancing test suites. Manager: "We must improve old test suites for better code coverage. Can you handle it?" Me: "Sure, my favorite task... (Not!) 🤷‍♂️" Meta's team had the idea of using LLMs to enhance test suites—sounds great, right? But they didn't release their code We did. We'd love your feedback as we work on improving this baseline In this video, I'll review TestGen-LLM, share insights, and introduce you to Cover-Agent

🚀 Introducing Cover-Agent 🧪 An open-source tool that includes a reimplementation of Meta's TestGen-LLM for automatically enhancing test suites. Manager: "We must improve old test suites for better code coverage. Can you handle it?" Me: "Sure, my favorite task... (Not!) 🤷‍♂️" Meta's team had the idea of using LLMs to enhance test suites—sounds great, right? But they didn't release their code We did. We'd love your feedback as we work on improving this baseline In this video, I'll review TestGen-LLM, share insights, and introduce you to Cover-Agent

Itamar Friedman

139,228 views • 2 years ago

Zuckerberg says Meta's Llama race changes in the next 12-18 months: most of the code will be written by AI - not autocomplete, but agents that run tests and improve the model loop. "We're not trying to build a general developer tool. We are trying to build a coding agent and an AI research agent that basically advances Llama research specifically." "Sometime in the next 12 to 18 months, we'll reach the point where most of the code that's going towards these efforts is written by AI." "And I don't mean autocomplete." "I'm talking more like you give it a goal, it can run tests, it can improve things, it can find issues." "It writes higher quality code than the average very good person on the team already." The hidden bottleneck is not chat UX. It is closing the loop between AI research, code, tests, and self-improvement inside the lab.

Zuckerberg says Meta's Llama race changes in the next 12-18 months: most of the code will be written by AI - not autocomplete, but agents that run tests and improve the model loop. "We're not trying to build a general developer tool. We are trying to build a coding agent and an AI research agent that basically advances Llama research specifically." "Sometime in the next 12 to 18 months, we'll reach the point where most of the code that's going towards these efforts is written by AI." "And I don't mean autocomplete." "I'm talking more like you give it a goal, it can run tests, it can improve things, it can find issues." "It writes higher quality code than the average very good person on the team already." The hidden bottleneck is not chat UX. It is closing the loop between AI research, code, tests, and self-improvement inside the lab.

Karl Mehta

36,337 views • 1 month ago

🇺🇸 SEC. DUFFY: THERE IS SHADY BEHAVIOR BEHIND CALIFORNIA COMMERCIAL DRIVER LICENSE TESTS "In regard to California, it is a requirement that when you get your CDL, you have to take the test in English and you also have a skills test. There is no way in hell this guy could have passed those tests but for some really shady behavior in California. We are investigating and looking at this. And by the way, let Gavin come play, but he will regret the day he messes with DOT.” Source: Secretary Sean Duffy Laura Ingraham

🇺🇸 SEC. DUFFY: THERE IS SHADY BEHAVIOR BEHIND CALIFORNIA COMMERCIAL DRIVER LICENSE TESTS "In regard to California, it is a requirement that when you get your CDL, you have to take the test in English and you also have a skills test. There is no way in hell this guy could have passed those tests but for some really shady behavior in California. We are investigating and looking at this. And by the way, let Gavin come play, but he will regret the day he messes with DOT.” Source: Secretary Sean Duffy Laura Ingraham

Mario Nawfal

44,664 views • 11 months ago

Nothing beats open-source! We now have a fully open-source coding agent that can compete with any proprietary solution out there: • 500+ available models • It doesn't train on your code • It doesn't charge a penny for tokens • It's open. You can change if you want. Kilo Code is the #1 app on OpenRouter right now, and the community is releasing new features on GitHub at rocket speed (about 20 releases in the last 30 days). I installed it in Visual Studio Code, but you can install it in pretty much any IDE. I need to spend more time with it, but here is a very interesting design choice: Most coding agents support two modes: an "agentic" mode for writing code and an "ask" mode for talking to the model without making any changes. Kilo Code supports 5 different modes: 1. Architect mode - Research, design, and planning 2. Debug mode - Problem solving and troubleshooting 3. Code mode - To write code. 4. Ask mode - To talk to the model. 5. Orchestrator mode - Combine every agent to solve problems. On paper, I really like this. I'll need more time to try out the specialized agents and see whether niching becomes an advantage. Here is the link to the website: Thanks to the Kilo for partnering with me on this post.

Nothing beats open-source! We now have a fully open-source coding agent that can compete with any proprietary solution out there: • 500+ available models • It doesn't train on your code • It doesn't charge a penny for tokens • It's open. You can change if you want. Kilo Code is the #1 app on OpenRouter right now, and the community is releasing new features on GitHub at rocket speed (about 20 releases in the last 30 days). I installed it in Visual Studio Code, but you can install it in pretty much any IDE. I need to spend more time with it, but here is a very interesting design choice: Most coding agents support two modes: an "agentic" mode for writing code and an "ask" mode for talking to the model without making any changes. Kilo Code supports 5 different modes: 1. Architect mode - Research, design, and planning 2. Debug mode - Problem solving and troubleshooting 3. Code mode - To write code. 4. Ask mode - To talk to the model. 5. Orchestrator mode - Combine every agent to solve problems. On paper, I really like this. I'll need more time to try out the specialized agents and see whether niching becomes an advantage. Here is the link to the website: Thanks to the Kilo for partnering with me on this post.

Santiago

73,062 views • 8 months ago

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Tibor Blaho

136,055 views • 1 year ago

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

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

There's a new AI-native IDE out there named Aide, and there are four things I like about it: 1. It's open-source 2. It's proactive and suggests changes before you ask 3. It uses an intermediate layer between the editor and LLM 4. It's SOTA on the SWE-Bench benchmark I'm excited about #3 because this layer (called "Sidecar") will help people connect any model to the IDE. While this isn't possible right now, it's clearly the goal. Sidecar is also open-source. As I write this, the code agent behind Aide, "CodeStory Midwit Agent," is second in the Verified SWE-Bench leaderboard (it finished in 2024 in the first place.) This is a huge deal! If I'm gonna have an agent help me code, it might as well be the best of the best. The proactive aspect is also cool: the IDE provides suggestions to improve your code without you having to ask. I recorded a quick video showing you how Aide works. The team behind the IDE partnered with me on this video. Right now, it feels like *everyone* is building AI-powered coding tools. As a career developer, nothing excites me more than seeing how quickly we transform the development experience. And 2025 is just getting started!

There's a new AI-native IDE out there named Aide, and there are four things I like about it: 1. It's open-source 2. It's proactive and suggests changes before you ask 3. It uses an intermediate layer between the editor and LLM 4. It's SOTA on the SWE-Bench benchmark I'm excited about #3 because this layer (called "Sidecar") will help people connect any model to the IDE. While this isn't possible right now, it's clearly the goal. Sidecar is also open-source. As I write this, the code agent behind Aide, "CodeStory Midwit Agent," is second in the Verified SWE-Bench leaderboard (it finished in 2024 in the first place.) This is a huge deal! If I'm gonna have an agent help me code, it might as well be the best of the best. The proactive aspect is also cool: the IDE provides suggestions to improve your code without you having to ask. I recorded a quick video showing you how Aide works. The team behind the IDE partnered with me on this video. Right now, it feels like everyone is building AI-powered coding tools. As a career developer, nothing excites me more than seeing how quickly we transform the development experience. And 2025 is just getting started!

Santiago

69,422 views • 1 year ago

Nothing beats Augment Code answering questions about large codebases. It's a free extension (works in VSCode, JetBrains, and NeoVim), and has a community edition you can run for free forever. Try this experiment: 1. Download any large open-source project from GitHub 2. Augment will index the code 3. Start asking questions about the codebase 4. Do the same using any other coding agent 5. Compare the speed and the depth of the answers you get If you have a small codebase, the differences with other coding agents won't be obvious, but if you are working on a large project, things will click immediately. Suggestion: download the Keras repository (~180,000 lines of code). I know the library well, and the answers I got from Augment were pretty impressive. By the way, Augment is a fully-fledged AI coding assistant. You can use its agent in every imaginable way: • To implement brand new functionality • To make quick edits to your code • To refactor existing functionality • To generate unit tests • To generate documentation • To handle GitHub—pull requests, commits, branching, etc My favorite feature is their "Next Edit" functionality: 1. You edit the code 2. Augment analyzes the change (across the entire codebase!) 3. Augment determines the ripple effects of that change 4. Augment suggests everything you need to update Here is a link to the tool: Thanks to the team at Augment Code for partnering with me on this post.

Santiago

34,977 views • 1 year ago

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 views • 5 months ago

Shipping speed is up across the board, and AI tools like Gemini 3 Pro are helping us code and build faster than ever. But validation and quality assurance? Still the bottleneck. That’s why I’m integrating TestSprite into my workflow. It analyzes my code and PRD, automatically builds a comprehensive test layer, and keeps my development flow unbroken. No test writing. No last-minute QA chaos. What it covers: ➞ UI Flow Coverage: Verifies real-time updates and synchronization (e.g., confirming gradient sliders and angle controls work together). ➞ Edge Case Validation: Catches subtle logic bugs like inputs accepting out-of-range values that I'd typically miss. ➞ Functionality Check: Automatically runs videos to ensure core features (like "Randomize" and "Copy to Clipboard") are working. ➞ Repeatable Test Suite: Creates tests I can rerun anytime, giving me confidence that new code hasn't broken the old. My new Antigravity + Test Sprite Loop: ➞ AI Plan & Code: Use Antigravity's Planning Mode with Gemini 3 Pro to generate structured code. ➞ Browser Agent QA: Use Antigravity's Open Browser feature to let the AI visually analyze and control the live UI for quick verification. ➞ Validate & Test: Run the automated, reproducible test suite in Test Sprite. ➞ Ship. This loop feels clean, fast, and robust. Works beautifully alongside Gemini 3 Pro, Cloud Sonet, or any AI stack.

Shipping speed is up across the board, and AI tools like Gemini 3 Pro are helping us code and build faster than ever. But validation and quality assurance? Still the bottleneck. That’s why I’m integrating TestSprite into my workflow. It analyzes my code and PRD, automatically builds a comprehensive test layer, and keeps my development flow unbroken. No test writing. No last-minute QA chaos. What it covers: ➞ UI Flow Coverage: Verifies real-time updates and synchronization (e.g., confirming gradient sliders and angle controls work together). ➞ Edge Case Validation: Catches subtle logic bugs like inputs accepting out-of-range values that I'd typically miss. ➞ Functionality Check: Automatically runs videos to ensure core features (like "Randomize" and "Copy to Clipboard") are working. ➞ Repeatable Test Suite: Creates tests I can rerun anytime, giving me confidence that new code hasn't broken the old. My new Antigravity + Test Sprite Loop: ➞ AI Plan & Code: Use Antigravity's Planning Mode with Gemini 3 Pro to generate structured code. ➞ Browser Agent QA: Use Antigravity's Open Browser feature to let the AI visually analyze and control the live UI for quick verification. ➞ Validate & Test: Run the automated, reproducible test suite in Test Sprite. ➞ Ship. This loop feels clean, fast, and robust. Works beautifully alongside Gemini 3 Pro, Cloud Sonet, or any AI stack.

Dhaval Makwana

110,884 views • 7 months ago

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

Santiago

140,873 views • 7 months ago

This might be the best "AI Engineer" I've tried so far. I'm an old school developer who started 30 years ago. I feel very uncomfortable letting AI take control of my code, but for the sake of science, I spent two hours building an application that took me weeks to build a couple of years ago. I used Pythagora, a brand new tool backed by Y Combinator. They just released to the public. Keep in mind that I use AI every day to write code, but Pythagora is something different: it's a tool that leads, and uses you—the human—as the copilot. I go into more details in the video, but here is the TLDR; 1. Holy molly! We've made a ton of progress on this front! This is way better than Devin when I tested it a few months back. 2. Love the approach of generating a plan with sub-tasks before writing any code. 3. The tools never tries to do too much: it tackles every small task one at a time, and gives you instructions so you test everything. 4. It does exactly what you'd do when it gets stuck: writes a bunch of logs and uses those to correct itself. Pretty neat! 5. It's fast. It runs locally. It's an extension to Visual Studio Code. I'm impressed, but I don't think this tool is for me. I'm not the type of developer who's ready to relinquish control. I felt I had no connection with the code because I didn't write it. It was not my code. I know many people who don't care about this. I know many people who will get tremendous value out of Pythagora. I hope they keep pushing the limits, providing feedback, and helping this get to a point where old folks like me feel more comfortable using it. Don't take my word for it. The best thing you can do is to give it a try and see how you feel using it. Thanks to the team who built this, for all of the explanations and support, and especially, for sitting and listening to my dumb questions for 2 hours while I tested this.

Santiago

211,993 views • 1 year ago

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

"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 views • 5 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,424 views • 7 months ago

"Vibe coding is NOT the same as using AI to write code that's reviewed, tested, and maintained." Here's my new episode with Lee Robinson (Cursor's Head of AI Education) where he shows how to build AI apps properly using planning, test-driven development, agent workflows, and more. Some tips from Lee: 1. Work with AI to create a detailed technical plan upfront including requirements, design preferences, and your preferred tech stack. 2. Ask AI to write tests so that it can check its own work. Add this to the plan: "Write unit tests for business logic, e2e tests for core user journeys." 3. Add "make descriptive commits" to your initial plan so that you can track what AI changed and why. 📌 Watch our beginner-friendly tutorial now: Also available on: Spotify: Apple: Newsletter:

"Vibe coding is NOT the same as using AI to write code that's reviewed, tested, and maintained." Here's my new episode with Lee Robinson (Cursor's Head of AI Education) where he shows how to build AI apps properly using planning, test-driven development, agent workflows, and more. Some tips from Lee: 1. Work with AI to create a detailed technical plan upfront including requirements, design preferences, and your preferred tech stack. 2. Ask AI to write tests so that it can check its own work. Add this to the plan: "Write unit tests for business logic, e2e tests for core user journeys." 3. Add "make descriptive commits" to your initial plan so that you can track what AI changed and why. 📌 Watch our beginner-friendly tutorial now: Also available on: Spotify: Apple: Newsletter:

Peter Yang

108,418 views • 11 months ago

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

How Base44 Beats Cursor: "I don't think you will want to see the code. Nowadays even the most technical users would prefer building inside Base44 instead of Cursor. They do not want to set up servers and databases and see the code and write tests and navigate through the files etc. This portion of software that you can build in Base44 is going to grow. If you can build it inside Base44, you'd prefer to do that than Cursor." Do you agree, people "will not want to see the code" Anton Osika Scott Wu GREG ISENBERG Theo - t3.gg

How Base44 Beats Cursor: "I don't think you will want to see the code. Nowadays even the most technical users would prefer building inside Base44 instead of Cursor. They do not want to set up servers and databases and see the code and write tests and navigate through the files etc. This portion of software that you can build in Base44 is going to grow. If you can build it inside Base44, you'd prefer to do that than Cursor." Do you agree, people "will not want to see the code" Anton Osika Scott Wu GREG ISENBERG Theo - t3.gg

Harry Stebbings

69,563 views • 8 months ago

Open source software is GREAT. But "open source" AI is NOT like software - it's VERY different. Rob Miles cuts through the bullshit: ROB: Oh, hey, Meta. I heard Llama's weights leaked. That's rough, man. Information security's hard. How you holding up? META: Oh, we're great. Yeah, we're fine. We... actually, that was deliberate. We meant to do that. ROB MILES: Oh, really? META: Yeah... well, the second time anyway. It's called open source. Look it up. ROB MILES: Oh. Well, I love free and open source software, but do those principles really apply to network weights? How does that work? META: Open source is good for users because it lets them read the source code and see what the program is really doing and how it works. ROB MILES: Wait, have you found a way to tell how a model works by looking at its weights? META: No. But, it lets developers all over the world spot bugs in the code and submit patches. ROB: Wait, people are fixing bugs in Llama's weights? META: Well, no. People can fine tune it themselves, though. ROB: ?? Other companies offer fine tuning through APIs. ... So, hang on, if you can't actually read the code and know what it's doing, then network weights are effectively a compiled binary. So, in what sense is this open source? Why not call it like public weights? Why call it open source at all? META: I love open source. ROB: Well, I know a lot of your employees do, but you don't love anything. You're a giant corporation. What's in it for you? META: I love, love open source.

Open source software is GREAT. But "open source" AI is NOT like software - it's VERY different. Rob Miles cuts through the bullshit: ROB: Oh, hey, Meta. I heard Llama's weights leaked. That's rough, man. Information security's hard. How you holding up? META: Oh, we're great. Yeah, we're fine. We... actually, that was deliberate. We meant to do that. ROB MILES: Oh, really? META: Yeah... well, the second time anyway. It's called open source. Look it up. ROB MILES: Oh. Well, I love free and open source software, but do those principles really apply to network weights? How does that work? META: Open source is good for users because it lets them read the source code and see what the program is really doing and how it works. ROB MILES: Wait, have you found a way to tell how a model works by looking at its weights? META: No. But, it lets developers all over the world spot bugs in the code and submit patches. ROB: Wait, people are fixing bugs in Llama's weights? META: Well, no. People can fine tune it themselves, though. ROB: ?? Other companies offer fine tuning through APIs. ... So, hang on, if you can't actually read the code and know what it's doing, then network weights are effectively a compiled binary. So, in what sense is this open source? Why not call it like public weights? Why call it open source at all? META: I love open source. ROB: Well, I know a lot of your employees do, but you don't love anything. You're a giant corporation. What's in it for you? META: I love, love open source.

AI Notkilleveryoneism Memes ⏸️

107,362 views • 2 years ago