Hoffenheimer
Trollope stands out for he had this to say, "All those I think who have lived as literary men, -- working daily as literary labourers, -- will agree with me that three hours a day will produce as much as a man ought to write. But then, he should so have trained himself that he shall be able to work continuously during those three hours."
That number might just be a biological limit. You might be working at full capacity already and your brain "procrastinates" in order to recharge. It's very difficult to tell when the brain is tired since you can't feel it, but wanting to do other things -- specifically things that take less mental energy like reading blogs/forums and playing games -- seems like a good signal of fatigue.
One thing you can try though is to split up your day into different blocks and focus on recharging in the time between those gaps. Say, do 3 hours in the morning and 3 hours in the late afternoon and just completely relax and do whatever the hell you want in the meantime.
If he went to experience it, got caught up in winning and didn't enjoy any of it then perhaps he would have some sort of point.
How do you know he didn't get into racing for the experience of it? Seems like that's what his whole point is -- he got 2nd at Le Man's ('rich boy' or not, still a good thing), but instead of enjoying such an achievement, he's caught up in the fact that he didn't win.
I don't think it hurts anyone when he says he's helping solve cancer, he's not stealing anyone's thunder. There's plenty of evidence of tool/library developers not getting any credit in the end product. If someone directly finds a cure using Light Table as their IDE, I'm pretty damn sure not a lot of people are going to seek out Chris and congratulate him on curing cancer. But he would've helped and that's the important thing. So let him have his motivation and keep building things.
The most powerful part about pure functional programming is that you get more powerful functions. Because your functions don't change the state of data, you can confidently combine them into new functions, producing a sort of chain effect. This can lead to very concise programs since there is no need to hold intermediate variables (i, count, temp, ...) in some place. What you sometimes end up with are one liners that -- if the functions are named well enough -- explain the entire logic of the program.
There are certain problems that lend themselves well to the functional style, mainly those where you are piping a piece of data through various functions and applying different transformations to it. It's worth learning at least a couple of functional languages so you're not applying a hammer where you need a wrench.