I'm not really sure what point you're trying to make here. I completely fail see the logic behind 40-hour days making it hard to be a team player. I have to say most of the time as a programmer I'm staring at a screen on my own, even when I worked on a projects with 50 people.
But then I've never been someone who was capable of being productive on 18-hour days. Even at LAN parties, when I was 16, I used to be the first one to go and catch some sleep. Still, having worked in the games industry, I'm no stranger to 12-hour workdays, and communication (face-to-face or otherwise) has never been anywhere near the bottleneck for me there. On the contrary, I used to get the most done in the quiet 1-2 hours before everyone else turned up.
As far as I'm concerned, it's one thing for the founders of a company to put in a lot of hours, but I'd never work for another company expecting employees to do so beyond a reasonable extent (i.e. only when truly urgent).
But then I've never been someone who was capable of being productive on 18-hour days. Even at LAN parties, when I was 16, I used to be the first one to go and catch some sleep. Still, having worked in the games industry, I'm no stranger to 12-hour workdays, and communication (face-to-face or otherwise) has never been anywhere near the bottleneck for me there. On the contrary, I used to get the most done in the quiet 1-2 hours before everyone else turned up.
As far as I'm concerned, it's one thing for the founders of a company to put in a lot of hours, but I'd never work for another company expecting employees to do so beyond a reasonable extent (i.e. only when truly urgent).