Is this really where we've landed? I refuse to believe that any of this markdown insanity will continue indefinitely.
pimlottc 12 minutes ago [-]
It's insane to me that the "fix" for AI errors is adding more "PLEASE PLEASE DO BETTER" to the prompt
nextaccountic 34 minutes ago [-]
it's looking like llms are interpreters, and markdown plus english text is the language of choice to run non deterministic programs on it
8cvor6j844qw_d6 20 minutes ago [-]
QUALITY.md feels similar to CONSTITUTION.md
Looks like unless something better comes up, we'll be stuck with it for a while.
I find markdown useful for repo-specific conventions, especially skills.
willcodeforfoo 38 minutes ago [-]
I thought the same about Yaml and Kubernetes/Helm…
cyanydeez 28 minutes ago [-]
it is until we define real consistent deterministic gates and protocols. It really is a symptom of the lack of concerted effort. Everyone has a personal preference on how to shove the context and most of them are just "here's some good text I've found to work in my context"
dofm 56 minutes ago [-]
The one thing I do not understand is that here you say:
"Ensure stakeholders are aligned on what matters most and why"
But it is instructions for LLMs, right? A way to describe something that the humans know and the LLMs don't.
LLMs literally cannot be stakeholders, by definition.
chrisweekly 44 minutes ago [-]
Not OP, but it seems to me the idea is that stakeholders can collaborate and come to consensus on the contents of QUALITY.md.
hiAndrewQuinn 6 minutes ago [-]
I'm less interested in this than in what people are willing to aggressively trade off against in order to get the stuff they truly care about.
For example, readability. Where are the developers out there saying "I am very willing to sacrifice a lot of readability to get even a small improvement on e.g. abstraction cleanliness", and sticking with it?
Or "performance can take a huge hit at the cost of being dead easy to read and reason about". Coming up with a list of abstractly good-sounding qualities is just prosocial signaling without knowing what you're willing to sacrifice. There should be a FUCKIT.md that enumerates these.
Looks like unless something better comes up, we'll be stuck with it for a while.
I find markdown useful for repo-specific conventions, especially skills.
"Ensure stakeholders are aligned on what matters most and why"
But it is instructions for LLMs, right? A way to describe something that the humans know and the LLMs don't.
LLMs literally cannot be stakeholders, by definition.
For example, readability. Where are the developers out there saying "I am very willing to sacrifice a lot of readability to get even a small improvement on e.g. abstraction cleanliness", and sticking with it?
Or "performance can take a huge hit at the cost of being dead easy to read and reason about". Coming up with a list of abstractly good-sounding qualities is just prosocial signaling without knowing what you're willing to sacrifice. There should be a FUCKIT.md that enumerates these.