Comment by MattPalmer1086
4 years ago
And that is as it should be (except the blaming for issues you raised).
The business should be able to choose what the priorities are. The business does not exist to produce beautiful code.
If a business wilfully disregards security or stability risks that they were informed of, and they get bitten, then they will almost certainly end up paying more to fix in resource and engineering time. But that's the trade off they chose to make.
If a business plays the blame game here, it's simply time to find another job. They are not going to be a good place to work at all.
As an addendum, I've been on both sides of this argument. When I became the chief technical architect for a software company, I had to tell my colleagues to build a huge pile of crap to hit important commercial milestones and keep customers happy.
I pointed out that the total cost of doing this badly, then unwinding it and doing it properly would be at least double the total cost of just doing it right.
That didn't matter. We had to hit those goals. So that's what we did. It was expensive, buggy and kept us in business. My colleagues finally understood I had turned to the dark side :)