|
|
|
| |
 |
Don't overuse finalization
It can be tempting to use "final" methods to help speed the application performance, but you'll typically only want to use "final" to prevent overriding, which is its primary intent, and avoid using "final" methods for efficiency purposes. Use "final" only when the program is running, but not fast enough, and your profiler has shown you that a method invocation is the bottleneck.
|
Java Zone - Get Help - Search
Tips
|
|
 |
Save on Hot Java Specials
|
SOFTWARE:
dtSearch Web
Add power searching to your web site.
Buy Now!
|
BOOKS:
PointBase Mobile Edition
Enable local data access for mobile users.
Buy Now!
|
|
 |
|
Follow the Sun coding conventions
Use "get," "set," and "is" 
Standardize! 
Make iterative testing of classes easy 
Follow standard capitalization rules
Avoid inheritance 
Don't create your own "decorated" private data member names 
Don't overuse finalization 
Follow a canonical form 
Use nested classes 
Eckel's Ten Java Maxims for Good Design
