News for hackers. Stuff that matters.
Re:Why most of us won't be inventing little languages by tonnydourado on Monday April 17, 2023 @08:07AM (#35599539)
> It's that other people won't understand you.

I think the idea is the other way around. It's not about inventing a new language, it's about taking a jargon that already exists, is used and understood by domain experts, and make it executable. Less regex/XML, more nouns and verbs from a very specific business context.

Granted, even with that perspective, it's still a stretch to say little languages are the future, but both the article linked here and the one it's replying to are from 2004, so, there's that.

Re:Why most of us won't be inventing little languages by MrBuddyCasino on Monday April 17, 2023 @08:15AM (#35599617)
I have yet to see a cucumber test that was actually touched by a non-technical domain expert. It is a fantasy and only introduces inscrutable abstraction layers that don’t add value.
Re:Why most of us won't be inventing little languages by robertlagrant on Monday April 17, 2023 @08:35AM (#35599773)
It's not a fantasy. They may not write them (though some less technical manual QA people will add to scenarios with a data table), but deciding on them and reading them, and spitting their results out into documentation are all useful in their own rights.
Re:Why most of us won't be inventing little languages by randomdata on Wednesday April 19, 2023 @07:00PM (#35634388)
I have, and that is how they wanted to communicate the needs of the application to the development team.

It was horrid. Getting non sequitur snippets of requirements without the big picture, in this weird almost English, but not, language that looked like it was desperately trying to copy the structure of test code, but without anything executable, losing the entire reason you might choose to accept the tradeoffs of documenting your requirements in code as promoted by actual BDD.

Not only did it not add value, it took away value.