I think the author glosses over the issue of keywords. In order to be productive in the Wolfram Language (or any language), you need to build up an understandin

I think the author glosses over the issue of keywords. In order to be productive in the Wolfram Language (or any language), you need to build up an understanding of what operations it supports. There are thousands of such operations, neccesitating a method of looking up the correct operation for each task. And it's not always clear how to glue them together. What kid would think to type "GeoPlot" or "{n,20}" unprompted? In other words, people still need to build a mapping between their internal desires and valid syntax. We are still a long way from being able to compute in the language of thought.