Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

Today, I'm excited to launch Entelligence AI DeepReviews, the next generation AI-powered code reviews. Vibe coded PRs are not production ready often creating more subtle bugs throughout the codebase than before. Entelligence fixes this by understanding the entire codebase and flags bugs, regressions, and breakages across files before you... show more

Aiswarya Sankar

10,234 subscribers

96,309 Aufrufe • vor 1 Jahr •via X (Twitter)

Wissenschaft & Technologie Nachrichten & Politik Bildung

Anya Rossi• Live Now

Private livecam show

12 Kommentare

Profilbild von Csaba Kissi

Csaba Kissivor 1 Jahr

@EntelligenceAI This can save a ton of time for teams.

Profilbild von The Crypto Digest

The Crypto Digestvor 1 Jahr

🚀Get the top YouTube crypto influencers summarized and delivered straight to your inbox. No more searching—just the best insights, powered by AI. 📊 🔓 Subscribe now for exclusive weekly updates and elevate your crypto game! 🚀 👉

Profilbild von Abhay

Abhayvor 1 Jahr

@EntelligenceAI Insane launch 🚀

Profilbild von Aiswarya Sankar

Aiswarya Sankarvor 1 Jahr

@EntelligenceAI thanks @abhaykondi !

Profilbild von AshutoshShrivastava

AshutoshShrivastavavor 1 Jahr

@EntelligenceAI Congrats on the launch Aiswarya . This will be really helpful for vibe coders.

Profilbild von Apoorv | Plxity

Apoorv | Plxityvor 1 Jahr

@EntelligenceAI congratulations on the launch 🚀

Profilbild von Nithin Bose

Nithin Bosevor 1 Jahr

@EntelligenceAI DeepReviews balances Vibecoding. Such a vital element to dev lifecycles

Profilbild von Christopher Settles

Christopher Settlesvor 1 Jahr

@EntelligenceAI Super helpful for software teams to be able to check over the details, even if OpenAI works out of the box

Profilbild von Aiswarya Sankar

Aiswarya Sankarvor 1 Jahr

@EntelligenceAI Agreed! Vibe coded PRs often have way more errors than eng written PRs

Profilbild von Ghandeepan M

Ghandeepan Mvor 1 Jahr

@EntelligenceAI Congrats on the Launch and many more to come ✌️

Profilbild von sabir hussain

sabir hussainvor 1 Jahr

@EntelligenceAI This is the best for developers and developers must see this

Profilbild von Aiswarya Sankar

Aiswarya Sankarvor 1 Jahr

@EntelligenceAI thanks @sabir_huss50540 !

Ähnliche Videos

introducing knowledge bases. greptile maintains detailed docs about how your codebase works, and uses them during review. for each part of the codebase, it maintains a running list of past bugs. this way, the next time it reviews that part of the code, it knows what to look for. greptile catches 12.2% more bugs with knowledge bases enabled! now available to all users :)

introducing knowledge bases. greptile maintains detailed docs about how your codebase works, and uses them during review. for each part of the codebase, it maintains a running list of past bugs. this way, the next time it reviews that part of the code, it knows what to look for. greptile catches 12.2% more bugs with knowledge bases enabled! now available to all users :)

Daksh Gupta

29,296 Aufrufe • vor 5 Tagen

AI has completely changed how code gets written. Models can now generate thousands of lines in minutes. That speed is exciting but it also creates a new problem... reviews are slow. Context is missing. Bugs slip through. The bottleneck isn’t writing code anymore, it’s understanding and shipping it safely. It’s why I’ve been looking closely at tools built AI-first for this stage of the workflow. One that stands out is Graphite Agent. It sits inside your PRs and does what reviews have always struggled with at scale: → Explains logic line-by-line → Surfaces and fixes bugs → Resolves failing checks in context All without leaving the review flow.

AI has completely changed how code gets written. Models can now generate thousands of lines in minutes. That speed is exciting but it also creates a new problem... reviews are slow. Context is missing. Bugs slip through. The bottleneck isn’t writing code anymore, it’s understanding and shipping it safely. It’s why I’ve been looking closely at tools built AI-first for this stage of the workflow. One that stands out is Graphite Agent. It sits inside your PRs and does what reviews have always struggled with at scale: → Explains logic line-by-line → Surfaces and fixes bugs → Resolves failing checks in context All without leaving the review flow.

Shruti

49,398 Aufrufe • vor 10 Monaten

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

54,703 Aufrufe • vor 1 Monat

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

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

Santiago

48,783 Aufrufe • vor 1 Jahr

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,637 Aufrufe • vor 11 Monaten

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,438 Aufrufe • vor 8 Monaten

Most AI app builders can generate a prototype. The real question is: Can they generate something you can actually launch? I recently explored MeDo, an AI-powered full-stack app generation platform that goes beyond just creating a frontend. With a single prompt, it can generate the frontend UI, backend logic, database structure, and plugin integrations. All in one workflow, without requiring coding or deployment experience. What stood out to me is the focus on building real products rather than simple demos. Whether you're creating SaaS tools, internal dashboards, e-commerce applications, games, or business automation tools. the goal is to move from idea → working product as quickly as possible. A few notable features: ✅ Full-stack generation from a single prompt ✅ Plugin ecosystem with integrations like Stripe and AI tools ✅ Auto bug-fixing capabilities ✅ Website cloning from screenshots ✅ Built-in UI enhancement options ✅ Marketplace of ready-made apps you can customize The AI app builder space is becoming increasingly competitive, and platforms are starting to differentiate themselves based on how close they get to a production-ready result rather than just generating code. For builders, founders, and creators exploring no-code AI development, it's an interesting category worth watching. Try it today and launch your next project with just a prompt:

Most AI app builders can generate a prototype. The real question is: Can they generate something you can actually launch? I recently explored MeDo, an AI-powered full-stack app generation platform that goes beyond just creating a frontend. With a single prompt, it can generate the frontend UI, backend logic, database structure, and plugin integrations. All in one workflow, without requiring coding or deployment experience. What stood out to me is the focus on building real products rather than simple demos. Whether you're creating SaaS tools, internal dashboards, e-commerce applications, games, or business automation tools. the goal is to move from idea → working product as quickly as possible. A few notable features: ✅ Full-stack generation from a single prompt ✅ Plugin ecosystem with integrations like Stripe and AI tools ✅ Auto bug-fixing capabilities ✅ Website cloning from screenshots ✅ Built-in UI enhancement options ✅ Marketplace of ready-made apps you can customize The AI app builder space is becoming increasingly competitive, and platforms are starting to differentiate themselves based on how close they get to a production-ready result rather than just generating code. For builders, founders, and creators exploring no-code AI development, it's an interesting category worth watching. Try it today and launch your next project with just a prompt:

Markandey Sharma

49,777 Aufrufe • vor 2 Monaten

This is the future of terminals!!! Tell the terminal what to do in English and let it execute the commands for you. No need to search for and remember esoteric commands anymore. Create projects from scratch, review your PRs and start projects simply by using English. Warp 🤖 takes the terminal to the next level. 1. Review code changes This prompt reviews my code changes before pushing them to the remote branch. It even takes parameters for extra context such as: - my coding style guide - the existing pull request link - the technologies used

This is the future of terminals!!! Tell the terminal what to do in English and let it execute the commands for you. No need to search for and remember esoteric commands anymore. Create projects from scratch, review your PRs and start projects simply by using English. Warp 🤖 takes the terminal to the next level. 1. Review code changes This prompt reviews my code changes before pushing them to the remote branch. It even takes parameters for extra context such as: - my coding style guide - the existing pull request link - the technologies used

Catalin

32,199 Aufrufe • vor 1 Jahr

🚨 AI coding agents hallucinate because they can't actually read your codebase. This MCP server fixes that. It's called Context+ and it gives AI 99% accuracy on large-scale engineering projects by building a real semantic map of your code before touching a single line. Here's what makes it different from every other MCP tool: → Tree-sitter AST parsing across 43 file extensions. Not grep. Not regex. Actual syntax trees. → Spectral Clustering that groups semantically related files into labeled clusters. Your AI finally understands what belongs together. → Obsidian-style wikilinks that map features to code files. Navigate entire codebases like a knowledge graph. → Blast radius tracing. Before any change, it shows every file and line where a symbol is imported or used. No more orphaned references. → Shadow restore points. Every AI-proposed commit creates a restore snapshot. One command to undo any change without touching git history. → Semantic search by meaning. Ask what something does. Not what it's called. The `propose_commit` tool is the wild part. It validates changes against strict rules, creates a shadow restore point, and only then writes to disk. AI can't just freestyle your production code. Works with Claude Code, Cursor, VS Code, and Windsurf. One line to install with bunx or npx. This is what responsible AI coding infrastructure actually looks like. 100% Opensource. Link in comments.

🚨 AI coding agents hallucinate because they can't actually read your codebase. This MCP server fixes that. It's called Context+ and it gives AI 99% accuracy on large-scale engineering projects by building a real semantic map of your code before touching a single line. Here's what makes it different from every other MCP tool: → Tree-sitter AST parsing across 43 file extensions. Not grep. Not regex. Actual syntax trees. → Spectral Clustering that groups semantically related files into labeled clusters. Your AI finally understands what belongs together. → Obsidian-style wikilinks that map features to code files. Navigate entire codebases like a knowledge graph. → Blast radius tracing. Before any change, it shows every file and line where a symbol is imported or used. No more orphaned references. → Shadow restore points. Every AI-proposed commit creates a restore snapshot. One command to undo any change without touching git history. → Semantic search by meaning. Ask what something does. Not what it's called. The `propose_commit` tool is the wild part. It validates changes against strict rules, creates a shadow restore point, and only then writes to disk. AI can't just freestyle your production code. Works with Claude Code, Cursor, VS Code, and Windsurf. One line to install with bunx or npx. This is what responsible AI coding infrastructure actually looks like. 100% Opensource. Link in comments.

Ihtesham Ali

31,074 Aufrufe • vor 5 Monaten

"Compoung engineering is how you make Claude Code smarter every time you use it." Here's my new episode with Kieran Klaassen where he demos his 4-step system to make Claude Code improve with every session: ✅ Plan. Sub-agents research your codebase and best practices before any code is written. ✅ Work. Claude asks clarifying questions, then builds the feature and writes tests. ✅ Assess. Review agents check security, architecture, and code quality. ✅ Compound. Learnings are captured so Claude never repeats mistakes. Kieran is my favorite Claude Code power user and I promise you'll learn alot too. 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:

"Compoung engineering is how you make Claude Code smarter every time you use it." Here's my new episode with Kieran Klaassen where he demos his 4-step system to make Claude Code improve with every session: ✅ Plan. Sub-agents research your codebase and best practices before any code is written. ✅ Work. Claude asks clarifying questions, then builds the feature and writes tests. ✅ Assess. Review agents check security, architecture, and code quality. ✅ Compound. Learnings are captured so Claude never repeats mistakes. Kieran is my favorite Claude Code power user and I promise you'll learn alot too. 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:

Peter Yang

85,263 Aufrufe • vor 6 Monaten

What they don't tell you about vibe coding: • Moltbook exposed 1.5M auth tokens. The owner hadn't written a single line of code. • Tea App leaked 72,000 government IDs. The database was just open, no sophisticated hack needed. • A researcher took control of a journalist's computer through her own vibe-coded game, without a single click. The code ran fine in all three cases, tests passed, reviews looked clean, and nothing raised a flag. That's the problem nobody is talking about. Teams are shipping faster than ever. AI writes the code. CI catches build failures. Tests catch regressions. Observability catches outages. But nobody is asking the one question that actually matters: What can an attacker do with this, right now? Because the bottleneck is no longer writing code. It's understanding what that code actually exposes once it's live. PR reviews miss auth edge cases. Unit tests don't probe broken access control. Staging environments don't simulate adversarial behavior. And business logic flaws look completely fine until someone decides to break them on purpose. Strix is an open-source tool that fills this gap. It reviews your running app the way an attacker would: - Crawls the app and maps every exposed route and flow - Probes abuse paths dynamically, not just at build time - Returns findings with proof-of-concepts and suggested fixes Strix was benchmarked against 200 real companies and open-source repos, where it found 600+ verified vulnerabilities including assigned CVEs. It's designed to fit into how modern teams already work. Run it before a release, after major changes, or continuously as the app evolves. If your team is shipping AI-generated code and you don't currently have a way to answer "what does this actually expose", it's worth looking at. GitHub link in the next tweet.

What they don't tell you about vibe coding: • Moltbook exposed 1.5M auth tokens. The owner hadn't written a single line of code. • Tea App leaked 72,000 government IDs. The database was just open, no sophisticated hack needed. • A researcher took control of a journalist's computer through her own vibe-coded game, without a single click. The code ran fine in all three cases, tests passed, reviews looked clean, and nothing raised a flag. That's the problem nobody is talking about. Teams are shipping faster than ever. AI writes the code. CI catches build failures. Tests catch regressions. Observability catches outages. But nobody is asking the one question that actually matters: What can an attacker do with this, right now? Because the bottleneck is no longer writing code. It's understanding what that code actually exposes once it's live. PR reviews miss auth edge cases. Unit tests don't probe broken access control. Staging environments don't simulate adversarial behavior. And business logic flaws look completely fine until someone decides to break them on purpose. Strix is an open-source tool that fills this gap. It reviews your running app the way an attacker would: - Crawls the app and maps every exposed route and flow - Probes abuse paths dynamically, not just at build time - Returns findings with proof-of-concepts and suggested fixes Strix was benchmarked against 200 real companies and open-source repos, where it found 600+ verified vulnerabilities including assigned CVEs. It's designed to fit into how modern teams already work. Run it before a release, after major changes, or continuously as the app evolves. If your team is shipping AI-generated code and you don't currently have a way to answer "what does this actually expose", it's worth looking at. GitHub link in the next tweet.

Akshay 🚀

52,399 Aufrufe • vor 5 Monaten

AI didn't make code cheap. it made bad code lethal. Matt Pocock: "Software fundamentals matter more than ever" AI in a good codebase ships gold. AI in a bad codebase ships garbage. framework mastery doesn't compound. fundamentals do. if you're starting with AI agents, build these 5 patterns before anything else: > Tool Use Design Pattern. tool calling is the core of every useful agent. > Agentic RAG. grounded answers over hallucination. maps to real products. > Planning Design Pattern. agents that break a goal into steps before acting. > Multi-Agent Design Pattern. orchestrator-subagent is the only shape that ships in production. > Building Trustworthy AI Agents. reliability, safety, knowing when not to use one. this article covers what to learn, build, and skip in AI agents in 2026. bookmark and read this today. repo with 500 more in comments

AI didn't make code cheap. it made bad code lethal. Matt Pocock: "Software fundamentals matter more than ever" AI in a good codebase ships gold. AI in a bad codebase ships garbage. framework mastery doesn't compound. fundamentals do. if you're starting with AI agents, build these 5 patterns before anything else: > Tool Use Design Pattern. tool calling is the core of every useful agent. > Agentic RAG. grounded answers over hallucination. maps to real products. > Planning Design Pattern. agents that break a goal into steps before acting. > Multi-Agent Design Pattern. orchestrator-subagent is the only shape that ships in production. > Building Trustworthy AI Agents. reliability, safety, knowing when not to use one. this article covers what to learn, build, and skip in AI agents in 2026. bookmark and read this today. repo with 500 more in comments

Rohit

28,332 Aufrufe • vor 3 Monaten

67 real production bugs. 10 different AI tools, same PRs, same standard. Entelligence benchmarked every major AI code reviewer on bugs that already shipped and broke things. They put 10 tools through race conditions, security vulnerabilities, breaking API changes, and logic errors across 5 real open-source repos (Cal[.]com, Sentry, Discourse, Keycloak, Grafana). The gap between top and bottom is not small. What separated them was not raw model power. It was whether the tool understood code relationships. How a function signature change ripples through a codebase, not just what's on the line being reviewed. Entelligence caught things every other tool missed. A breaking API change in Cal[.]com that every other tool flagged as clean. An interface change in Grafana that would have broken compilation across all existing Logger implementations. A cache race condition in Keycloak that allowed concurrent threads to corrupt a bidirectional mapping. They also published the full methodology and didn't hide where they underperformed. Ruby codebases, race conditions, CSS regressions. It's all in there. 1/2

67 real production bugs. 10 different AI tools, same PRs, same standard. Entelligence benchmarked every major AI code reviewer on bugs that already shipped and broke things. They put 10 tools through race conditions, security vulnerabilities, breaking API changes, and logic errors across 5 real open-source repos (Cal[.]com, Sentry, Discourse, Keycloak, Grafana). The gap between top and bottom is not small. What separated them was not raw model power. It was whether the tool understood code relationships. How a function signature change ripples through a codebase, not just what's on the line being reviewed. Entelligence caught things every other tool missed. A breaking API change in Cal[.]com that every other tool flagged as clean. An interface change in Grafana that would have broken compilation across all existing Logger implementations. A cache race condition in Keycloak that allowed concurrent threads to corrupt a bidirectional mapping. They also published the full methodology and didn't hide where they underperformed. Ruby codebases, race conditions, CSS regressions. It's all in there. 1/2

AshutoshShrivastava

10,362 Aufrufe • vor 6 Monaten

Someone just open sourced a tool that honestly feels unfair for developers. you join a new company. 200,000+ lines of code. zero docs. zero context. normally you’d spend weeks just figuring out “what the hell is going on here”. now? you run ONE command. and the entire codebase just… lights up. → every file, function, class, dependency automatically mapped → full system-level understanding in minutes → interactive graph instead of boring static docs → ask “where is auth handled?” and it traces the entire flow end-to-end → shows ripple effects before you even make a commit → auto-builds architecture layers: API / Service / Data / UI → works with Claude Code, Codex, Copilot, Gemini CLI, everything → fully open source and free this is not “better documentation”. this is your codebase getting a brain. onboarding isn’t slow anymore. it’s instant.

Someone just open sourced a tool that honestly feels unfair for developers. you join a new company. 200,000+ lines of code. zero docs. zero context. normally you’d spend weeks just figuring out “what the hell is going on here”. now? you run ONE command. and the entire codebase just… lights up. → every file, function, class, dependency automatically mapped → full system-level understanding in minutes → interactive graph instead of boring static docs → ask “where is auth handled?” and it traces the entire flow end-to-end → shows ripple effects before you even make a commit → auto-builds architecture layers: API / Service / Data / UI → works with Claude Code, Codex, Copilot, Gemini CLI, everything → fully open source and free this is not “better documentation”. this is your codebase getting a brain. onboarding isn’t slow anymore. it’s instant.

divyansh tiwari

39,476 Aufrufe • vor 3 Monaten

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

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

Akshay 🚀

30,859 Aufrufe • vor 1 Jahr

Whoa: WhatsApp grew to 450M monthly users with no code reviews in place. Jean Lee, engineer #19 at the company: "WhatsApp was the ultimate lean company. By the time we were acquired by Meta, we only had fewer than 30 engineers serving 450 million monthly active users. We didn't have code reviews. The only time I got my code reviewed was the first time I made a commit. Brian asked to take a look at it before I committed it, and he asked me a bunch of questions, which I had to think through a lot, but that was it. After this first time, we didn't really have a formal code review. Everyone was trusted. All engineers just pushed their code to production without a review. It was trusted that they would ask if they were unsure."

Whoa: WhatsApp grew to 450M monthly users with no code reviews in place. Jean Lee, engineer #19 at the company: "WhatsApp was the ultimate lean company. By the time we were acquired by Meta, we only had fewer than 30 engineers serving 450 million monthly active users. We didn't have code reviews. The only time I got my code reviewed was the first time I made a commit. Brian asked to take a look at it before I committed it, and he asked me a bunch of questions, which I had to think through a lot, but that was it. After this first time, we didn't really have a formal code review. Everyone was trusted. All engineers just pushed their code to production without a review. It was trusted that they would ask if they were unsure."

The Pragmatic Engineer

45,175 Aufrufe • vor 5 Monaten

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

Kaitee

64,294 Aufrufe • vor 1 Monat