|
|
|
|
|
by wkoszek
1207 days ago
|
|
Your role as a company is to maximize revenue. If presence of bugs makes you lose revenue by customer churning or burned-out developers leaving, fix bugs. If not, create new features. And define a bug as "thing that the customer complained about". If customers don't complain, it's either not a bug, or you are solving a wrong problem. |
|
I’m not disagreeing that customer complaints are important for prioritisation, but the problem isn’t quite as first-order as that.
In an extreme case, imagine you found a bug that corrupts data if a customer name begins with z. Would you not fix this bug just because you don’t have any customers whose name begins with z?