6 ms·

Will repost an earlier comment of mine: "I met a director from Tesla just after their unveiling of the Model X. She said a small number of people were assigned

Will repost an earlier comment of mine: "I met a director from Tesla just after their unveiling of the Model X. She said a small number of people were assigned to fully assemble / prep each vehicle shown that night.. for roughly two weeks they worked 20 hour shifts and slept 2 hours each night. Most teams were working on them right up until the cars rolled on stage; there was still wet paint on one. Also, it was said a "normal" workweek of 16 hours days isn't uncommon.. She can't wait for options to fully vest and gracefully exit. It's not for lack of thrill, growth, etc. – just that after 3-4 years it is heavily taxing and a pace of sanity is much desired."

bsaul 10y ago
That's really something i don't understand. After 5 hours of intense work i'm unable to code or think anything. I may be able to do many 4 hours work periods if i'm resting inbetween, but i can't do it multiple days in a row, otherwise i simply start slowing down and take bad decisions. The best decisions i take are usually in the morning after a good night of sleep, and the problems i've been struggling for the evening simply seem a lot easier. Even in week-end hackathons, the rookie's mistake is to not get enough sleep in the friday evening, create bugs during saturday, and end up completely unable to work on sunday. Whenever i coach team, i usually tell them not to run the wrong race. If you're running a marathon, don't run at maximum pace because you'll never make it to the end.
- 56k 10y ago
  Same here. Management work is different, though. More about making decisions than being hands-on.