I just got through https://www.amazon.com/Specification-Example-Successful-Deliver-Software/dp/1617290084 https://www.amazon.com/Specification-Example-Successfu

I just got through https://www.amazon.com/Specification-Example-Successful-Deliver-Software/dp/1617290084 https://www.amazon.com/Specification-Example-Successful-Deli... which pitches a common structure (Given-When-Then) for describing behaviors and getting them out of your ticketing systems, which are not designed for knowledge explanation long-term, but are more for describing active work in short term. BDD is almost a poisoned term at this point because it’s become associated with tooling and opinionated holistic processes. But if you think of Specification by Example as readmes with a Given-When-Then structuring, then you have a strategy (document before writing) combined with a language definition to assure your strategy is executed at the right level of detail. Which solves the entangled problem of what do I do first (document) with what level of detail (enough to describe all the input behaviors to whatever I’m working on)