The harsh language there is not being "capable of understanding a brilliant language." I'm not aware of what was meant by a brilliant language, but I have to assume that it means research languages. I would not expect fresh grads to build production worthy code in any language, but especially not in a research languages (which typically are relegated to the realm of research because they are not capable of being used by large teams for the making of good software).
I'm in the business of creating value with good software, not ivory tower building that only a smaller proportion of software artisans can build and maintain.
And that's a bad thing?
When we can talk to an AI and describe something novel and it can interpret that, then I'll start to worry about software development jobs being lost to AI.
Naturally those developers are also entitled to have jobs, the question is how it is actually done in practice.
Sadly a large majority are sweetshops.
“The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.”
-- Rob Pike
From https://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Fr...