OO

 

John is cofounder and managing director of Loop Factory, a Java focused education company.

He has spent the last decade teaching IT; from OO to Java, going through AS/400 systems, methodologies and Delphi; to professionals, unemployed and children.

John has recently cofounded JavaBlackBelt.com, a web site dedicated to technical quizzes about Java related technologies.

 Gathering OO programming and design guidelines has not been that difficult.
Good books and web sites list many, as for example J2EE Design and Development by Rod Johnson.

Any experienced OO developper/designer apply most of these guidelines instinctively, even without having learned them explicitly. If you are such a designer, many guidelines will look obvious to you.

Some guidelines are old and part of the common IT vocabulary now (such as Liskov and Open-Close principles).
Others are more controversial.

Learning OO


There is not much knowledge quantity to acquire when learning OO design. But this knowledge is hard to get, and often bound to a long experience.

I hope these guidelines will ease the learning process for those who have learned the OO basics and want to go further.

Like the design patterns, they formalize good and recurrent practices observed in projects.


Contribute


You cannot edit a guideline yourself, but you can put a comment on it. If you'd like us to change a guideline text or add a book/web reference, don't hesitate to comment on that guideline.
You may also just want to write what you personally think about that guideline.

Are you aware of additional OO guidelines? I'd love to list them here. Please contact me at John [at> JavaBlackBelt dot com.