Talk:Getting Started

From Patterns

Patterns vs. Pattern Language Approach

--Norbert (Dec. 27/2006) I am torn between the best way of approaching Patterns vs. Pattern Language. I think the Conservation Economy started with a fairly straightforward 'grammar' that tied together the various patterns into the 'map'. Christopher Alexander used a strong spatial metaphor. I am not clear what the right grammar is for systems in general - scale comes into it (both size and rate), as well as the categories that you proposed. Julian Vincent's "Things (substance and/or structure) do things (energy and information transformation) somewhere (time and space)" is kind of catchy. My gut tells me there are other relationships that will likely emerge as we try to organize the patterns. My initial thought was to focus on documenting individual patterns in as much detail as we can, capturing information such as your categories and scale, and deferring the Pattern Language work when we have enough patterns. I found it very difficult to complete the pattern template for Diversity and Open Loops - providing specific guidance on how to instantiate the patterns within a design is hard at this level of abstraction. I believe the effort will ultimately pay off - one of the concerns I had with the TRIZ Inventive Principles is that there was little guidance in how to use them in a practical sense, other than by reading case studies and examples.

--Tom McKeag (Dec. 27/2006) Ok, I understand your reasoning here, I think. Researching and documenting phenomena first (patterns) allows for a more open exploration and steeper dive into the individual subject. On the other hand, organizing the rules for grouping first (pattern language) could aid in focusing and analyzing that search.

Asynchronous Collaboration

--Norbert (Dec. 27/2006) I was reading a Wiki on 'Barn Raising' that pointed out the challenges of trying to accomplish group activity asynchronously. Do you think it would make sense to get a consensus on a limited set of patterns that people are particularly interested in working on, give everyone some time to absorb and research the patterns, then set aside a block of time to collectively work on those patterns? At the simplest level, we could agree to spend 'n' days with the intent of each completing a number of 'turns' If we can find time when enough people are available, we could use the conference bridge. I have also seen 'group chat' sessions that are left open for an extended period, sort of a 'drop in' place where you can communicate with people in real-time. What do you think?

--Tom McKeag (Dec. 27/2006) I am open to different ways, most of them will be new to me. I generally work alone now, but in the past have used the Delphi approach of working individually on a common problem in order to bring back to a group discussion. I have also participated in team charettes, public workshops, etc.

I prefer deadlines and stated goals and agendas for meetings. I don’t believe you can have development without commitment, so also believe in assigned tasks that are coordinated, rather than assembling a product from volunteer offerings.