Comment by doug_durham
2 days ago
There is no evidence that it was "vibe" coded. It was ported to Rust by an expert engineer using an AI tool using solid SWE practices.
2 days ago
There is no evidence that it was "vibe" coded. It was ported to Rust by an expert engineer using an AI tool using solid SWE practices.
1 million lines of code in 7 days = ~6000 lines of code to be reviewed per hour, 24 hours per day.
or... they just trust that their ai got it right, which to most people is "vibe coding".
the speed of the rewrite and various analyses of the resultant codebase provide ample evidence that it was vibe coded and solid SWE practices were ignored
nobody understands the Bun Rust codebase. I wouldn't risk my business on code understood by no person. who is responsible? who will take accountability?
nobody. into the trash with it.
How can you claim following SWE best practices if couldn't realistically even have read the code?
So transcoding doesn't work unless every line of code is read? That's not how transcoding is done in practice.
But the code that does the transcoding has been read.
Somebody needs to have read deterministic code to even have a chance of noticing something being wrong.
This has not happened here.
"Please follow best practices."
You're telling me that isn't good enough? You might need to head off to the VC reeducation camps.
That's just agreeing with extra steps.
It was not ported by an engineer. It was transpiled by an LLM and no engineer has ever seen those 1mloc.
In 7 days?
1 million lines of code written and approved, in 9 days proves without reasonable doubt it was vibe coded.
Those SWE practices were so solid that the rewrite was already rolled back!