[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Pattern: WYSIWYG

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)

- "Fine grained" -- at the level of individual methods and objects.

- "Real time" -- each method is stored upon accept, and is immediately available to other developers.

- Code units have semantics, and have relationships to other code units, typically "is contained by" and "requires" kinds of relationships. This property allows a code unit to be meaningfully referred to as a "module".

- An individual code unit's developer,

not
a system integrator, decides when that code unit is ready to become part of its containing configuration. This pushes responsibility down to an appropriate level -- those with the most knowledge about a thing should make decisions about that thing. It also reduces an organization's vulnerability to single point of failure dependence on an integration guru.

- Modules and users interact in pre-defined roles: manager, owner, developer, browser.

[ prev | top | next ]