I agree strongly with this, and it's not a new phenomenon. A lot of older engineers will recall when management tried to measure us with LOC metrics. Today we h

I agree strongly with this, and it's not a new phenomenon. A lot of older engineers will recall when management tried to measure us with LOC metrics. Today we have a whole culture built around speed. And yet a lot of the younger folks I work with seem to have trouble thinking deliberately through a problem and coming to a good solution. It's not their fault, imo. The pressure to move, move, move is tremendous. That Darwinian aspect of a market is not going away, but neither is the fact that writing good, solid software is a very contemplative and design-driven process. In my pretty long career I don't recall hearing of any projects that failed because they couldn't get code written quickly enough. I'm not sure why it is we always seem to come back to "fast" as the most desirable attribute of a programmer, but I suspect that it has something to do with the inability of management to accurately gauge risk or estimate timelines for a process they cannot really comprehend.