Skip navigation
Reviewing AI-generated code is the new bottleneck.
0:00 / 3:25

Reviewing AI-generated code is the new bottleneck.

Santiago

@svpino457K followers

Visit on X
580 likesDownloadOriginal post

64,477 views

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.

34 Comments

Comments from the original post on X (Twitter)

  • Santiago's profile picture

    @svpino

    By the way, Cline was recently the fastest-growing AI project on GitHub, and it's fully open source with 50,000+ stars. Here is a link to install Cline on @code: If you want to understand the new "Explain Changes" feature, here is a link to their blog:

    31 likes

  • Kirha's profile picture

    @kirha_ai

    AI moved the bottleneck from writing code to trusting it. Tools that make verification faster are now more valuable than tools that make generation faster, because output is no longer the scarce resource, developer attention is Anything that compresses the “review + understand” loop is going to be essential in modern workflows

    9 likes

  • Bill's profile picture

    @billassault

    This isn't about saving time. It's because people generating all this code don't understand it, so they can't possibly review it. And somehow they think reviewing it in English is good enough.

    8 likes

  • Nick's profile picture

    @nickbaumann_

    @sdrzn Santiago found /explain-changes lfg

    4 likes

  • Vayo's profile picture

    @vayospot

    time to install cline...

    3 likes

  • Ajit Gupta's profile picture

    @unfiltered_ajit

    New job in upcoming years Software developer ❌️ Software reviewer ✅️ Code is there, but we need to review it. So, you still need to know how to write code before reviewing AI's code.

    3 likes

  • Nikos Katsikanis's profile picture

    @NikosKatsikanis

    if you can't review the code, then plumbing is a better move

    3 likes

  • juanmacias 🏳️‍🌈's profile picture

    @juanmacias

    You can put the AI to review the code, is what I’m doing…

    3 likes

  • Finleysson's profile picture

    @finleysson

    Let another AI check it. Problem solved

    2 likes

  • andy's profile picture

    @apricitycodes

    we just externalized the 'typing fast' part and internalized the 'thinking hard' part. sounds like the bottleneck just upgraded its address, not disappeared.

    2 likes

  • Dan Wells's profile picture

    @DanWells1139026

    Why bother? Why not just let it turn out crappy products & tell us we have to buy them & like them or else? That’s been the MO of tech for a while.

    2 likes

  • Ehsan 🇮🇷's profile picture

    @ehsanianno

    Nice, now instead of reading 100 lines of code, devs have to read 100 lines of text

    1 like

  • Anirudh Sharma's profile picture

    @anirudhology

    What are your thoughts on Claude Code's "review" and "security-review" modes?

    1 like

  • Milla Millennial's profile picture

    @MillennialMilla

    Unpopular opinion. If a reviewer needs an AI to explain the code they're supposed to review, then maybe they're not qualified enough.

    1 like

  • Zaf____'s profile picture

    @Zaf98140883

    Have tried multiple prompts like this. The best way to review is not to look at the lines but to look at the impact. Tell the LLM to find the flows affected by this change and then show the before/after of the flow in Psuedo code. That's all.

    1 like

  • Daniel King's profile picture

    @KingDDev

    Part of the reason why I built KarpeSlop, detecting AI slop was taking too much time

    1 like

  • Brent Brookler's profile picture

    @brentbrookler

    wait! cline or anything ? i’m confused.

    1 like

  • John Au-Yeung's profile picture

    @AuMayeung

    This is such a smart approach. Code generation is fast, but understanding it safely is the real limiter. Pairing every line with an explanation is like adding automated pair programming. Even a mini-guide: review diffs in chunks with context notes to halve the mental load.

    1 like

  • Prometheus Protocol's profile picture

    @Prometheus9486

    This is exactly the right observation. The bottleneck has shifted from creation to verification. It's the human-level version of the exact problem AI agents face at a protocol level. An agent can’t ask for a line-by-line explanation before using a tool; it needs a mathematical guarantee. That's why we built on-chain rails for a provable software supply chain, verifying every tool from git commit to on-chain deployment.

    1 like

  • Massoud's profile picture

    @massoudmaestro

    The output models need to improve. Solid code should be based on data structure objects and reliable well understood algorithms.

    1 like