Nicola:
> Hmmm, responsibility is of everybody to the same degree. If we keep
> things too separated, knowledge gets shared less... and the project
> starts depending too much on a single person. Yes, there are concern
> areas, and parts of code that some prefer, but as you have seen
> yourself, a natural layering has already occurred ;-)
I've already come to this conclusion as well, since my earlier posts.
> (discussions get forgotten, just code remains)
Not when someone (like moi) takes the key discussions and puts them in a
formal document deliverable (like the Architecture document) and soon to be,
some Usage Guidelines documents (re: when to use Sync vs Async events,
impications of using Properties vs. Instance variables).
There is massive value in some of these discussions, and they need preserving
and dissemination, and not just in an email archive! <grins>
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|