Comments on: Design Pattern Conversation: What’s the Best Way to Communicate Patterns? Part One. http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/ News and Artilces about Designing and Developing with Yahoo! Libraries. Sun, 27 Jul 2008 00:31:49 +0000 http://wordpress.org/?v=2.3.3 By: Peter Boersma http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-10145 Peter Boersma Mon, 16 Oct 2006 18:20:39 +0000 http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-10145 This may be premature (since it's only part one of the followup session) but I wondered what the participants of the disuccion think about the idea of adding Process attributes to Patterns? I explained the idea ("adding design process attributes to patterns expands the focus of patterns to include the context of designing") last August, on my blog: Adding design process attributes to patterns http://www.peterboersma.com/blog/2006/08/adding-design-process-attributes-to.html Any of the participant (or readers!) care to comment? This may be premature (since it’s only part one of the followup session) but I wondered what the participants of the disuccion think about the idea of adding Process attributes to Patterns?

I explained the idea (”adding design process attributes to patterns expands the focus of patterns to include the context of designing”) last August, on my blog:

Adding design process attributes to patterns
http://www.peterboersma.com/blog/2006/08/adding-design-process-attributes-to.html

Any of the participant (or readers!) care to comment?

]]> By: Jenifer http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-9924 Jenifer Fri, 13 Oct 2006 17:55:24 +0000 http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-9924 Thanks, Michael! Completeness is good up to a point -- if a pattern language is too large, or includes solutions that aren't so good, then it becomes less usable. But you're right in that comparisons like this make patterns more helpful. That's something I'll keep in mind for the future. Thanks, Michael! Completeness is good up to a point — if a pattern language is too large, or includes solutions that aren’t so good, then it becomes less usable. But you’re right in that comparisons like this make patterns more helpful. That’s something I’ll keep in mind for the future.

]]> By: Michael van Ouwerkerk http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-9804 Michael van Ouwerkerk Thu, 12 Oct 2006 06:06:26 +0000 http://yuiblog.com/blog/2006/10/11/communicating_patterns_part_one/#comment-9804 Jenifer, I'm currently reading your book and I love the approach you've taken with it. I find it to be very accessible and still inspiring. This way, I can more easily share it with my colleagues as well. I find that often the best insights about when to use a pattern and when not come from comparing patterns (e.g. responsive disclosure vs responsive enabling). For me, this highlights another important way of communicating patterns: make the collection as complete as possible, to allow for comparisons. Jenifer,

I’m currently reading your book and I love the approach you’ve taken with it. I find it to be very accessible and still inspiring. This way, I can more easily share it with my colleagues as well.

I find that often the best insights about when to use a pattern and when not come from comparing patterns (e.g. responsive disclosure vs responsive enabling). For me, this highlights another important way of communicating patterns: make the collection as complete as possible, to allow for comparisons.

]]>