Some more reasons (as an erstwhile enterprise dev turned gamedev who has embraced visual coding): 1. Merging visual code is basically impossible in my experi

Some more reasons (as an erstwhile enterprise dev turned gamedev who has embraced visual coding): 1. Merging visual code is basically impossible in my experience. 2. Likewise for refactoring. 3. Likewise for finding all references, etc. The above make visual code difficult to scale with larger teams or teams with lots of turn over. 1. Games often are released and that's it (though this has changed significantly) this puts less emphasis on maintenance. 2. In my experience there were way fewer non-technical people involved with the enterprise product. There were designers and PMs, but not so many. In contrast a game is extremely content heavy which means many artists, game designers, sound designers, etc. Visual coding empowers these people. 3. Non-game stuff often has very basic interactive elements/art. Like, you can get away with the system's UI toolkit. Games are the opposite, everything is bespoke because it all has to connect to the game's artistic vision. Visual tools such as shader graphs make this easier. 4. Iteration in games is essential. It's the engine that drives quality. Visual tools empower this. In my experience normal software iterates less or at least differently.