Comment Whose bug is it anyway? (Score 4) 108
When my company releases a new version of our software, it inevitably has some problems in it, due to (a)our customers demanding new features fast and (b)limited testing resources. We do take responsibility for all bugs that *we* introduce, naturally, and fix them ASAP.
However.
Sometimes M$ will release a new version of DirectX which causes our application to stop working (pretty much every release has done this). Whose bug is this? Is it M$'s bug? As much as I'd like to blame them, they *do* have the right to change the API. And generally, newer versions of DX have sucked less than the previous versions. Is it ours? Our code was 100% compliant with DX(n-1).
This is the kind of situation that bothers me the most, quite frankly. Our software runs right, but because the user has changed/has never upgraded/is experimenting with/has poured water on their computer, our software ceases to function. We work to fix these bugs, but I refuse to believe that some *fine* of some kind would help. Better customer communication is all it really takes...
However.
Sometimes M$ will release a new version of DirectX which causes our application to stop working (pretty much every release has done this). Whose bug is this? Is it M$'s bug? As much as I'd like to blame them, they *do* have the right to change the API. And generally, newer versions of DX have sucked less than the previous versions. Is it ours? Our code was 100% compliant with DX(n-1).
This is the kind of situation that bothers me the most, quite frankly. Our software runs right, but because the user has changed/has never upgraded/is experimenting with/has poured water on their computer, our software ceases to function. We work to fix these bugs, but I refuse to believe that some *fine* of some kind would help. Better customer communication is all it really takes...
