Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.
If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.
Fortran. always Fortran.
because there’s always more documentation than with vibecode.
Well obviously with vibe coded stuff, you just put the code back in the AI and ask for documentation.
Problem solved. /s
Your comment felt like it made my blood pressure spike, because I have heard people saying this 100% without irony
Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.
If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.