A better representation would be me speaking these phrases to you in person
So, essentially the same TEXT in audio format? Doesn't that simply proved the point that the TEXT is already the, conceivably, most concise and precise representation of your idea?
No. First, there are benefits unique to audio interaction (immediacy, tonal emphasis, emotion); next up, benefits to physical presence (enhances interaction - e.g. pointing, gestures, a wider visual canvas), and finally you skipped this last bit with the pretty pictures... :)
"...code editors open in front of us, trying to demonstrate certain use-cases where visual coding is superior."
Regarding your comment "Good luck trying to debug a program from its visual representation.", do you remember savePipelineToFile and restorePipelineFromFile? :D Those features make it trivial to debug and replicate errors between environments.
On and off, I've programmed in both Java and Perl since the mid-nineties. I still use both in my 'webMethods' job when Flow js unsuitable. But for core integration work, webMethods Flow programming beats text-mode programming hands down. It wouldn't survive so long (neither would my job), if this wasn't the case. In fact, my personal view is the only reason for webMethods to thrive is Flow makes even average coders (like me), way much more productive then they ever would be CTRL+SPACEBAR-ing away in Eclipse.
Sadly, Software AG (and webMethods Inc. before them) have let webMethods Flow wither on the vine. There's so much they could have added to it by now - both in terms of visual language enhancements and visual tools. For example, diff and merge tools, environment comparison tools, code metrics and estimation tools, temporal debugging, automated test case generation (by using the input pipeline persisted on error), automatic documentation, some form of AoP...