Rule number one: don't piss off your programmers. Programmers produce things that are largely unintelligible to management. The whole reason we have arguments

Rule number one: don't piss off your programmers. Programmers produce things that are largely unintelligible to management. The whole reason we have arguments about processes is because we can't measure the productivity of our programmers. It's difficult to even measure the quality of the work without getting other programmers involved. Even if there is a serious bug, how do you determine if it's due to bad luck, sloppy coding or sabotage? If a previously exceptional employee stops being exceptional right after you stressed them out is it because they are being stroppy or because they are stressed and can't perform? Do not piss off your programmers. They can sink your boat either because they are stressed out and can't perform or even just because they are pissed off. If your company policies involve pissing off your programmers, you are in a pile of trouble. The real answer to this guys question is: If you can't fix your policies so that your programmers are happy, then find another job. This one is done.