View this PageEdit this Page (locked)Attachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 2-Nicholas Beckmann

The Portland Form is a standard way of posting problems, specifically problems in computer programming. Along with the problems presented are solutions. Because problems are often solved in similar ways these are called by the creators of the Portland Form to be patterns. The Portland form starts of with the observation of a pattern, then why the problem pattern exists, followed by how to solve the problem or part of the problem, and moving on to any more associated problems. Using the Portland allows for hypertext links which allow readers to follow links to find out more about keywords, sources, etc.

Smalltalk Best Practices is one pattern language. It documents many solutions to common problems including “analysis themes, design, and coding.” Many of these patterns will have been realized and solved by an experienced Smalltalk programmer. Inexperienced programmers and those looking for expansion on current solutions will find this pattern language useful. However, the power of this language is in its benefits to groups. It can be used as “shorthand vocabulary” or a “powerful documentation tool” to “convey in a few words both structure and intent of the system.” This pattern language is fitting for this class seeing how we use a derivation of Smalltalk. It seems to me like such library of resources should be useful to more languages yet this is the first I’ve heard of anything like this. It may be useful to me as a programmer if I run into problems enumerated by the Best Practices.

Links to this Page