Reviewing AI-generated code is the new bottleneck.
@svpino457K followers
64,477 views
34 Comments
Comments from the original post on X (Twitter)

@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_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

@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

@nickbaumann_
@sdrzn Santiago found /explain-changes lfg
4 likes

@vayospot
time to install cline...
3 likes

@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

@NikosKatsikanis
if you can't review the code, then plumbing is a better move
3 likes

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

@finleysson
Let another AI check it. Problem solved
2 likes

@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

@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

@ehsanianno
Nice, now instead of reading 100 lines of code, devs have to read 100 lines of text
1 like

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

@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

@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

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

@brentbrookler
wait! cline or anything ? i’m confused.
1 like

@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

@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

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












