March 17, 2026
Cash beats tokens, fight me
Give Django your time and money, not your tokens
Stop hiding behind AI: donate cash and show your work — Django draws a line
TLDR: A Django maintainer says stop outsourcing contributions to AI and instead donate money and contribute with real understanding, not a chatbot’s facade. Commenters split: some back cash and transparency, others say contributing is already too hard, while critics slam AI giants and one challenger dares “LLM-only Django” to prove itself.
Drama alert: a Django contributor just told folks to stop paying chatbots to write pull requests and instead give real money (and real effort) to the Django Software Foundation. The core message: LLMs (AI text tools) are fine for learning, but don’t fake understanding. Reviewers say it’s demoralizing to debate with a “facade of a human.”
The comments turned into a town hall. Supporters like kanzure cheered the “cash, not tokens” push and called for clear disclosure when AI helps draft code, pointing to other projects doing exactly that (link). Veterans like yuppiepuppie added real talk: even for longtime users, contributing is hard—finding tickets and navigating the code feels like a maze. Translation: don’t blame people for leaning on AI; fix the on-ramp.
Then came the spicy takes. piker blasted the AI hype machine, saying big companies are “selling out your peers” to juice profits. jihadjihad widened the scope: this isn’t just Django—any serious project with human reviews needs contributors who truly understand their changes. And positive-spite threw down the gauntlet: if AI is so great, go build Django with it and prove it’s not sloppier.
Cue the memes: “LLM vs Human: Cage Match,” “bring your own brain,” and talk of AI-use badges. Open-source soap opera? Absolutely.
Key Points
- •The article advises donating money to the Django Software Foundation rather than using LLM tokens to generate contributions for Django.
- •Django is portrayed as having high quality standards, slow evolution, and long-term maintenance expectations, requiring deep contributor understanding.
- •Using LLMs to generate code, PR descriptions, and handle review feedback can mask contributor comprehension and harm the project.
- •LLMs should be used to aid comprehension and refine communication, with transparent disclosure of their use.
- •There is no shortcut to understanding; contributors should invest time learning, and the personal growth from genuine contributions is more valuable than recognition.