| ▲ | hnlmorg 2 hours ago | |||||||||||||
Whilst I agree with your point, I think what sometimes gets lost in these conversations is that reviewing code thoroughly is harder than writing code. Personally, and I’m not trying to speak for everyone here, I found it took me just as long to review AI output as it would have taken to write that code myself. There have been some exceptions to that rule. But those exceptions have generally been in domains I’m unfamiliar with. So we are back to trusting AI as a research assistant, if not a “vibe coding” assistant. | ||||||||||||||
| ▲ | tjwebbnorfolk 2 hours ago | parent | next [-] | |||||||||||||
I think the point is in a banking context, every line of code gets reviewed thoroughly anyway. | ||||||||||||||
| ||||||||||||||
| ▲ | egorfine an hour ago | parent | prev [-] | |||||||||||||
> as long to review AI output as it would have taken to write that code myself That is often the case. What immensely helps though is that AI gets me past writer's block. Then I have to rewrite all the slop, but hey, it's rewrite and that's much easier to get in that zone and streamline the work. Sometimes I produce more code per day rewriting AI slop than writing it from scratch myself. | ||||||||||||||