Theory and Practice III
Sander and Jos both asked me whether Jonas perhaps really asked the question of “why” the coat-hanger had a Nils Holgersson figure on it. Yesterday my promotor asked me the same question with respect to my own research. He said: The whole of Western Science has been occupied for centuries with the “how” questions. Scientists believe that when you answer the how question you know what ever it is you wanted to know about ‘it’. “How” does an electron interact with a nucleus? How does a baby grow in the womb? How does evolution ‘work’? How do mountains come into existence? How does gravity work? How do children and parents evolve relationships? How does an economic crisis work, and how can we fix it?
But the more interesting questions are the “why” questions, he said. Why do we have vision? What is vision for? Not: How does the eye work, or how does the visual system work, but why does it work? James Gibson asked this question and his theory of Direct Perception is very different from ‘mechanistic’ theories precisely in that respect. He said seeing is for doing: you see what you can do. You see a chair as a “to-sit-on”, which is called it’s affordance. And the objects we perceive basically *are* affordances even before they become ‘objectified’: they are first “opportunities for action”. Cognitive psychologists that were asking ‘how’ questions then asked Gibson: but *how* does that work? How can the brain ‘detect’ affordances, how does it ‘know’ what it sees? And thus “knowledge” became interpreted as something that was needed in order to answer the how question: knowledge, and perception, and the physical characteristics of the eye were always seen, by these cognitive psychologists, as building blocks needed in order create the ‘machine’ that would be the answer to the question of “how it works”.
It is a new insight for me that designers (my promotor is from Industrial Design) should care first and foremost to ask the *why* question. Because as I saw it designers are always busy answering *how* questions: how to create this or that. But I think I may have been wrong. Because in order to design, you need to know mostly *why* you are designing. Asking why is asking: what is it for? And this is what designers ask.
The why question is the functional question, the how question is the mechanical question. I have sometimes confused myself in mixing these up. This is because cognitive science as I saw it also mixes these up in a way. The model that most cognitive models are dependent on is the ‘functionalist’ model. This model is an *answer* to a “how” question, but the mechanism it describes is based on *functions*. And functions are basically descriptions of *why* questions. I guess. Let me try to explicate.
Suppose I want to know “how does vision work”? How do we recognize objects? And suppose I observe a pattern of activation in one of the first cortical areas in my brain. But now I do not ask how this brain area works, I ask instead: what is this pattern *for*? *Why* is it there? Well I could say, this pattern in visual cortex is there in order to detect features. It is a feature-detector. Here I have defined a *function*. The function is basically the “why” question turned into a mechanism. “It is there in order to produce X” becomes “this thing works as an X producer” And so now I can also answer part of the how question: how do we recognize objects? Well, we have various mechanisms, amongst which “the feature detector” mechanism.
This is what cognitive science does.
I guess it is not what I should be doing. Still thinking about what I’m actually saying here, how to say it better (and why…)
Popularity: 7% [?]
26 Aug 2009 admin 0 comments


We now live in a strange society where people will pay more to receive less. If you are not already making money on the basis of this principle, this is your time to get your business together and become increadibly rich.