And I'd argue that a well-designed UI only goes so far, and that eventually you need the expressiveness of some sort of programming language. This suggests a hierarchy of user interfaces for complex tasks:

structured language > purpose-specific UI > natural language (processing)

Old adventure games were really illuminating with respect to limitations of natural language interfaces. Rather than allowing for the expressiveness of natural language, you simply had the feeling of groping around like a blind child at an easter egg hunt for the few valid operations that existed.

I feel like this using GUI tools for data tasks. It's like being forced to communicate by banging rocks together compared to, say, the expressive power of R or Python.

I wonder if natural language interfaces could leapfrog GUIs if we all up and learned something like Lojban...

"Show me country & city as rows, year as a column, sum the amount of population for country/city combination, show the YoY as a column and the subtotal for city".

Really? That's 3 clicks a way with a well-designed UI.

And what if I have those 3 fields in different tables? Even more verbosity...

P.S: My job has nothing to do with designing UIs, just to dispell any doubt :)