Javascript has decent feedback cycle, but pretty bad program state persistence as you reload things, there are some attemps and sometimes Vite is able to do it,

Javascript has decent feedback cycle, but pretty bad program state persistence as you reload things, there are some attemps and sometimes Vite is able to do it, but it's a pretty sad state of affairs in general. The end remarks are more to let the imagination run a little bit free than anything particularly structured, the part about deployment doesnt really exist as it is in most companies, there is a concept of canary deployments, blue green, etc, but not on a running process ala Erlang or Elixir. Still, Im not sure if it is even a good idea since starting from a clean slate is usually good. I need to do more testing around this. There is no interest in documentation while the process of discovering is going on, because the documentation would be stale as soon as you move on in the discovery process. Its not even a fault of the system, it just doesn't make sense. Once you find a good enough design, then you transition into settling it, documenting it, writing more thorough tests. About the review process, this is mostly targeted at individuals and teams where there is a certain trust involved. But for knowledge spread that's why I also tackle doing this collaboratively, as I think it could even increase the effectiveness of this approach. The design was pretty fast done with a template. I'll see if I have time today to test other fonts and see how it improves. Thanks for taking the time to read