3 ms·
Lessons from Mark Zuckerberg, Founder and CEO of Facebook: http://blog.facebook.com/blog.php?post=2208562130 This was a big mistake on our part, and I'm s
by temphn 14y ago
Lessons from Mark Zuckerberg, Founder and CEO of Facebook:
http://blog.facebook.com/blog.php?post=2208562130
This was a big mistake on our part, and I'm sorry for it.
But apologizing isn't enough. I wanted to make sure we did
something about it, and quickly. So we have been coding
nonstop for two days to get you better privacy controls.
Lessons from Yishan Wong, Director of Engineering at Facebook:
http://www.quora.com/What-are-some-good-questions-to-ask-yourself-to-determine-if-you-are-ready-to-join-a-startup
Working at a startup doesn't necessarily mean long hours,
but it does mean that it's not the hours that count, it's
the results. If you need to work 80 hours to get
something done by next week, you will need to do it
because otherwise the startup might die - in a large
company, this might just result in some mild consequences.
Startup life tends to go in bursts. You should be
comfortable with this.
Had Mark Zuckerberg left at 5pm in the middle of the news feed crunch, the company probably would have died before it was able to pay Sheryl Sandberg so much money to work 40 hours a week. Instead they coded 48 hours straight.
- j_baker 14y agoWell that was certainly nice of him. Did you have any evidence that Sandberg's strategy is wrong for her or even the majority of people in the tech industry, or were you under the impression that an anecdote from a completely unrelated incident years before would actually prove something?
- wpietri 14y agoI believe the difference is "normal" versus "emergency". My startup aims for a sane work-week, but if something caught on fire I would be there until the fire was put out. As long as that happens rarely, it's not a problem. And you keep it that way by carefully analyzing each fire and making sure that you solve the root causes.