Originally posted by Don Morgan:
Can some of the arguments be grouped together into objects themselves, and then use a composition relationship?
Originally posted by Kishore Dandu:
In the same vein, it is not good data design to have about 50 columns in a database table. More than likely the data model is not normalized properly.
Originally posted by Steven Witkop:
OMG Certified UML Professional exams are as important as the Sun Certified Java exams.
Good luck on your exams...
-Steven Witkop
SCJP, SCJD, SCEA and OCUP
[ April 04, 2005: Message edited by: Steven Witkop ]
Originally posted by Stan James:
I thought C++ was an April fools joke.
Originally posted by Hu Chong:
I am currently working in a multi-million dollar project with the project team size of around 150+. There are many problems as with other IT projects
of a smaller size.
Care to share your experiences in projects of such size?
Originally posted by Vladas Razas:
From C++ I remember Meyers rule "Avoid gratuitious constructors". I forgot why?What terrible things may happen?
Vladas
Originally posted by Ilja Preuss:
Refactoring is something that is better done every couple of seconds, not at the end of the project.
Originally posted by Jeroen Wenting:
I doubt that's Java... It reads like C++
Originally posted by Jeanne Boyarsky:
Udayan,
While my goal is to have smaller methods, I find 15-20 lines to be a reasonable maximum. Having said that, it isn't worth it for me to add the final keyword. It would only yield a small performance improvement, if any, compared to database accesses and the like. Further, it would make it harder for me to use Eclipse's "extract method refactoring" because I would have to remember to add the final by hand.
"particularly where your method doesn't change parameters try making them final explicitly." - Methods should never change parameters. This is a poor practice that makes code brittle and harder to understand.