[flagged]
> scale, security, whatever Yea, who needs performance or security in a web framework!?
Did you deliberately miss my point?
Heck the longer I live, the more I realize AI is catching my mistakes.
Give Django your time and money, not your tokens
51–60 of 184 posts
Re: Give Django your time and money, not your tokens
#52s/Django/the codebase/g , and the point stands against any repo for which there is code review by humans: > If you do not understand the ticket, if you do not understand the solution, or if you do not understand the feedback on your PR, then your use of LLM is hurting Django as a whole. > Django contributors want to help others, they want to cultivate community, and they want to help you become a regular contributor.…
> I am going to try to make these points to my team, because I am seeing a huge influx of AI-generated PRs where the submitter interacts with CodeRabbit etc. by having Claude/Codex respond to feedback on their behalf.
Are people generally unhappy with the outcomes of this? As anecdotally, it does seem to pass review later on. Code is getting through this way.
Re: Give Django your time and money, not your tokens
#53Earlier quoted context omitted.
Isn't the meaning of milquetoast opposite to what you are probably trying to convey?
I think they don't understand what milquetoast actually means, as the post defintiely isn't - django quite clearly asserted themselves and their rules. What the parent comment was probably trying to say was something like "a completely reasonable, uncontroversial post that I'm glad to see them make", but chose milquetoast (a word that no normal human ever uses - and certainly not in casual conversation) due to an aff…
On the contrary, they could have stated their points much more bluntly and strongly than they did in the post. I had the same impression upon reading it.
Milquetoast perfectly describes it, I am happy to see less common words used around here (specially when the convey the intended meaning this precisely), and I find claiming "affectation" of the person who used it unnecessarily rude.
Re: Give Django your time and money, not your tokens
#54Perhaps we should start making LLM- open source projects (clearly marked as such). Created by LLMs, open for LLM contributions, with some clearly defined protocols I'd be interesting where it would go. I imagine it could start as a project with a simple instruction file to include in your project to try to find abstractions which can be useful to others as a library and look for specific kind of libraries. Some peopl…
OpenClaw https://github.com/openclaw/openclaw is effectively that - 1,237 contributors, 19,999 commits and the first commit was only back in November.
Re: Give Django your time and money, not your tokens
#55Great message but I wonder if the people who do everything via LLM would even care to read such a message. And at what point is it hard/impossible to judge whether something is entirely LLM or not? I sometimes struggle a lot with this being OSS maintainer myself
"the people who do everything via LLM". That's a bit of a straw man characterization. I don't believe that there are many professional developers "do everything with an LLM'. I don't even know what that statement means.
[dead]
Re: Give Django your time and money, not your tokens
#56Perhaps we should start making LLM- open source projects (clearly marked as such). Created by LLMs, open for LLM contributions, with some clearly defined protocols I'd be interesting where it would go. I imagine it could start as a project with a simple instruction file to include in your project to try to find abstractions which can be useful to others as a library and look for specific kind of libraries. Some peopl…
OpenClaw https://github.com/openclaw/openclaw is effectively that - 1,237 contributors, 19,999 commits and the first commit was only back in November.
Simon, as co-creator of Django, what's your take on this story?
Re: Give Django your time and money, not your tokens
#57I feel like open source is taking the wrong stance here. There’s a lot of gatekeeping, first. And second, this approach is like trying to stop a tsunami with an umbrella. AI is here to stay. We can’t stop it, for much we try. I feel the successful OS projects will be the ones embracing the change, not stopping it. For example, automating code reviews with AI.
OSS projects usually has culture which adopting quality aimed development practices much faster that commercial projects (because of cost of adoption) so it looks like same concerns eventually will hit other kind of projects.
Re: Give Django your time and money, not your tokens
#58[flagged]
Re: Give Django your time and money, not your tokens
#59I feel like open source is taking the wrong stance here. There’s a lot of gatekeeping, first. And second, this approach is like trying to stop a tsunami with an umbrella. AI is here to stay. We can’t stop it, for much we try. I feel the successful OS projects will be the ones embracing the change, not stopping it. For example, automating code reviews with AI.
When you waste time trying to deal with "AI" generated pull-requests, in your free time, you might change your mind.
I share code because I think it might be useful to others. Until very recently I welcomed contributions, but my time is limited and my patience has become exhausted.
I'm sorry I no longer accept PRs, but at the same time I continue to make my code available - if minor tweaks can be made to make that more useful for specific people they still have the ability to do that, I've not hidden my code and it is still available for people to modify/change as they see fit.
Re: Give Django your time and money, not your tokens
#60Earlier quoted context omitted.
OpenClaw https://github.com/openclaw/openclaw is effectively that - 1,237 contributors, 19,999 commits and the first commit was only back in November.
Simon, as co-creator of Django, what's your take on this story?
I think this line says everything:
> If you do not understand the ticket, if you do not understand the solution, or if you do not understand the feedback on your PR, then your use of LLM is hurting Django as a whole.