Ken Tilton <firstname.lastname@example.org> wrote:
| Rob Warnock wrote:
| I might name that category K3 after the day I got stuck at some
| innocuous point on a rock climb called Kascading Krystal Kaleidoscope,
| because there were two perfectly even ways to proceed, each with a small
| problem, but each on the face of it seeming dead easy, so each could
| tempt me away from the other as being easier, yet once settled on seem
| dicey opening the door to the other. I finally made one of the moves and
| when my partner joined me on the ledge ten minutes later he demanded to
| know WTF I had been doing, it was easy. He said he had never seen me
| like that, and in fact /while/ I was stuck I noticed the phenomenon.
| This is close to "hunting", as in automatic transmissions on an upgrade
| and autofocus lenses faced with fuzzy scenes, but different I think...
Probably not "hunting" per se [which is closer to the phenomenon of
"Pilot-Induced Oscillations" (PIOs) which can cause "porpoising", e.g.,
especially when landing tail-wheel planes], but more like the classic
"approach-approach conflict", e.g., the dog starving between two bowls
| Next metaphor: coding encounters of the third kind? This is a first for
| me: the code is starting to write itself. Better put, the design is
| starting to architect itself, I am still writing the code of course. I
| am thinking of the actual encounter with the aliens, the point at which
| the computer takes over in the musical conversation after initial
| guidance from its programmers.
| I have a clear sense of not having written this code. I have a pretty
| good memory, and I am looking now at mechanisms and frameworks I never
| intended or conceived.
Isn't this called "being in the zone"? It's said to happen to
athletes all the time.
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607