Science versus Engineering

Varangy wonders what I think about this editorial by Chris Anderson, the editor of Wired. Anderson says “faced with massive data, this approach to science — hypothesize, model, test — is becoming obsolete.” Anderson confuses statistical models (which are summaries of the data) with scientific ones (which are descriptions of the mechanism that produced the data). As far as the content goes, I’m completely unconvinced. Anderson gives no examples of this approach to science being replaced by something else.

For me, the larger lesson of the editorial is how different science is from engineering. Wired is mainly about engineering. I’m pretty sure Anderson has some grasp of the subject. Yet this editorial, which reads like something a humanities professor would write, shows that his understanding doesn’t extend to science. It reminds me why I didn’t want to be a doctor. (Which is like being an engineer.) It seemed to me that a doctor’s world is too constrained: You deal with similar problems over and over. I wanted more uncertainty, a bigger canvas. That larger canvas came along when I tried to figure out why I was waking up too early. Rather than being like engineering (applying what we already know), this was true science: I had no idea what the answer was. There was a very wide range of possibilities. Science and engineering are two ends of a dimension of problem-solving. The more you have an idea what the answer will be, the more it is like engineering. The wider the range of possible answers, the more it is like science. Making a living requires a steady income: much more compatible with engineering than science. I like to think my self-experimentation has a kind of wild flavor which is the flavor of “raw” science, whereas the science most people are familiar with is “pasteurized” science — science tamed, made more certain, more ritualistic, so as to make it more compatible with making a living. Sequencing genes, for example, is pasteurized science. Taking an MRI of the brain while subjects do this or that task is pasteurized science. Pasteurized science is full of rituals and overstatements (e.g., “correlation does not equal causation”, “the plural of anecdote is not data”) that reduce unpleasant uncertainty, just as pasteurization does. Pasteurized science is more confusable with engineering.

There’s one way in which Anderson is right about the effects of more data. It has nothing to do with the difference between petrabytes and gigabytes (which is what Anderson emphasizes), but it is something that having a lot more data enables: Making pictures. When you can make a picture with your data, it becomes a lot easier to see interesting patterns in it.

Andrew Gelman’s take.

More. Derek James, a graduate student at the University of Louisiana at Lafayette, agrees with me.

4 thoughts on “Science versus Engineering

  1. Seth,

    You said:
    “That larger canvas came along when I tried to figure out why I was waking up too early.”

    I know this a bit off topic, but, in dealing with this question, did you discover any possible means by which a person who chronically sleeps late could be made to spontaneously wake earlier?

    Thanks,
    Araglin

  2. to spontaneously wake up earlier get a lot of sunlight early in the morning. Go outside soon after you get up. The shade is fine. Try 2 hours outside.

  3. I’ll definitely try that, although, the fact that I have to work (office job) Monday through Friday would require that I start out only getting the morning light on weekends…

    Oh: Could it be that staring at a computer monitor at night makes me want to go to sleep later and wake later?

    Thanks,
    Araglin

  4. Hmm…I’m thinking that there’s uncertainty in engineering or other applied sciences too. Not sure that the uncertainty disappears just because it’s an applied science. Just a thought. When I think of engineering I think of a skunk works.

Leave a Reply

Your email address will not be published. Required fields are marked *