software-as-spec is out of vogue now? I may have misunderstood, but I thought software-as-spec is the same thing as test-driven-development, which I could have sworn is still lauded.
Can you explain why you think they are the same? SW as spec is problematic because whatever the sw does is interpreted as being what it is supposed to do. So how do you identify bugs? At least with TDD the tests serve as some kind of documentation.
I'm no fan of either, generally, but I also don't work on "move fast. break things" type projects.
I'm no fan of either, generally, but I also don't work on "move fast. break things" type projects.