Hal,
That brings up a pretty big point to me. I am a big believer in
architecting my applications. I do it on all my medium to large projects.
However, I would certainly like to get more information on how other people
architect their applications. I feel that the way that I have been doing it
is lacking. I have been considering coming up with some higher level
Fusedoc sort of thing - something that would map out an entire circuit or
an entire application.
Right now, I have been doing sort of an OO/UML approach. I
generally start with a list of what all will need to be done and I put
related tasks together in a circuit. I am interesting in hearing other
approaches/suggestions how best to architect an application.
At 10:10 AM 5/24/2002 -0400, you wrote:
>Keith,
>
>Just throwing in my 2 cents here. The problem you're describing is a
>common one. The reason for it is that the architecture hasn't been
>sufficiently thought through before you begin to either Fusedoc or code.
>Fusedocs document what you have planned, but if the planning isn't
>sufficient, you'll find this out when you start writing your code. In
>that case, a decision NOT to write Fusedocs is entirely rational.
>
>Architecting an application - especially a large or complex one - is
>hard work and sometimes frustrating work. There is *nothing* fun about
>throwing away 6 hours of work because my architecting shows me that an
>earlier decision will run into a dead end. Still, it's a lot better than
>finding this out when coding.
>
>My experience has been that many of us developers don't spend much time
>in architecting an application and that decision leads to a lot of
>problems further down the line. I've had this experience in another
>area: when I first start doing technical writing, I did magazine
>articles. I found that I didn't need any real planning on these; I just
>wrote them. When I wrote the first book, though, I ran into HUGE
>problems due to my lack of planning. I would get to page 238 and wonder,
>"Did I already say this?". I rewrote the book 4 complete times. What a
>mess!
>
>Finally, someone said to me, "You need to architect a book, just like
>you architect an application." The thing is architecting a book didn't
>feel natural to me. In fact, I really did not like it. I felt I would be
>constricted in the actual writing by decisions I made in planning. It
>really was uncomfortable, but I stuck with it because I didn't like the
>results of NOT architecting the book. Gradually, it got easier and my
>fears diminished. I found that, quite apart from my worries, having a
>detailed outline gave me a system into which I could put my thoughts.
>Now, I'm actually starting to like architecting books and I *love*
>architecting applications.
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
