[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!

[ top | next ]

Smalltalk-Specific Needs

(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.)
Satisfy intent, not letter of corporate "in the waynesses":
  • Archive your Smalltalk repository as a whole, rather than adhering tightly to an archive policy that mandates control of each "file".
  • A simple interface to stdin can allow your Smalltalk system to be constructed from within a central make file, if that is a dictate.
  • Synchronize your iterative process with the major milestones of corporate waterfall processes.
    • This will be difficult early, when the traditional process expects reams of requirements/design documents. Satisfy them (in the short term) with reams of automatically generated templates, while continuously improving your internal documentation.
    • This will be trivial later, when your documentation is realistic and synchronized with your code, and when your implementation is far ahead of normal waterfall expectations.
"...but reality dictates that we must evolve a means of interacting successfully with them." [panel 93.3] Isolate legacy systems, by:
  • Minimizing coupling -- make extensive use of lazy caching, so that your system can change independently of the legacy system.
  • Keeping legacy interface narrow and shallow: a minimum number of methods that are relatively independent of specific legacy state.
  • Providing a pluggable "legacy isolation" layer that encapsulates the legacy system and transforms it to the object system.
Maintain accountability of code that you assume is stable. Don't let "cowboy coders" into your base image!

[ prev | top | next ]