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.
But how do we define what orbits what? On the scale from the Sun to Earth, the Moon orbits the Sun, just a litle more wobbly than the Earth’s path, by litle I mean well below the error when we imagine the Erath’s path as an elipse.
We can try to define if something goes around as orbiting, but If I pick two planet from our solar system one will goes around of the other, thechnically orbiting it? We can try to restricting the distance… but that is a problem as well, even worst idea that “nothing” comes in between: multiple moons? What about the moons’ moons?
Ahhh, humans and their need to neatly categorize things…