wserjifowe

I think it's not going to be so obvious. If you write a feature that is intended to deceive then sure, but the developer who wrote that feature was probably told "ok, if the inventory is below a certain threshold, then add this behavior". The feature itself is benign. Should a developer resign anytime they can concoct a theoretical way in which a feature they're writing could possibly be exploited?

I think things get murky with complex relationships that exist in industry. For example, I think it would be hard to argue that a company like Expedia or Priceline created a feature so their customers (hotels) could exploit it.

Also, what leverage do you think a developer has in these sorts of situations? Should the developer say they're not willing to write the feature because it's possible customers could exploit it?