> Mark didn’t accept anything less than perfect. If he thought something was shit he would tell you and you’d have to start over.
Perfection seems a bit incongruous with moving fast and breaking things. Maybe different standards for copy (assuming this was external facing and not an internal document) vs code? Still a bit weird.
That particular right to flexible mistakes applies only to him. The employees get the privilege of 3 am emails nagging them about punctuation.
I'd love to see the guy apply such harsh standards to his own firm place in the company.
If you are still up at 3am that’s a problem in the first place, but being asked to fix a period when you are up is not.
Perhaps being a billionaire changes your view on perfection but I'm not sure I buy the narrative about him being a perfectionist given how decidedly mediocre a lot of what he's touched is.
Actually it's more like ten percent luck, twenty percent skill, fifteen percent concentrated power of will, five percent pleasure, fifty percent pain. Wait, what were we talking about?
Not true.
Source: worked for Zuck.
As for 3.00 am and a missing period. Well, trying to judge someone on a sample size of one is heavy handed.
Email aren't meant to be responded to immediately.
Do it.
Do it right.
Do it fast.
So in this case, Move Fast and Break Things means that when an aspect of the work is in phase 1, there should be evidence of things breaking so you know that progress is happening at the maximum possible speed. Then because things are moving fast, work quickly moves into phase 2 of taking the breakages and fixing them to a high standard. Although I make no claim as to how it actually worked at Facebook.