this style of active code review removes basically all AI smells in practice
atq2119 on Hacker News
In the thread “GCC steering committee announces AI policy”, replying to this comment
Helped: Babysitting long edit-build-test loops for narrow tasks.
… while I'm in a meeting or working on something else, and then doing a thorough, thoughtful, and active local code review (meaning, having an editor and the diff open side-by-side and liberally making edits to clean up the code) before pushing anything out for others to see feels like a reasonable point in the space right now. Nothing is perfect, but this style of active code review removes basically all AI smells in practice. The edit-build-test loop is fairly long (i.e., longer than a few seconds), so having AI babysit this loop for the initial development of a task is helpful.