4 ms·
I mean I've seen it happen with unrealistic stakeholders. Business forces the team to make a false commitment to a specific ship date with a specific set of fe
by CSMastermind 3y ago
I mean I've seen it happen with unrealistic stakeholders. Business forces the team to make a false commitment to a specific ship date with a specific set of features. It's obvious that the team can't hit that mark but telling the stakeholders that will just result in them refusing to budge and telling you that you need to come up with a plan to make it happen.
Eventually it's easier to just agree with them and do your best than waste even more time arguing with them. Eventually you fail to ship or you ship a buggy mess. The software engineers know the code quality is shit but they don't have time to think or set anything up.
- pylua 3y agoThat is called fraud.
- deleted 3y ago[deleted]
- thowaway91234 3y agoIt’s either more time or less features. Less testing is non-negotiable.
- harimau777 3y agoDevelopers generally don't have the power to make that decision.
- thowaway91234 3y agoNot with that attitude.
- The_Colonel 3y agoYes, this is a common scenario for sure. But it's always "we don't write tests because there's no time" and not "we don't write tests since they might reveal bugs, and we don't want that" as the article claims.
- pseudalopex 3y agoThe article said developers don't want to find bugs because of time pressure. But it didn't suggest fixing the time pressure.
- biql 3y agoSo they lie about estimates because they afraid to miss their chance to delivery buggy mess. But doesn't it do more harm to the reputation in the long term?