upvote
I don't know about you, but I force myself to read the whole spaghetti thought process of any AI that's actually working on code, and make sure I understand what the hell it just said before I ask questions or give it a green light. Even or especially when whatever it said is full of fluffy stuff about having understood the problem space. That's usually where a well-placed question can bring the entire structure crashing down.

"You're right to push back" has become the gold standard phrase I'm looking for from these things to assure myself that I'm covering all the bases and understanding what it's building (not that that's enough, and not that it isn't still going to build some ungodly blob anyway).

I kinda like using voice to jot down my next questions or iterate on things, but there's a clear danger to it, which is that you may inadvertently be signing off on stuff you haven't thoroughly read. If there's one thing about LLM-written code, it's that the devil is in the details.

reply
[flagged]
reply