One of the first things I do when working on a new stack is to tighten the feedback loop as much as possible.
Usually a combination of hot reloading, good intellisense / autocomplete / quick docs, debugging.
I did a talk and built the animations with Manim (mathematical animation library) and at the time you had to render the clip and play it each time you wanted to preview it, causing a significant delay (10-15s) between each change and what it looked like rendered.
It was unbearable (but finished the project). Afterwards, I put together an environment using p5.js that allowed instant feedback, even at a specific point in time. I also threw in an in-browser editor so I could keep working on an animation on my phone as I was doing a lot of walking around that time (usable, but barely).
Usually a combination of hot reloading, good intellisense / autocomplete / quick docs, debugging.
I did a talk and built the animations with Manim (mathematical animation library) and at the time you had to render the clip and play it each time you wanted to preview it, causing a significant delay (10-15s) between each change and what it looked like rendered.
It was unbearable (but finished the project). Afterwards, I put together an environment using p5.js that allowed instant feedback, even at a specific point in time. I also threw in an in-browser editor so I could keep working on an animation on my phone as I was doing a lot of walking around that time (usable, but barely).
This was the result of that project:
https://github.com/jasonjmcghee/viz-studio
https://viz.intelligence.rocks/