Comment by john_strinlai
5 hours ago
i find something a bit funny in an ai project, written by ai, requiring human-written text with specific guidance to not use ai.
"Given that coding agents write most underlying code now, we'd prefer PRs in the form of human-written text. [...] Please do not have AI artificially expand what you'd like to do into a formal proposal."
XY problem, don't expand the design doc before you have the idea for the design. Don't compile down into lower abstraction levels until necessary
i think it makes perfect sense and I'll probably adopt the same posture for my open source project.
The idea is that the core dev team is the one with the AI harness. If someone contributes an idea they can just feed it to their AI to implement it and it probably costs 10 minutes of human time, because they trust that their harness will be able to implement the feature competently.
So, because the implementation effort is so low, the only aspect that matters if the quality of the idea. It's way easier to screen human written text than a bunch of code in a PR. If you just give them code, they would not know if you made it with a competent harness. If you gave them a AI written design they would have a lot more to read through to decide whether it's slop. If you just give them an idea it's a lot easier to determine whether it's high quality.
Coding agents are extremely useful but often extremely dumb with design. If you do not design the software yourself, you will probably get slop. This was always the core issue with vibe coding.
AI Averages, and is inclined to do average designs and implementations, which in some cases might be an improvement, but long term it creates more to deal with.
Hm. If "AI averages," then why doesn't it create an average amount to deal with, instead of more?
2 replies →
They specifically ask not to create/submit a formal proposal. I do not see any restriction on the use of AI otherwise.
i read the emphasized "human-written" part, in combination with that last line, as a blanket restriction (for contributing). but perhaps i read it wrong.
The point is that they just want your prompts, not your code.
3 replies →
List of commits already include at least two contributors who are openly working with Claude on their code: https://github.com/yc-software/qm/commits/main/
Yet the README is generated ("Two skills maintain the boundary in both directions.") and the demo is .. a Mobius strip?
I'd prefer if you explain what it is you are building in the form of human-written text.
Well, if they're consistent, the ADR directory contains only human written text that drives the underlying development... Aaand it's empty. Well.
I personally would probably have the readme generated based on that directory as the primary document, probably with another `readme_generation_rules.md` in the ADRs directory, and I would be pretty ruthless about disallowing all the slop-adjacent wording.
> I would be pretty ruthless about disallowing all the slop-adjacent wording.
I’d think that trying to play whack-a-mole with slop like that would result in a lengthy prompt, as well as being brittle to future changes.
If you want the prompt to be the source of truth, you’re probably going to have to accept prose that feels like AI, at least until you can regenerate with some future smarter model.
That's not surprising. I have much the same thing in my latest open-source work[0]. I have a workflow that's working nicely with agents, it's more of a pain to review someone else's code than it is to get a well-written description of their problem.
0: https://github.com/pjlsergeant/byre?tab=contributing-ov-file