Same dev tools/language/framework for everyone?
gaius: It totally depends on what your company does. If all the development is a particular style (web apps, desktop apps, embedded systems, etc etc) then it makes a lot of sense provided the choice of tool is periodically revisted and also provided that it's chosen for the right reasons (i.e. not just someone senior's "favourite toy"). You don't want to put all your eggs in one basket and end up in a technological dead end with nowhere to go but a rewrite. I'd argue that that's what's happened to everyone who thought J2EE was a good way to build websites...If however you have a lot of different things going on (e.g. your company's main business is programming embedded systems and happens to have an unrelated group doing your website and another unrelated group doing internal desktop apps for business users) then a one-size-fits-all strategy is likely to be suboptimal.