Live data from Hacker News

AI has a deep understanding of how this code works

github.com

121–130 of 329 posts

Re: AI has a deep understanding of how this code works

#121
When I read this discussion on GitHub, a quite different thought than what the comments here on HN discuss comes to my mind:

Why is the person who made this AI-generated pull request (joelreymont) so insistent that his PR gets merged?

If I created some pull request and this pull request got rejected for reasons that I consider to be unjust, I would say: "OK, I previously loved this project and thus did such an effort to make a great improvement PR for it. If you don't want my contribution, so be it: reject it. I won't create PRs anymore for this project, and I hope that a lot of people will see in this discussion how the maintainers unfairly rejected my efforts, and thus will follow my example and from now on won't waste their time anymore to contribute anything to this project. Goodbye."

Re: AI has a deep understanding of how this code works

#122

When I read this discussion on GitHub, a quite different thought than what the comments here on HN discuss comes to my mind: Why is the person who made this AI-generated pull request (joelreymont) so insistent that his PR gets merged? If I created some pull request and this pull request got rejected for reasons that I consider to be unjust, I would say: "OK, I previously loved this project and thus did such an effort…

Central to it being that you consider it unjust. The other option is to take into consideration the perspective of the maintainers, find their feedback to be just and then decide whether you want to contribute in the manner that they expect or you're not ready to do that kind of work.

You don't have to stop loving a project just because you're not ready to put in the work that the maintainers expect you to put in.

When I open a PR without discussing it at all beforehand with anyone, I expect the default to be that it gets rejected. It's fine by me, because it's simply easier for me to open a PR and have it be rejected than to find the people I need to talk to and then get them all onboard. I accounted for that risk when I chose the path I took.

Re: AI has a deep understanding of how this code works

#123

When I read this discussion on GitHub, a quite different thought than what the comments here on HN discuss comes to my mind: Why is the person who made this AI-generated pull request (joelreymont) so insistent that his PR gets merged? If I created some pull request and this pull request got rejected for reasons that I consider to be unjust, I would say: "OK, I previously loved this project and thus did such an effort…

Central to it being that you consider it unjust. The other option is to take into consideration the perspective of the maintainers, find their feedback to be just and then decide whether you want to contribute in the manner that they expect or you're not ready to do that kind of work. You don't have to stop loving a project just because you're not ready to put in the work that the maintainers expect you to put in. Wh…

> Central to it being that you consider it unjust.

I assume this is a correct characterization of how joelreymont feels about the fact that his PR was rejected.

Re: AI has a deep understanding of how this code works

#124

"Challenge me on this" while meaning "endure the machine, actually" I guess the proponents are right. We'll use LLMs one way or another, after all. They'll become one.

"Challenge me on this" Five seconds later when challenged on why AI did something "Beats me, AI did it and I didn't question it." Really embarrassing stuff all around. I feel bad for open source maintainers.

Even if it was in good faith the offer is “ask me a question and I’ll type it into a publicly available LLM”. Wow what a once in a lifetime opportunity!

Re: AI has a deep understanding of how this code works

#125
> P.S. Pushing my ambitions onto unsuspecting open-source communities was a mistake I won’t repeat. The best playground is always your own project.

In fairness, the author claims to have learned - quoting from his portfolio page

So... 1 down, 6.9 billion to go.

Re: AI has a deep understanding of how this code works

#127

There are LLMs with more self-awareness than this guy. Repeatedly using AI to answer questions about the legitimacy of commits from an AI, to people who are clearly skeptical is breathtakingly dense. At least they're open about it. I did love the ~"I'll help maintain this trash mountain, but I'll need paying". Classy.

I don't think he's dense, I think he's just a high level troll

Oh, you would be surprised. I don't know this particular guy but I can assure you that most people like this are not trolling.

Re: AI has a deep understanding of how this code works

#128
> You may think that the answer to that is to also automate the review process, or (more plausibly) to lower our quality standards: we can accept PRs based on simple/lightweight tests (themselves AI-generated), and if users find issues we can quickly use automated tools to fix them, basically having our users perform the testing work that is missing.

Our glorious AI-driven future in a nutshell.

Re: AI has a deep understanding of how this code works

#129
post #127

Earlier quoted context omitted.

I don't think he's dense, I think he's just a high level troll

Oh, you would be surprised. I don't know this particular guy but I can assure you that most people like this are not trolling.

I can support your assertion here with experience. This is as earnest as it gets.

Re: AI has a deep understanding of how this code works

#130

When I read this discussion on GitHub, a quite different thought than what the comments here on HN discuss comes to my mind: Why is the person who made this AI-generated pull request (joelreymont) so insistent that his PR gets merged? If I created some pull request and this pull request got rejected for reasons that I consider to be unjust, I would say: "OK, I previously loved this project and thus did such an effort…

Yeah, I learned my lesson on this...

I used to contribute to a FLOSS project years ago and decided to use Claude to do some work on their codebase recently where they basically told me to go away with these daffy robots or, at the very least, nobody will review the code. Luckily, I know better than putting too much work into something like this and only wasted enough time to demonstrate the basic functionality.

So... I have a debugged library (which is what I was trying to give to them) that I can use on another project I've been working (the robots) to the bone on and they get to remain AI free, everyone wins.

Post reply on HN