|
|
Re: Ola Bini: Is the World Class-Oriented?
|
Posted: Oct 19, 2008 12:50 PM
|
|
@Brain specialists say that humans organize their environment along two orthogonal axis: What things ARE and what things DO. Both are equally useful, neither comes first.
I've done some brain research. Two of my mentors in the field are world recognized, one has her last name as a keyword on Medline and the other is a member of NAS.
Certain parts of the brain seem to store different relevant facts. It's not a question of coming first in the brain, but what areas in the brain trigger certain kinds of processing first.
The brain isn't unilaterally one thing. We visually process things differently with the left eye than we do with the right eye. For instance, the right cerebral hemisphere just seems to be better at retaining abstract information about an object.
Relevance judgment also influences our predictions (one object appearing in a scene influences our "initial guesses" about what will come next). See: http://barlab.mgh.harvard.edu/papers/PBR_06.pdf
Also, neither ARE or DO may come first, but there is a systematic way the best architects define ARE and DO. That system determines WHEN the optimal time is for each (see below).
@Programming with classes lets us specify what the objects ARE. Programming with collaborations lets us specify what objects DO.
I'm of the Dr. W. Edwards Deming school of management:
When you no longer have any more statistically significant variation in what things DO (i.e., defects introduced by human error in translation), you can no longer expect better performance from workers. Better quality and worker performance strictly isn't attainable, because you can't increase quality and therefore can't get productivity benefits from fewer defects and rework.
Once you've reached the limits of what things DO, management needs to change the system not the workers. Once you can't detect meaningful variation, you have to change what things ARE to increase quality. Only by changing what things ARE can you change the system.
@As yet they are independent, but I hope to tie them together at some time.
What value will such unification bring? I've never quite liked the notion of a Controller, and try to strive for mere control partitioning instead.
|
|