Get abstract

All software design problems can be simplified by introducing an extra level of conceptual indirection. This fundamental rule of software engineering is the basis of abstraction, the primary feature of object-oriented programming. Get in the habit of using indirection to solve design problems; this skill will serve you well for many, many years to come.



Previous: #8 - Write test code early
 
Next: #10 - An indirection should have a meaning


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


Java Zone - Get Help - Search Tips

 

Eckel's Ten Java Maxims for Good Design Implementation
DevX's Review of Eckel's "Thinking in Java"
"Thinking in Java, Second Edition" DevX product listing
Eckel's Home Page
Java Code Library
Java Pro Magazine
Java Discussion Group

 TALK BACK
Cutting a corner or two in order to meet a deadline is always a temptation. Can you tell us of an experience of yours that did (or didn't) work out the way you expected? Join the discussion and tell our growing Java community about it.
Click here to Join


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!
Advertising Info  |   Member Services  |   Contact Us  |   Help  |   Feedback  |   Site Map
Jupiterweb networks

internet.comearthweb.comDevx.comClickZ

Search Jupiterweb:

Jupitermedia Corporation has four divisions:
JupiterWeb, JupiterResearch, JupiterEvents, and JupiterImages

Copyright 2004 Jupitermedia Corporation All Rights Reserved.
Legal Notices, Licensing, Reprints, & Permissions, Privacy Policy.

Jupitermedia Corporate Info | Newsletters | Tech Jobs | E-mail Offers