Dear Monks,
Those who are experienced, are the one who can observe the things well. While developing the code, often we see the code how it looks and stuff. Sometime we see when we debug the error or want to improve our code.
Something constantly goes through our mind while programming, developing or designing. Those all are combination of many things including obsevations. In that regard, I ponder sometime, what can be achieved via observation. What model we should focus on ..How observation can be expanded. What is the limit of observation etc..

Seeking the guidence of experienced monks.

Thank You,
artist

Replies are listed 'Best First'.
Re: Observational Skills and Analysis
by cciulla (Friar) on May 03, 2003 at 14:36 UTC

    There IS a limit on observation. Perception, OTOH, is infinite.

    Learning new languages, methodologies, and techniques coupled with working with truly great code artisians expands ones perception -- which is distinct from observation. More like the difference between merely hearing and truly listening.

    Over the course of a career, novel problems occur less frequently until one can meet just about any challenge more or less intuitively. You spend more time refining your technique.

    Actually, I've found that I'm more effective at solving a problem when it is in the periphery -- when I'm not directly observing it. Call it the Schrödinger's cat method of development. :)

Re: Observational Skills and Analysis
by mojotoad (Monsignor) on May 03, 2003 at 07:06 UTC
    Those who are experienced, are the one who can observe the things well.

    I observe a comma splice, in my observation.

    ;P

    Matt

    Update: Dang. My attempt at implementing a comma splice is flawed. I leave the evidence here, as posted it is an example for grammarians.

Re: Observational Skills and Analysis
by Heidegger (Hermit) on May 05, 2003 at 05:15 UTC
    It's a very abstract thing we're discussing here. What happens when we program we could also call meditation ;-)