Hacker News new | ask | show | jobs
by mixologic 86 days ago
Worth noting that mcollina is a member of the Node.js Technical Steering Committee
2 comments

yes this.

if there's anyone i would trust in exploring these avenues, it's him and the maintainers doing god's work in the nodejs repo in these past few years.

We call it a slip slop at work, it's ok to slip some slop if it's "our" slop :-)
> I pointed the AI at the tedious parts, the stuff that makes a 14k-line PR possible but no human wants to hand-write: implementing every fs method variant (sync, callback, promises), wiring up test coverage, and generating docs.

Is it slop if it is carefully calculated? I tire of hearing people use slop to mean anything AI, even when it is carefully reviewed.

Was 14k lines carefully reviewed? Seems unlikely.
Considering the many hundreds of technical comments over at the PR (https://github.com/nodejs/node/pull/61478), the 8 reviewers thanked by name in the article, and the stellar reputations of those involved, seems likely.
My mistake 19k lines. At 2 mins per line that’s (19000*2)/60/7=90 7-hour days to review it all, are you sure it was all read? I mean they couldn’t be bothered to write it, so what are the chances they read it all?

For someone’s website or one business maybe the risk is worth it, for a widely used software project that many others build on it is horrifying to see that much plausible code generated by an LLM.

When you review code, do you spend 2 minutes per line? That seems like a huge exaggeration of effort required
> I mean they couldn’t be bothered to write it, so what are the chances they read it all?

What kind of logic is this?

The PR has been open for 3 months, and all the reviewers involved have actually read the whole code and are experts on the matter.
I carefully review far more than 14k LoC a week… I’m sure many here do. Certainly the language you write in will greatly bloat those numbers though, and Node in particular can be fairly boilerplate heavy.