←back to thread

177 points foxfired | 1 comments | | HN request time: 0.23s | 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. Suppafly ◴[] No.43618422[source]
With a lot of the products I support, I suspect the real reason is that they had originally hired outsourced programmers, or got rid of most of their in house programmers over the years, and literally have no ability to fix simple issues in a cost effective way. It's why they always try to push you to the next version of the program that is a ground up rewrite instead of continuing to support the existing version.