This should be required reading for all software engineering / computer science majors, but it's not. Would replace so much other useless junk that kids are taught in school these days and would actually help produce grads worth hiring (currently, there are none - globally).

It won't help. It's almost impossible to see the value in Joe's work until you have to build a complex distributed system yourself. Takes years.

A problem with Erlang itself, you've got to have done it the hard way a lot of times to see the value in some of its built in things.

No grads worth hiring globally? I don't hire, but that seems a bit rough anecdotally knowing a few.

I had a quick read of some parts, but I'll have to sit down and read it properly tomorrow once the beer has taken its course. I didn't find the bits I browsed particularly revelatory, and focused fairly narrowly on erlang.

Any particular sections you think would turn those unhirable grads into hirable ones?