I'm not so sure why we have to start with what the tool can not do. Especially the tool is trying to do things that nobody else did. Idea starts small.
While I like the test driven approach and the framework you're promoting and also agree with much of your talk, a lot of your argument against swagger assumes that people using Swagger use it exclusively and write nothing else. That is far from realistic. If you put the effort into writing decent documentation (as you recommend and your tool requires) then swagger supplements the written documentation rather than replaces it.
Thanks a lot for this helpful presentation.
Great presentation, this.
I'm not so sure why we have to start with what the tool can not do. Especially the tool is trying to do things that nobody else did.
Idea starts small.
While I like the test driven approach and the framework you're promoting and also agree with much of your talk, a lot of your argument against swagger assumes that people using Swagger use it exclusively and write nothing else. That is far from realistic. If you put the effort into writing decent documentation (as you recommend and your tool requires) then swagger supplements the written documentation rather than replaces it.