If #1 is pervasive throughout an application, e.g. badly done SQL code, then it can be a pain to get performance up, but with #2, there may be no way to get the

If #1 is pervasive throughout an application, e.g. badly done SQL code, then it can be a pain to get performance up, but with #2, there may be no way to get the codebase back under control, or bring new developers on at a reasonable pace. I think the consensus seems to be that #1 is manageable, but #2 is a potentially project threatening issue. It's a shame that 'You Ain't Going to Need It' hasn't permeated to all areas yet, but with many people working at cost+, hours billed often tends to be maximized in worse projects. It's a shame that there's very little mechanism to be paid more for doing a great, undramatic job, than a 50% over-budget cluster-flock code-dump that people hate.