3 ms·
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.
by doug_durham 5mo 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.
- 1attice 5mo agoThat's just agreeing with extra steps.
- vor_ 5mo agoIn 7 days?
- b40d-48b2-979e 5mo agoThose SWE practices were so solid that the rewrite was already rolled back!
- cheesefck 5mo agothe 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.
- oytis 5mo agoHow can you claim following SWE best practices if couldn't realistically even have read the code?
- shimman 5mo ago"Please follow best practices." You're telling me that isn't good enough? You might need to head off to the VC reeducation camps.
- doug_durham 5mo agoSo transcoding doesn't work unless every line of code is read? That's not how transcoding is done in practice.
- bhaak 5mo agoBut 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.
- egorfine 5mo agoIt was not ported by an engineer. It was transpiled by an LLM and no engineer has ever seen those 1mloc.
- 12345hn6789 5mo ago1 million lines of code written and approved, in 9 days proves without reasonable doubt it was vibe coded.
- john_strinlai 5mo ago1 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".