> <i>And, for the any employees still at Twitter, don’t underestimate the power of a pocket veto.</i><p>This is something I've been repeating to some of my younger colleagues.<p>Engineers aren't really fungible resources, to the extent that these projects require. Ask any manager how easy it is to swap "allocated resources", and they'll probably sigh heavily.<p>People are afraid that if they don't follow their manager's every request, they will be fired. But remember that hiring is <i>hard</i>, and managers are loath to fire someone they've already spent so much effort finding, hiring, and onboarding. Finding someone else to do it can take weeks, months, or longer! Which in many cases risks killing the project altogether.<p>Even if you're at the bottom of the chain, as the person who does the actual <i>implementation</i>, you have a lot of power on what gets prioritized.<p>See also the oft-circulated OSS "Simple Sabotage Field Manual" <a href="http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html" rel="nofollow">http://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabota...</a>