Speed over quality will always come back to bite them.
The technical debt will build up to the point where it becomes unmanageable, the business reputation will be destroyed and customers will leave.
Quick fixes work for short term issues, but consistent unrealistic deadline targets are detrimental to the business.
Usually as a result of overselling the capabilities of the business.
A customer informed of a realistic deadline and cost, early in the project will be be more understanding and a respect will build, especially if you can achieve the desired result.
It also means that future work will be more efficient for the company and the customer due to that lack of technical debt, as you achieved they will come back for more business and build the company a reputation for delivering quality, on time.
I see your perspective, we need to meet business goals.
I agree, within reason, but apportioning blame is not constructive, the focus should be on the solution and fixing the problem, not singling people out due to some minor timing issue, due to some typically arbitrary timing set by the customer.
Obviously there are extreme cases where blame is necessary.
They do sometimes have business requirements, that need a specific timing and that is normal.
But if the modus operandi for the business is speed over quality, it will eventually burn them.
As with most things in life, there needs to be appropriate balance.
Now everyone's perspective is different and it will always be a matter of opinion.
Quality attributes are business requirements. They are just the ones easily forgotten/ignored. Customers request functionality (they ask for this), but they expect quality (they do not ask about this).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I.e. toxic work environment.
Speed over quality will always come back to bite them.
The technical debt will build up to the point where it becomes unmanageable, the business reputation will be destroyed and customers will leave.
Quick fixes work for short term issues, but consistent unrealistic deadline targets are detrimental to the business.
Usually as a result of overselling the capabilities of the business.
A customer informed of a realistic deadline and cost, early in the project will be be more understanding and a respect will build, especially if you can achieve the desired result.
It also means that future work will be more efficient for the company and the customer due to that lack of technical debt, as you achieved they will come back for more business and build the company a reputation for delivering quality, on time.
That's assuming they have not moved on to the higher paid position by that time.
And when the fire is put at their feet, it's their subordinates who are to blame.
I see your perspective, we need to meet business goals.
I agree, within reason, but apportioning blame is not constructive, the focus should be on the solution and fixing the problem, not singling people out due to some minor timing issue, due to some typically arbitrary timing set by the customer.
Obviously there are extreme cases where blame is necessary.
They do sometimes have business requirements, that need a specific timing and that is normal.
But if the modus operandi for the business is speed over quality, it will eventually burn them.
As with most things in life, there needs to be appropriate balance.
Now everyone's perspective is different and it will always be a matter of opinion.
Quality attributes are business requirements. They are just the ones easily forgotten/ignored. Customers request functionality (they ask for this), but they expect quality (they do not ask about this).