Just speaking about Houdini makes me want to pick it up again.
I found that the complexity lied in knowing all the different nodes, the jargon, and of course when to use what (which comes with experience).
After a month or so I bailed out because of time constraints, my daily job, and other side projects.
If you're a programmer does it affect the way you think about things ?
I was highly infected by such programs (Maya hypergraph, SekD Samplitude non destructive virtual tracks; all share this lazy composition of generic nodes) before entering a computer cursus and it shapes everything I do ever since. And since few people experienced that level of generative-ness, I often look like a fool.
I think in a way all those roads lead to functional programming.
Of course, in an enterprise world most people's eyes glaze over when you mention any of this.
To answer your question, I do think it influenced my thinking and made me a better programmer. Even at work, where I mainly program in C#.
I'm in general not that big a fan of visual programming and prefer text myself.
The CmiVFX tutorials about building towns, nature.. anything procedurally were a long and dense brain rewiring. It's almost not about using Houdini, it's about solving a problem with generic functions.
Houdini earns a paradigm name as many things in Houdini are built in Houdini, which is .. well math with interfaces. At least back in 2005, the skeletal animation system component was a encapsulation of geometry primitives bound by some arithmetics, you could open and edit it as any other surface or object. Turtles all the way down. Beautiful. Reminds me of Emacs/Lisp actually, once inside, you won't leave.