One asserts that nerds want to know the details for ego reasons.
The other asserts that he (presumbly as a self-proclaimed "nerd" in this situation) wants to know the details because otherwise he has no idea if the product is even useful.
If the product being sold is actually that simple e.g. "trade stocks with a few clicks" thats fine. But for anything that requires customisation, integration or any kind of technical support thats not true. You need to know the details to know if it will work.
This very much matches the stereotypical enterprise sales disaster i.e. buzzwords and flashy things sold to c-suite that are then suffered by those who actually use them and find that it doesn't do what they need
EDIT: also in this context where the article title specifically mentions "technical documentation" we are clearly not looking at the super simple type of product.
Car mechanic buying bolts needs to know thread and sizes of bolts, he does not care about "our bolts are best bolts in the world", if he would spend an hour with sales rep that feeds him marketing and in the end it turns out they don't sell what that mechanic needs, it will make him angry.
IT people or "nerds" know what they need and they have specifications to meet. Making it an "ego" thing is silly :).
A max strength before shearing/failure is just another req. for the task the mechanic wants to know, it doesn't make them objectively worse unless they were used in a situation where they needed to be stronger.
That seems pretty antagonistic for no reason.
> You parent comment basically says the very same thing
How so? The original comment said that a lack of information hurts nerds' feelings because having information is a matter of pride for them (so for emotional reasons, not rational ones). Your parent said they need information to make a well-informed decision, not for emotional reasons. How is that the same thing?
Taking the SAML/SSO example of the grandparent post, the odds are that the only time the poster will hear of the product is when they're asked to do the integration to make logins work. It is unlikely that they will know or even care about what shiny features the product has, since they're not the expected user base. If there's simple documentation on integration methods freely available online, it's easy enough to read it in half an hour or so and figure out how feasible the setup is likely to be in your environment. Going down the demo/chat route is likely to take a good 1-2 hours minimum, and the likelihood is that much of that is wasted sitting through presentations for the product side. That's great for the actual customers, but not useful for the technical staff the customers brought along to make it work. If you're lucky, you might get to actually speak to technical staff that can explain the SAML/OIDC setup steps in call 1; often, you might well have to set up a second call to actually discuss the technical requirements if not more. With many such integrations, the time quickly adds up...
You parent comment basically says the very same thing, that you (a IT professional / nerd) are looking for different marketing messages (actual product details) than other users.
Others, who would prefer an "intuitive" product that "works out of the box" and is "so simple" that even the middle aged house wive can easily trade stocks on XYZ (which like 50% of the ads I receive via Alphabet Ads).