> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Berin: > > Have just read though your document and I have to say that > you vision of > A5 is very much in line with my own thoughts concerning a containment > API.
Thanks. I did pull some inspiration from you, Peter D., and Noel, and I combined them with my own thoughts. > I have some concerns about the necesity for the > LifecycleArtifacts > interface but that's probably more of an implemetation > concern based on > how you go about achieving the result your describing - but that's > something we can discuss at some other time. Those are just implementation details. We can discuss it later. The important thing is that I wanted to put together a high level document for general design/concepts before we got too deep into detailed discussions. It is part of the reason I kept wanting to push the A5 context discussions till later--it's too fine a detail to start with. I find that starting with "bottom up" design (i.e. detail first) lends to disproportionate APIs. You can tell where all the attention was spent, and by the time the team came to other details they get so emotionally drained from the first details that you get a "close-enough" attitude. When you start from the "top down", you provide a mental framework for your designs. That mental framework serves to focus the details so that many conversations that might otherwise occur about the details get filtered out--whether it is a conscious decision or not. You also are left with a consistent architecture and a design where the same emotional clarity is applied to all details at the same level. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
