But you would tell a salesperson he probably can't code and you when you're upset with your sales team thinking they can code, you might write an article entitled "Salespeople can't code. Sorry".
We all make generalizations when we are trying to make a point, because it is the best way to state a point clearly. A title like "Many webdevelopers seem to have a less-than-average capacity to sell" states something so mind numbingly obvious that you'd ignore the article. When someone says "webdevelopers can't sell", you should interpret that as "if you are a webdeveloper, you may be interested in this article, because you may be overlooking some important things that help you sell your app".
Interestingly, your type of response illustrates the article: you criticize details, while ignoring the big picture. That's the same as mentioning your features, but not the problem you solve.
We all make generalizations when we are trying to make a point, because it is the best way to state a point clearly. A title like "Many webdevelopers seem to have a less-than-average capacity to sell" states something so mind numbingly obvious that you'd ignore the article. When someone says "webdevelopers can't sell", you should interpret that as "if you are a webdeveloper, you may be interested in this article, because you may be overlooking some important things that help you sell your app".
Interestingly, your type of response illustrates the article: you criticize details, while ignoring the big picture. That's the same as mentioning your features, but not the problem you solve.