←back to thread

177 points foxfired | 1 comments | | HN request time: 0.203s | source
Show context
esafak ◴[] No.43618222[source]
It depends. Some other reasons:

1. It's an enterprise product and the economic buyer doesn't know or care about bugs as much as checklisted features.

2. The company is not connecting the impact of fixing bugs to their bottom line. Or they are and estimate the impact to be low.

3. The code base is due for a rewrite so it would be a waste.

4. It's a side bet not worth the extra resources.

replies(6): >>43618291 #>>43618343 #>>43618422 #>>43618825 #>>43618896 #>>43619003 #
1. tetha ◴[] No.43618896[source]
At work, we've also delayed the rollout of bug fixes by a month or three at times. If the customers are in a big Christmas / end of year / event rush, a known bug - that takes a minute to work around - is sometimes preferable to an unknown fix - that might cause the entire operation to stop for an hour.