3 ms·

> when a bug pops up That’s reacting to a bug you know about. Do you mean to talk about how developers aren’t good enough at reacting to bugs found in third pa

> when a bug pops up That’s reacting to a bug you know about. Do you mean to talk about how developers aren’t good enough at reacting to bugs found in third party libraries, or how they should do more prevention? In this case, it seems like OpenAI reacted fairly appropriately, though perhaps they could have caught it sooner since people reported it privately. “Holding someone responsible” is somewhat ambiguous about what you expect. It seems reasonable that a car manufacturer should be prepared to do a recall and to pay damages without saying that they should be perfect and recalls should never happen.

JohnFen 4y ago
> Do you mean to talk about how developers aren’t good enough at reacting to bugs found in third party libraries, or how they should do more prevention? My point was neither of these. My point is very simple: the developers of a product are responsible for how that product behaves. I'm not saying developers have to be perfect, I'm just saying that there appears to be a tendency, when something goes wrong because of external code, to deflect blame and responsibility away from them and onto the external code. I think this is an unseemly thing. If I ship a product and it malfunctions, that's on me. The customer will rightly blame me, and it's up to me to fix the problem. Whether the bug was in code I wrote or in a library I used isn't relevant to that point.