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.show more

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:

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

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.

@sdrzn Santiago found /explain-changes lfg

time to install cline...

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.

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

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

Let another AI check it. Problem solved

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

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.

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

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

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

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.

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

wait! cline or anything ? i’m confused.

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.

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.

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

That's not a bottleneck, it's a flufferbot. Focus on the real problem and resolve it. It won't be about people. Trust me

Code review taking 70% of the time? Ouch! 😅 Sounds like my last sprint... Cline looks promising. Anyone else tried it?

I feel like this is a new career in the upcoming phases of spare engineering! Soon there will be openings for code debuggers on AI written code!

I'm successfully vibe coding using the free version of chatgpt, literally nothing else is needed, just a good coder to begin with and the correct prompts.

For me it works fine, to let AI create a lot of mermaidjs chart (text2charts).. People (specially all the non coders involved in DEV workflows) could much faster understand and compare different solutions/changes

Also, the AI code generation is slow. I have to spend a lot of time waiting after prompting. If the generation was almost instant, reviewing would not be much of a problem for me.

What?? Review?? Just vibe push it, no? 😅

It's not because code is complex, it is because ai generated code is out of project context and low quality

lol sounds annoying... there's better ways to dev with AI.

This video alone does more explaining than most landing pages. Inline reasoning per line is exactly what AI code review needed.

git reset --hard The most important git command when working with AI coding agents 🤣.

It doesn't always work right.

So we automated the easy part and made the hard part 3x bigger. Classic engineering move. Now we need AI to review AI code, and then AI to review that review...

This could completely change how we onboard onto unfamiliar codebases. Context + explanation in one view is huge