Vibe code was never meant to be reviewed.

These rewrites are just test-driven development taken to the absolute extreme. Created under the hope that the existing tests are exhaustive and cover every relevant use case, such that if they all pass, the rewrite must be at least as good as the original. So just go with the vibes and burn tokens until they pass, and your job is done.

In practice, this is never true for any codebase above a certain level of complexity, especially not one as mature and widely used as Postgres. But reality doesn't seem to be an obstacle for vibe coders.

▲

dirkc 2 hours ago | parent | next [-]

The challenge is that more and more people are producing project like this - 1,000s of commits and > 200k lines of code - and saying it was carefully created using agent based workflows and not vibe coded.

	▲	HPsquared an hour ago \| parent [-]
		In that case they need to document the process and workflow, and demonstrate the care that was taken.

▲

wartywhoa23 2 hours ago | parent | prev | next [-]

> reality doesn't seem to be an obstacle for vibe

Went straight into my vault of brilliant quotes!

▲

coldtea 2 hours ago | parent | prev [-]

And run them in test setups to try to find bugs.

If you find some, fix them.