Idempotent. But non-trivial does have a specific meaning: it means that we don't have any code already written or proven technique that we can simply reuse for or apply to this problem, and some new knowledge will have to be synthesized, and there's a risk in making any estimates of time/cost until more is known.
What's wrong with idempotent? It has a precise, useful meaning
What's wrong with idempotent? It has a precise, useful meaning
It's often misused. Along with orthogonal.
shudder We have a business relationship with a financial company based out of Germany, and their system (which sits on top of replicated Oracle) defines "idempotent" to mean "our database already has a cache of the answer we already gave you". Oh, and they gave us a JAR file of client code that does client-side failover, with a fixed 8-second delay to account for the Oracle replication lag between sites. No coordination between different instances of our client. So now, when one client fails over due to a connectivity blip, the other clients get cached error messages (logically equivalent to 404 Not Found). "Idempotent", indeed.