I'm a designer and I understand what you mean. There are two different things going on here...
1. Design also has its own "architecture astronauts", people who theorize a lot but don't get things done. They are usually in academia, since there are not many companies willing to pay for design astronauting.
2. Design, despite being more closely related to engineering, is usually expressed from the perspective of art. That's why I think most programmers have problems getting a grasp of it. The reasons are mainly historical, but fortunately people are paying more attention to more rational approaches to design (Tufte, Krug).
To me it seems the author is trying to overreach the scope of UX (when it's already huge) with vague ideas of where it should head.