alt Hacker News'Cause I don't have any quality user-facing documentation yet; that README is for bots. None of the interfaces have had a chance to settle, so any time spent accurately and humanely documenting what the project is capable of right now is an investment I cannot afford. I figured most people would just give it over to their favorite LLM with whatever instructions they prefer for translation because that's what I would've done...
Replies
What does "that README is for bots" mean? Are you implying it is some kind of special language written by and correctly understood by bots/LLMs, but otherwise semantically coherent?
Wait so someone asked for something you made with AI that wasn't slop, and then you linked to something you knew was slop, and you said "I think this counts as something that isn't mere slop" and then when called out on it you admit you knew it was slop the whole time?
This is a frequent pattern among AI users. What causes it?
I don’t mean to pick on you in particular here, but this approach has been bothering me a lot lately, and it seems like it’s super common.
I get that it’s an early prototype and not all the design choices are made yet, but I struggle with “I can’t afford human-readable documentation yet”. Isn’t human readable documentation important for efficiently planning and deciding what you want to build? I feel like I can’t afford not to have human readable docs and plans while the project is taking shape
Related, if a user can prompt an agent to translate to a human-readable summary, wouldn’t it be better to just do this in place? Sure, models can deal with noisy LLM outputs but shouldn’t a document that’s easier for humans also be easier for bots?