I wouldn’t wait to see what I don’t wanna see. Doesn’t make sense.
Discussion
Say there are technological and performance constraints to this service.
Would you be ok with a one second “screening” time? Is that too slow?
I dunno … if you’re trading off filter accuracy for completion time … I don’t think there is a solution… different users will want differently.
The “implementation standard” that allows users to subscribe to such an algo SHOULD be able to accomodate “options” sent along with the query.
If a developer is concerned that their algo is loosing users cause it “takes too long” then they could simply provide an option to toggle for speedier results.
Thanks for this feedback, will refine the user story.
Let me re-ask the question: what if the fastest performance and result was no less than one (1) second - would you use this reverse DVM service in this case?
Yea. I’m not gonna budge. 💜 Build what you think is best… and iterate options in as it gets used. MHO