In Defense of Food: An Eater's Manifesto by Michael Pollan

Seven words: "Eat food. Not too much. Mostly plants."

That's Michael Pollan's entire thesis. The rest of In Defense of Food exists to explain why something so self-evident needed a book to articulate it, and how we arrived at a world where it does.

The Nutritionism Trap

Pollan's central argument is that we stopped eating food and started eating nutrients. Nutrition science, aided by a willing food industry, reduced eating to a checklist of vitamins, minerals, fats, and macronutrients. The result is that we now consume elaborate engineered products designed to hit nutritional checkboxes, while being measurably less healthy than populations that just eat actual food without thinking about it.

He calls this ideology "nutritionism." The term is precise. Nutritionism is not nutrition science. It is the belief that food's value reduces entirely to its measurable components, and that we can extract, synthesize, and optimize those components independently of the whole. Once you accept nutritionism, "fortified" processed food can be marketed as healthier than an apple because it has more measurable vitamin C per serving.

The critique lands because it explains a pattern I recognized in myself. How many times have I picked up something labelled "high protein" or "low fat" or "heart healthy" without asking a simpler question: is this actually food? The labelling is a signal that the product requires defending. Real food does not need a nutrition label to justify its existence.

A Systems Problem, Not a Willpower Problem

Pollan traces the historical arc of this shift and it is not flattering. Government dietary guidelines shaped by lobbying, food science driven by research that kept contradicting itself, subsidies that made processed ingredients cheap and whole foods relatively expensive. The Western diet did not emerge from individual failure. It emerged from incentive structures that rewarded the wrong outcomes.

This maps to something I think about in software organizations constantly. When a team produces low-quality code consistently, the instinct is to blame the individuals. But low-quality code is almost always a systems problem. Incentives reward shipping velocity. Deadlines punish the time needed to do things properly. Testing gets cut when pressure builds. The quality problem is not the team; it is the environment the team operates in. Pollan's framing of the food system applies: "It's a systems problem, not an individual willpower problem."

Understanding this distinction matters for how you fix things. You cannot fix a systems problem by trying harder. You have to change the environment.

The Practical Rules That Actually Work

Pollan is strongest when he stops being a critic and starts being a practitioner. His practical advice is memorable precisely because it ignores nutritionism entirely:

Eat food your great-grandmother would recognize. Shop the perimeter of the grocery store, where the actual food lives. Do not eat anything that contains more than five ingredients. Do not eat anything that would not rot. If it has ingredients you cannot pronounce, put it back.

These rules are heuristics, not algorithms. They will misfire occasionally. But they are robust in the statistical sense: applied across a lifetime of food choices, they steer you toward real food and away from engineered products. I have adopted several of them and the friction they introduce is the point. Pausing to ask "would my grandmother recognize this?" forces a moment of actual thought into what is otherwise an automatic behaviour.

The engineering parallel is code review heuristics. Rules like "if a function is longer than 50 lines, question it" or "if you need to write a comment to explain what the code does, consider renaming the variable" are not universal laws. But they are useful friction. They force a moment of deliberate consideration before an automatic decision gets made.

Where the Argument Overstretches

Pollan has two significant weak points.

The first is access. Eating whole, unprocessed food costs more money and more time. A family working two jobs in a food desert does not have the luxury of a farmers' market on a Saturday morning or an hour to cook from scratch on a Tuesday night. Pollan acknowledges this in passing, but he does not grapple with it seriously. The book reads as if written for people who have already solved the basic constraints and just need guidance on what to do with their options.

The second is his treatment of nutrition science. Pollan uses its contradictions, the constant cycling of dietary recommendations, as evidence that the whole enterprise is suspect. But that framing misunderstands how science works. Science contradicts itself because it revises its models when new evidence arrives. That is not a flaw. That is the mechanism. Dismissing nutritional research wholesale because it has been wrong before applies a standard that would invalidate most fields. The real critique should be at the institutional incentives that shape which research gets funded and how it gets communicated, not at empirical inquiry itself.

What Stays With You

After reading this book, I started shopping differently. Not dramatically. I did not overhaul everything. But I started noticing the gap between things that look like food and things that are food. I started reading ingredient lists with a different question in mind.

The book works not because it resolves the tension between nutritionism and whole-food eating, but because it names the trap clearly enough that you can see yourself inside it. Once you see it, you cannot entirely unsee it.

The seven-word rule is almost annoyingly simple. But the simplicity is the point. Our relationship with food became complicated because powerful institutions made it complicated. The antidote, Pollan argues, is to reclaim the simplicity. Not because simple is easy, but because the complexity was never in your interest to begin with.

I send occasional notes on system design and the senior-to-staff transition, no fixed schedule; you can sign up here. I break down architecture and engineering decisions on Gazar Breakpoint on YouTube.

I also do 1:1 mentorship for engineers targeting staff and principal.