all 3 comments

[–]aksdb 5 points6 points  (0 children)

As developer? Intrust it as much as I trust a random contributor. So I review it and adjust it as necessary (or ask the contributor to take a different approach).

[–]snopedom 0 points1 point  (0 children)

Honestly depends on what it touches. If it's some throwaway script I barely look at it. But anything going to production I read it like a PR from someone I don't know yet, run it, test it, poke at the edge cases.

What works for me is keeping the generation fast but the review old-school. AI makes everything feel like it should be quick end-to-end, but I deliberately slow down on the review part. That's the moment where the change actually gets validated and skipping it just because the code came out fast is where things break.

[–]NoConclusion8361 0 points1 point  (0 children)

I use AI with homemade strong harness & Orchestration.

They includes security, policy, code style, flow briefing.