>>>The way I work, when I'm working on a particular object or class, that's my focus. I could care less about any objects it might invoke or that might invoke it.
>>
>>I guess it's just a blind spot for me. <<
>
>Actually, that explains it for me. I had considered it, but was afraid that I would be creating a label that would have been received negatively.
>
>I'm a "parallel programmer" (vs a "serial programmer" ?) ... I'm frequently working/modifying 10+ programs and class libraries at the same time. I'm constantly referring back to the bigger picture, and making global changes.
>
>It may be related to "design-on-fly" vs "pre-design" ... each has its relative merits and appropriate conditions.

I'm a proponent of Top-Down design (which may help further). I think it fits well with OOP principles.

The downside (if it can be called that) is that once the code has been written, I only worry about what it does or returns and what parameters are required. More often than I care to admit, I'm asked: "How does < blank > work?" or "What's the math behind the < blank > calculation?". My usual response is usually a dumb look followed by, "Duh, I dunno.":-)