Developers of open-source applications SHOULD include a PRD.md document with the source-code — in addition to README.md and HACKING.md documents.
Discussion
Loading...
@reiver interesting take. Given the spread of the coding LLMs your wish might even come true, as most of the better harnesses for those rely upon having one of those to guide 'em / derive further tasks from.
Quality of the PRD might be a different question.
But then again: When was the last time you saw a really great&done human-written PRD document and team who really knew what they really wanted from the get go and built something that actually held up against reality on the first run/iteration? #agilé and all.
@reiver not familiar with this, what is it?
PRD = product requirements document
It talks about WHAT the application is.
The vision. The purpose. The problem statement. The mission. The target audience. The functional requirements. The technical considerations. The UX. Etc.
@reiver @andypiper It's requirements documentation. You know, the documentation we should have been writing for the last 20+ years until Agile (capital A) came along and told us documentation was bad. 😋
@andypiper @reiver Sure, no worries. I couldn't help get my little dig in about documentation. I find it highly amusing that it's taken the AI hype-train to get a whole generation (or possibly multiple generations) of developers to realise that project documentation is actually a good thing. 😀