'lo all,
> Performance is a tricky issue that you need to test it based on some
> reasonable assumptions.
> I strongly propose that you read the book "Refactoring" by Martin Fowler
as
> a guide for OO design, it is a very good book which can be used as a
> checklist for design and code review.
Just to back this up, from my own experience:
-> "Make it run, make it right, make it fast." Don't tweak your code just
for performance. Code clarity is so much more important. Plan time at the
end of a project to meet performance requirements. (And if you think this
is really a risk for your project: do some quick calculations, and perhaps
prototype a little, to ease your mind.)
-> Do read and apply "Refactoring". I suggest you start with the "Bad
Smells in Code" chapter.
-> More on process in the chapter on "An Outline Development Process" in
Fowler's "UML Distilled". It has many good ideas.
> Regards.
>
> Tan Teck Seng
Groetjes,
<><
Marnix
--
Marnix Klooster
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
