A lot depends on who you are programming for. Usually it is for a company that places more importance on a deadline than anything else, including quality. Other

A lot depends on who you are programming for. Usually it is for a company that places more importance on a deadline than anything else, including quality. Other "ilities" are even less relevant. So you just hunker down, and produces something that "works" very fast. For, say, a small dataset. Then either the project finishes (abandoned sometimes), or it grows (exponentially sometimes), and what was created fast no longer is usable. So you do it once again, now to support the new requirements. And so on. We are constantly rewriting systems, as we continuously copy data from different media. It keeps us employed. It is much easier to be remembered for doing something fast than for creating something that lasts.