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 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).