Seems that for a beginner, a visual experience while programming could be helpful to understand the problem and tie it to something that feels real and tangible, but that it also slows the process down a lot because of the need to move around in a physical space and so on. I have a feeling that many hardcore programmers would be resistant to a visual programming experience, even if it were optimised better than this game, but your project made me wonder if somewhere in between could be a sweet spot. Imagine writing code, and when you get stuck, you put a VR set on and the code is visualised in a virtual room, as objects, with parameters and connections and you could walk through the code by scrolling time backwards and forwards. It might help you get unstuck and fix the problem while actually understanding the issue, not just trial and error.
I think the Dreams logic system is good at orchestrating high-level behavior, and not actually great at building complex logic. Dreams works not because you can visualize your timers and variables and toggles, but because the underlying game systems are extremely well-designed and easy to control with such a system. In a sense, a lot of the difficult stuff has been pushed behind the scenes. This is not a criticism; I think it's a very good way to design programming environments for others to use.
