Skip to main content

Roger's Theory of Food and Drugs

When a controversy arises about a new drug or a new food additive, we often hear the phrase, "There' s no evidence that it causes any problems." Well, maybe there is no direct evidence these new drugs or food additives cause problems, but there is common sense evidence of significant risk.

Throughout evolution, humans have been consuming certain kinds of substances. Through natural selection, humans have grown accustomed to these substances. This process has tended to weed out any of the substances with negative effects.

Even substances that humans have been consuming for only a few generations - not enough time for evolution to have had a significant effect - have stood the test of time. A few generations is enough time to begin to assess the long-term health effects of the substances.

In contrast to "old" substances, evolution has not acclimated humans to new drugs and food additives. Nor has it been possible, in most cases, to assess the long-term impact of these substances. It is certainly conceivable that any particular new drug and food additive is not harmful, but there is definitely a significant risk.

Comments

Roger L. Cauvin said…
I'd like to think that everything I wrote is so incontrovertible that we can call it law instead of theory. But I suspect others disagree.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio