%0 Conference Paper %1 coplien1997pattern %A Coplien, James O. %B Proceedings of the 2nd European Conference on Pattern Languages of Programming (EuroPLoP '97). Siemens Technical Report 120/SW1/FB %C Munich, Germany %D 1997 %I Siemens %K design designpatterns methodology patterns workshop writers %P 51-60 %T A pattern language for writers' workshops %U http://dirkriehle.com/community-service/hillside-group/europlop-1997/p2final.pdf %X Peer review is a crucial element of the quality improvement process for any document and more broadly for any intellectual work. Most intellectual disciplines rely on a peer review culture for the advancement of knowledge, and those disciplines often focus more on content than on expression. Design reviews and code walk-throughs focus on what might be broken, not on what works. Most refereed journals scrutinize works first against standards of formalism and second, if at all, for readability. The pattern community is less interested in the advancement of knowledge than in the broad dissemination of sound practice, and is equally concerned with content and expression. Writers’ workshops, which come from the creative literature community, provide an alternative to prevailing peer review practice that is well-suited to the needs of the pattern community. Writers’ workshops follow a collection of normative behaviors designed to give authors constructive feedback on their work while protecting their dignity. The following patterns document those normative behaviors and the structures that support them. This is a “cheap” pattern language. The patterns not only should be applied in order, but reflect a chronological (rather than structural) progression. There is no single ideal medium to describe what goes on in a Writers’ Workshop. I use patterns here not because they describe structure, but because they provide an ideal form to elaborate the forces that drive these ceremonies. None of these patterns stand alone; they combine to make a whole larger than the sum of the parts. The patterns interact in intricate ways; I attempt to describe the interactions in the course of the presentation. This language describes our many Writers’ Workshop experiences at Bell Labs. The rationales and forces recall the initial tutoring that the Hillsiders received from Richard Gabriel back in the spring of 1994, at a retreat near Ben Lomond. That’s the closest link we have to the creative literature community, which has a lot more experience with this format than we do in the pattern community. I offer this language as capturing practice that has worked well for us, in hopes that others find it useful.

@inproceedings{coplien1997pattern, abstract = {Peer review is a crucial element of the quality improvement process for any document and more broadly for any intellectual work. Most intellectual disciplines rely on a peer review culture for the advancement of knowledge, and those disciplines often focus more on content than on expression. Design reviews and code walk-throughs focus on what might be broken, not on what works. Most refereed journals scrutinize works first against standards of formalism and second, if at all, for readability. The pattern community is less interested in the advancement of knowledge than in the broad dissemination of sound practice, and is equally concerned with content and expression. Writers’ workshops, which come from the creative literature community, provide an alternative to prevailing peer review practice that is well-suited to the needs of the pattern community. Writers’ workshops follow a collection of normative behaviors designed to give authors constructive feedback on their work while protecting their dignity. The following patterns document those normative behaviors and the structures that support them. This is a “cheap” pattern language. The patterns not only should be applied in order, but reflect a chronological (rather than structural) progression. There is no single ideal medium to describe what goes on in a Writers’ Workshop. I use patterns here not because they describe structure, but because they provide an ideal form to elaborate the forces that drive these ceremonies. None of these patterns stand alone; they combine to make a whole larger than the sum of the parts. The patterns interact in intricate ways; I attempt to describe the interactions in the course of the presentation. This language describes our many Writers’ Workshop experiences at Bell Labs. The rationales and forces recall the initial tutoring that the Hillsiders received from Richard Gabriel back in the spring of 1994, at a retreat near Ben Lomond. That’s the closest link we have to the creative literature community, which has a lot more experience with this format than we do in the pattern community. I offer this language as capturing practice that has worked well for us, in hopes that others find it useful.}, added-at = {2011-04-02T09:06:44.000+0200}, address = {Munich, Germany}, author = {Coplien, James O.}, biburl = {https://www.bibsonomy.org/bibtex/21f732a939f9f01f113ab6983e29b50e3/yish}, booktitle = {Proceedings of the 2nd European Conference on Pattern Languages of Programming (EuroPLoP '97). Siemens Technical Report 120/SW1/FB}, interhash = {50c1054425f53ceff1f5d25b39373a7f}, intrahash = {1f732a939f9f01f113ab6983e29b50e3}, issn = {1040-6042}, keywords = {design designpatterns methodology patterns workshop writers}, pages = {51-60}, publisher = {Siemens}, timestamp = {2011-04-02T09:06:44.000+0200}, title = {A pattern language for writers' workshops}, url = {http://dirkriehle.com/community-service/hillside-group/europlop-1997/p2final.pdf}, year = 1997 }