Replying to Avatar Silberengel

I wrote a design document, including PlantUML diagrams, and mockups, and hyperlinks to designs I liked and specs I wanted to cover and architectural/quality concepts I wanted to include, and coding guideline stuff from our PO. It was like 5 pages long.

And then I had it generate the .feature files, and went through multiple iterations on each file, editing and then having it review-and-suggest-more, and basta. The team has been feeding me their wishes, on the side, in Gherkin, and I just say "Please incorporate this into the .feature files and then implement." and ta-da!
Avatar
Silberengel 6mo ago

What you get out is not a product, but it's a highly-functionality prototype. You can then hone it and refine it. Once it gets relatively good and everything basically works, you can hand it off to your architect (or architect it, yourself) and he can rewrite the code.

He can even open a new repo, copy-paste in the .feature files, and then build a completely new, clean software program that passes the same tests.

Reply to this note

Please Login to reply.

Discussion

Avatar
Silberengel 6mo ago

The key is that you hone it and refine it OVER THE FEATURES, never directly in the implementation. Otherwise, the business logic gets wiped out, when it changes code. You have to hard-break between the behavior and the implementation.