Asynchronous Multithreaded Unconsciousness



Extreme programming is funny in that exceptional programming is best done alone, not as a communal activity. But most programmers have neither the memory, nor the perceptual ability to take 20 things into account at one time. Nor the patience to wait on their unconscious abilities to deliver a message So average programmers rely on structure to function in a world too complex for them to perceive all the pieces.

For decades I took projects on alone, because most projects needed to be done yesterday and the quickest route to yesterday is through one programmer; not replying on others is a big performance enhancement as long as the project is not too big. During this phase of my life I found new ways to solve problems by discovering all the precepts to the problem. When I could not find a solution, I would walk away from the problem; going off and do something else, preferably mundane. Many solutions use to pop into my mind when mowing a lawn. A friend of mind says her solutions always come out the shower head.
The point being we seem to have an asynchronous multi-threaded server within our heads and all we have to do to hear its insights, is to still our mind and make sure we are listening when it speaks to us through our feelings. Most people too distracted by the things of man, to hear when it calls.
But there is more to this server because it works on different problems at the same time, with results overlapping. It is a long drawn out search sometimes, cross referencing everything that is in our head.

The database is nothing like our computers. Engineer should try and develop a database system similar to how the brains stores information; chemical imprints  that have no linkages; a search is a chemical release across the folds of our brains coaxing synchronous chemical imprints to arise in response.

No comments: