hoodie VS cookies.js

I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.

Sure you might not be able to write 100% of the documentation in one go and then the code, but AFAIK that's neither the goal or the intention of DDD, it's more like "document a bit, write a bit, repeat".

The way I do it is first write a draft of the documentation, of how I want the API to look like. Then check if that basic code is possible (which I can predict most of the times based on experience), then write some more docs or methods. When writing a lib I normally already know where I want to use it, so I can put example snippets from how I want to use it as the documentation first and then try to implement those methods.

Examples of libraries I've written mostly this way:

- https://github.com/franciscop/brownies

- https://github.com/franciscop/files

- https://github.com/franciscop/backblaze