Added by Geoff Sauer on Jan 31, 2003.
Average rating: 4.00/5.00 (n=1)
 


In a series of books, Christopher Alexander, an urban planner and architect, has inspired object-oriented programmers with his idea of a pattern language-originally, a catalog of solutions to common problems faced by any community or individual creating a livable structure such as a town or a house. His approach might also help technical communicators polish and perfect our own standard rhetorical structures (such as the procedure, user guide, or reference), viewed as common ways of answering frequent, if virtual, questions from our users . Alexander's way of describing age-old patterns such as neighborhoods, streets, paths, and homes may give us a model for creating our own set of patterns in technical communication, whether or not we adopt some of the eager elaborations offered by folks in the object-oriented design world. What's a pattern? For Alexander, a pattern is a practical guide to resolving any problem that occurs over and over, such as how to lay out common ground for a town square, or punch a hole in a wall for a door.
 
  View all 20 works by Price, Jonathan R.  
  View all 17 works published by Communication Circle, The  

Please share your rating/opinion of "What Technical Writers Can Learn from Christopher Alexander's Pattern Language".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués