HN Explorer

Ask HN: In the new AI world, what's the best way to review code?

1 points by iwebdevfromhome ↗ HN
Just as title says, in the world of ai accelerated code production, when you're in charge of a repo or project, how do you usually look at code from proposed changes ?

I'm interested to find what your workflows look like these days.

4 comments

[ 0.28 ms ] story [ 7.3 ms ] thread
kay_o
Not supposed to edit or touch any code, or review. Other agent reviews and approves. You only write prompt.
dabinat
But if you never review it, how do you know it’s correct, secure, maintainable, performant, etc? You just trust it’s correct because you told the agent to make it correct?
battery_staple_
My hobby project gets much less of my time than I would prefer. I've got the strongest model I have access to, on a cheap subscription, running --yolo in a VM with a fairly locked down firewall. I found that a tree (i.e. the filesystem) isn't really enough, for representing my thoughts, so I've built a graph datastore of sorts with a query layer that basically consists of a view (fitting the graph onto a tree) and a filter (for the root of that tree). Technically I've got a review process for the graph, but in practice I just approve it. I'm planning to build out an automated review process, kinda like unit tests, where I give a given prompt ownership over a specific cluster of nodes (and the code paths owned by them), and that prompt has to approve changes before I see them, but I haven't done that yet.

To answer your question, the actual review I do, is when the agent asks me questions. I tell it to resume a task, it asks questions, I answer them. If those questions are off-the-rails, I stop, pop the conceptual stack, and come at the whole thing from a different angle.

I'm basically trusting the model to do a good job, and fixing forward, always annealing the project toward what I want. And the rejection criteria is when the questions that it's asking are _questions I don't care about_.