Comment by righthand
16 days ago
Sure but the specs are informal and unadaptable then. Usually a specification follows some sort of guiding format and organized thought. Usually abstracted from the whims of the author to make the spec clear. Context files are what? Dev notes and cheat sheet?
I'm hoping they'll be the docs themselves, written before the project is out.
We already have README, and API specs, and Jira, and Confluence, and RFCs are freely available.
Why do these "agents" need so much hand holding?
Because they are like very eager Junior devs.
1 reply →
It’s a great thought and this track has led me to wonder why no one is trying to build applications from BDD/gherkin statements.
It’s hard for me to believe that people are writing more technical documentation, understanding more, when they want to use the Llm to bypass that. Maybe a handful of disciplined engineers per capita but when the trend is largely the opposite, the academic approach tends to lose out.
Gherkin was always a pretty bad format that made it difficult to write terse, clear spectests. Inevitably the people who used it made horribly repetitive or horribly vague gherkin files that were equally bad for BDD and testing.
This is an artefact of the language which the creators are in total denial about.
There are better languages for writing executable user stories but none very popular.
bdd/gherkin are sometimes useful but they are not a great format to capture all the comblexity of the problem.
1 reply →