ultrabike
500+ Head-Fier
- Joined
- Apr 3, 2012
- Posts
- 913
- Likes
- 108
Quote:
I believe in approaching a problem with both self-confidence and humility. One needs to understand what one can leverage and the real limitations of what's available. As far as what we do and/or don't know, I cannot stress enough how important simulation and prototyping is in the development of a product for precisely what we don't know. And how many new ideas flourish in the process. Moreover, what works in one situation does not work in another one (even if the problems are somewhat similar) - and there are always trade-offs (no-such-thing-as-a-free-lunch).
As far as measurements is concerned, more often than not they are filtered by marketing and provided as a sales pitch. In many cases, one has to have NDAs in place if real data is to be shared.
EDIT: Let me give you another perspective. When two or more companies develop a product for the same market, they want their product to outperform their competition. They don't share IP or give away secret sauces. In some cases, what does happen is the development of standards so that products can inter-operate. And even these standards have a lot of politics involved. Companies will try to push their agendas by attempting to cripple each other. They often try to push clauses that disable the application of certain technologies their competitor is knowledgeable and relies on. Inter-operability exercises are really interesting. One company's team locks itself out of the other and hide as much as possible. Written agreements and negotiations take place. Believe me, every effort is done at obscuring your product to the competitors. White papers? They are more often than not "mumble-jumbo."
engineers feel free to correct me, but don't you kind of need to know what you're doing? And if I had a company which made amps with good measurements on a quality never before measured, I would try to show it to the world!
I believe in approaching a problem with both self-confidence and humility. One needs to understand what one can leverage and the real limitations of what's available. As far as what we do and/or don't know, I cannot stress enough how important simulation and prototyping is in the development of a product for precisely what we don't know. And how many new ideas flourish in the process. Moreover, what works in one situation does not work in another one (even if the problems are somewhat similar) - and there are always trade-offs (no-such-thing-as-a-free-lunch).
As far as measurements is concerned, more often than not they are filtered by marketing and provided as a sales pitch. In many cases, one has to have NDAs in place if real data is to be shared.
EDIT: Let me give you another perspective. When two or more companies develop a product for the same market, they want their product to outperform their competition. They don't share IP or give away secret sauces. In some cases, what does happen is the development of standards so that products can inter-operate. And even these standards have a lot of politics involved. Companies will try to push their agendas by attempting to cripple each other. They often try to push clauses that disable the application of certain technologies their competitor is knowledgeable and relies on. Inter-operability exercises are really interesting. One company's team locks itself out of the other and hide as much as possible. Written agreements and negotiations take place. Believe me, every effort is done at obscuring your product to the competitors. White papers? They are more often than not "mumble-jumbo."