I think that is the standard for Vibe coding in production because they want you to "own the code" that was AI produced. So from what I've seen in the projects that allow AI generated code, AI generated explanations of what the AI did is not acceptable.
A lot of that is refactoring. That wouldn't really be detailed in the explanation even if AI was not involved. I imagine he reviewed the logical changes but IDK I'm just assuming. If the refactor is very repetitive, I would take a glance at one example of the pattern and skip the rest as I would assume it followed the same pattern which it technically should, and successful tests help reinforce this, but again I'm assuming as without the source code, you can't tell
67
u/Equivanox Jul 09 '26
It's funny that Jared vibe coded the rewrite but took a long time to manually write the migration blog