> If he thinks Google's policies are detrimental to productivity, then he has to put his money where his mouth is and go start a business where he can implement

> If he thinks Google's policies are detrimental to productivity, then he has to put his money where his mouth is and go start a business where he can implement his own hiring policies. That only works if you are good at entrepreneurship and management in general. Most developers aren't (me included), so I think changing jobs to a more compatible company is the better option. At least that's what I tell myself - punishing bad management decisions by quitting jobs/projects seems to be the most effective way of changing how software development is run. > The guy should have quit then publish his paper I think for those who agree with him, his getting fired only proved his point. If he did it the other way around, nobody would have even read the paper.