I'm not trying to be argumentative, but hopefully this gives you a better idea of the "other side" as it were, Fourth.

It comes down to the creative process. Right now there's no real way to sketch unless you are an expert programmer. It seems like many of us commenting here are not; we use programming as a means to an end.
What sketching does is take you to a state of mind that's very right-brained. It's holistic thinking, where associations are made that aren't normally made with logical thinking. Text-based language and logical thinking are left-brained, both of which are the realm of programming.
The goal then, for a more right-brained style of software development, is to not have to think about the logical side and to purely express ideas, just like sketching or free writing. One way to do this is to become an expert programmer. Another way is to use tools that do as much of the left brain stuff as possible so you don't have to.
Personally, I'm no longer afraid to learn more programming, that fear left me over a year ago. So I could become an expert programmer...but I don't want to. I know that takes time, and I'd rather spend that time designing experiences. I'd rather spend that time more directly living out my own principle.
Even so, I think there's some validity to the fear of becoming an expert programmer. It changes how you think. And that could lead to seeing certain design situations as a problem that needs to solved. That's how much of game design has worked up to this point, and if you want to go in a new direction, it's worth considering different ways to think.