I agree FxCop warnings are sometimes intrusive and ignore the context of your application. But you can exclude the rules you do not like from the analysis. I still find FxCop somewhat useful to police and enforce some good coding practices.

The best way to have programmers write quality code is to automatically enforce it. Have an automated tool verify the code for comments and run it on your build server each time new code is committed. I am a .NET developper, so each time I commit code, StyleCop and FxCop are run on the build server. This means my code is always commented, hell even spelling errors are not allowed! If I am too lazy to comment, the build server sends an email to the whole team informing them of my laziness.

I managed to beat every single NES game i put my hands on. But not Teenage mutant ninja turtles on the Original NES. I would always get lost in the airport area, never to find my out. This game really got me insanely frustrated and I eventually gave up. Only recently did I found out on a Youtube video, that I had to jump into a ravine that looked exactly like any other death trap in the game to continue the level. That really was idiotic level design.