> The measure of good programming _ought to be, but isn't and never will be in the eyes of the people who are actually going to make it into a position of autho

> The measure of good programming _ought to be, but isn't and never will be in the eyes of the people who are actually going to make it into a position of authority_ is not whether you solve that problem (that is a given) but by how much future headache your solution causes As Dilbert points out "our boss can't judge the quality of our work, but he knows when it's late". The only measure of good programming that will translate into actual tenure in an organization is: how fast did you get it done? It's been this way for 50 years. It won't end tomorrow just because you're right about the way things ought to be.