[Schattenbaer]

Part of this is a problem of quantification and immediacy.

Extra time spent doing the work well is easier to quantify as a cost than some issues down the line.

Low quality costs money, but only in time, and it's hard to pin down an exact cost. How much of an outage was caused by a quality shortcut? What percentage of our morale issues are caused by working with bad code? And how much, exactly, do those issues cost us? Was some specific quality compromise one of the straws that help break the camel's back?

Much harder questions, and the causes are often not clearly linked to their effects. Combine that with the human predilection for shortsightedness and our dislike of delayed gratification and you have a system that is stacked against quality.