So I'm guessing this wasn't ever a real situation, just a fantasy story about how he'd love for an interview to play out.
Somehow, this does not come across as a fantasy being played out, more of a cautionary tale.
Seems incredibly bleeding edge for an interview question.
And then the start of his reply is 'Using babeljs.io, I’ll write this in ECMASCript 2015 notation.', which is weird given the example code was already implied to be in this.
Then when it becomes hard to find good people, Thing suffers because they are too quick to reject people based on one answer. And if the Carpenter finds there are few jobs that suit his criteria, he has trouble getting one with the style of answer he tries to jam into every question.
That’s a bit of a metaphor for how many (but not all) companies become internal shit-shows in tech. They get a lot of positive feedback (raising money, adulation from HN) for their tech, but meanwhile are terrible managers.
It takes great discipline (and possible great mentoring) to say to yourself, “things are going well, but what am I doing wrong that I just happen to be getting away with?"
FWIW, the meaning I took away from it is "Well, this is a cool way of looking at things. Some people will run away screaming, some people will appreciate it. If you want a happy life, find the people who appreciate it and don't worry so much about the people who don't see things your way."
Despite using a bunch of fancy new language feature, name-dropping Knuth, and describing the solution for an hour, the result is code with no additional benefit and significantly worse maintainability.
Sometimes being smart doesn't have to look so smart.