• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Individual-Group Needs Mismatch

- There is no distinction between system code, your own code, and the code of other developers -- "If it's in my image, I must have written it, unless I don't recognize it, and it seems to be dealing with the Furblesnotzer subsystem, then maybe it is Joe's code, except that Sue was working on Furblesnotzer last week, and then maybe..."

- A "module" of code is ad-hoc, undefined, carries no semantics. Generally, a class category or change set (ST 80) or a class (ST/V), but rarely a cohesive whole.

- No cross developer browsing -- except by convention, or by snooping around in other developers' home directories!

- Isolated change management -- you cannot effectively have multiple people working on one "module" (whatever that is).

- No documentation support -- "structured commentary" is not state of the art among CASE tools.

- Integration synchronization -- generally, project milestones require that everybody freeze development in order to proceed with integration.

[ prev | top | next ]