|
|
|
| |
 |
Write test code early
Write the test code first (before you write the class) in order to verify that your class design is complete. If you can't write test code, you don't know what your class looks like. In addition, the act of writing the test code will often flush out additional features or constraints that you need in the class-these features or constraints don't always appear during analysis and design. Tests also provide example code showing how your class can be used.
|
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!
|
|
 |
|
Elegance always pays off 
Use bare bones methodology 
First make it work, then make it fast 
Automate everything 
Remember the "divide and conquer" principle 
Write test code early 
Separate the class creator from the class user (client programmer) 
Get abstract 
Name classes intelligently 
An indirection should have a meaning 
Eckel's Ten Java Maxims for Good Design Implementation
