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
341 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
I believe for simple, common tasks and small projects, it's at least manageable. Even good, if you are not forced to use AI and can simply choose to what extent you use the tools and its results.
But with enterprise-level coding agents that are supposed to handle issues in long-term projects, the work is shifted to every other phase really, before and after the coding. Initially I thought that proper documentation at least benefits everybody, but prompts and instructions optimized for AI are not necessarily good documentation for humans to read.