56
Why AI coding tools shift the real bottleneck to review
(blog.logrocket.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Jan 2026
56 points (96.7% liked)
Programming
24699 readers
335 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Big agree.
But also: people seem to only focus on the output side of the task of writing code, and forget that the developer also receives input from the codebase in return.
Even if you end up with exactly the same code artifact after completing a work item, you’ll have a better understanding of the codebase without delegating swaths of it to AI. But bosses tend not to consider this.
Tech bros have successfully convinced people that mental states do not exist, or at least do not matter — for laborers, anyway, cuz they’ll happily claim that their superior thoughts are exactly why they deserve to be billionaires.