If the product is for people who think adding unnecessary machine learning to simple tasks then sure, I'm not the audience but a condescending "you don't get it" is not really adding any clarity. Do you get it?
If the product is for people who think adding unnecessary machine learning to simple tasks then sure, I'm not the audience but a condescending "you don't get it" is not really adding any clarity. Do you get it?
But just saying "I don't need this and it probably wouldn't work even if I did" doesn't add any clarity either. :-)
What would add clarity is to ask the creator whether they see it being applicable in a particular use case, and you can give your specific use case, and give them the chance to say "yes, here's why" or "no, the product doesn't help you". Then future readers can see the use case and decide if they have similar needs to you and it would greatly help their purchasing decision.
Honestly, I wish more product discussions were focused like that. "Here's my situation" and the entrepreneur gave an honest "yes, here's why" or "no, the product doesn't help you". But it typically is just a commentator saying "I don't need this because I solved that problem myself" and the product person claiming that it works in every use case, so other readers don't get as much of a benefit from the discussion.