• 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

Cycle of Development

Cycle of development

• Initial start or conversion to ENVY:
  • Decide on overall structure and create top level components, then sub-components.
  • Resolve name clashes; version all components.
• After initial phase, loop as follows:
  • Make components editable.
  • Write code and integrate it with other team members. Test and bug-fix the public interface between collaborating classes. If desired, do informal code reviews.
  • Do full integration.
  • Test, fix bugs, reintegrate; repeat this step until satisfied.
  • Brand components with a version name, making them read only.

• Depends upon team size and application size
• No shorter than two weeks recommended, except in code freeze, pre-release bug-fixing
• Typical cycle length that worked well for teams of 6 to 12 developers was 4 weeks.

[ prev | top | next ]