Patterns As Tangible Things

Maybe the Wiki community can help me out; I've run into somewhat of an interesting dilemma (at least, to me).

I've been involved in a bit of 'scoping' lately, of tools and processes. Being more development focused, sometimes the world of the "Big A" Technical Architect can baffle me to no end. One of the interesing topics lately, as I've been playing with RationalRose and TogetherControlCenter, is the notion of PatternsAsTangibleThings.

What do I mean by this?

In my own thinking, a pattern is a strategy for solving a common problem. (For example, implementing a Factory pattern to allow access to multiple databases.) A pattern (and the varied pattern resources) are not an 'end' to a means, but rather an idea to be developed toward a particular solution, defined at development time after deciding on general strategies for laying out the application.

While sitting in on some of these conversations, the discussion of "applying patterns" floats around, everyone around the table nods intelligently, and I have to ask the question; "What is the actual problem we are trying to solve?"

I usually get dirty looks at this point.

What I'm curious about:

I've discovered that I can be a bit pragmatic and skeptical about such things. The curse of being trained as a scientist first, I guess....

-- ChadThompson


EditText of this page (last edited September 8, 2002) or FindPage with title or text search