Thank you 
I used scripting basically to work faster. Since there are 16 stones taking part on a choreography, and each one has animated properties in a timeline with hundreds of keyframes, I wanted to avoid repetitive work like randomizing animation curves, or activating and deactivating things manually. But the most crucial part was something rather technical: I had the movie split in scenes, and I needed to transfer the physics engine state from the end of one scene to the beginning of the next one. So I wrote a script to do that.
And yes, the results can be amazing but it’s not very inviting towards experimentation with code. The documentation is not so easy to understand or even complete. Maybe I should play with it and then make some tutorials
One thing I would point out: working with Blender for two months changed my view about creative coding. Often, when you work with Processing or openFrameworks for a while, you start to need a framework that includes saving and loading configuration files, maybe animation timelines, a gui and lots of non-visual related code. Many people spend years iterating and building their own interactive system. Which is cool, and probably always unique. But when I see the massive GUi in Blender and all those thousands of options I think that I will never build such a complex environment myself, and I may just as well use Blender instead It just an idea, and not a decision. Of course you don’t need to build something so complex to create amazing work. But the truth is that I really enjoyed creating materials with nodes in the shader editor, replaying animations a hundred times while tweaking animation curves… It’s different. With Blender you are probably trying to do something polished with a fixed duration, instead of a living real time system (what you would create with Processing or similar). Combining both tools is another interesting option.