Sometimes it notices something I would have missed (like missing an 'order_by' or off by one errors, because the underlying lib wasn't coded like the original AI pretended it was)
orwin on Hacker News
In the thread “AI Can Make You Suck Faster Too”
Helped: Flagging uncertain lines and asking for detailed explanation and library search.
Got in the way: Initial attempts were poor; juniors still lack domain knowledge.
… It started poorly, but now I have my method: I first read the code and flag the lines I'm not sure about, then ask any frontier model (I like Claude here for analysis, even if I don't use it for the rest) to explain the PR and to put effort on the parts I flagged (basically explain in detail the code, not only the PR), and to search through the libraries. Sometimes it notices something I would have missed (like missing an 'order_by' or off by one errors, because the underlying lib wasn't coded like the original AI pretended it was). I also changed the way I do review because it has been more than a year and the juniors/new hire are still lost, wether on domain knowledge for the older new hire, or just capabilities for the juniors, and discussing with other departments, it's the same for like 95% of them. …