You can theoretically ship at any time. But it might be broken, slow, harmful, or fail some critical objective. Team dysfunction is inseparable from tech dysfu

You can theoretically ship at any time. But it might be broken, slow, harmful, or fail some critical objective. Team dysfunction is inseparable from tech dysfunction. Imagine one team owns three quarters of this service as another owns half of it. Or more likely, one owns a tenth of a problem space and another owns a fifth. Suddenly you need a fully realized solution. Who will step up? Well, you’re the one who actually needs it…but surely you don’t have to start from scratch? Surely…? Then there’s just the fear of showing your ass. The day after it launches, who will be in hot water? Will it be you, because you agreed with the PM that your substandard code could ship? Why didn’t you flag the problem earlier? Get more help? Tell someone you weren’t already a superstar at this infra or that architecture?… And then recall they did ship, it sucked, they bought Instagram. Then WhatsApp. And dozens of others I guess the lesson is: yelling “go faster!” at a blocked-up engine is only gonna go so far. Mark’s (and many others’) move is to apply money to replace or get additional engines. Or roll up your sleeves and fix the org and culture…doesn’t have exactly “founder mode” romance to it tho, and there’s scarcely a harder task out there.