Ways to contribute: Peer review, human code review, money for tokens for code and code review, configure SAST and DAST tools to make it DevSecOps instead of DevOpsSec, configure AGENTS.md and an /upgrade-dependencies-and-run-tests skill,
Compare "It's inadequate because it's AI" with "it looks like this generation of agents doesn't yet handle this quality aspect with or without explicit prompts" with "you could improve quality by writing tests, docs, and before that refactor for maintainability and subjective elegance" (if you're trying develop a hit open source project)
> impossible to know whether misconceptions or gaps are because the author doesn’t understand the material
Shouldn't a researcher consider the argument - it's premises and form - instead of tangential ad hominem about the author?
Pushing for well-formed arguments is older than AI
“The author doesn’t understand the material” isn’t an ad hominem — most of my work involves working with other people, usually less experienced, to help them deliver reasonably complex econometric or ML models. Sometimes I’m hands on, usually not. Knowing if it’s “the author not understanding the material” is important because my job is to help them understand it so that they can deliver something that 1) works and 2) does what it’s supposed to. AI written docs are at best a mixed blessing.
Or maybe it’s me not understanding! Either way, if something looks wrong, I want to discuss it with people who know the subject matter and can talk me through the parts that look off so that I can learn from it.
No, that's not an ai written comment either.