I think perhaps a critical part of the equation is in creating a seamless mix of code and no-code. In my environment I never have to choose between the two. I

I think perhaps a critical part of the equation is in creating a seamless mix of code and no-code. In my environment I never have to choose between the two. I code when I need to code, I use the automation when it suits my need. Take excel as an example. It already does a lot (no code) but allows you to code (vb script) when you want to and if you have the skills. My field is even more niche - I'm the guy writing new code, then exposing that code, and integrating that code, into the no-code layer. I'm not limited to "what is available" - it's a full language under the hood. Well multiple languages actually. In addition to the system language I can also write C, or even assembler, that's all part of the system. So I just drop down as far as I need to go.