Just knowing an object-oriented language isn’t enough to create object systems. You also have to learn to “think in objects.” This chapter explains why it’s important to understand what it means to truly be “object-oriented” and how you can build your business by using object-orientation from top to bottom.
Object-Oriented Analysis and Design
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
I just wish we could get away from class-based object-oriented programming. In something like Dylan you have open classes where methods don’t belong to classes. In Dylan, and other languages I suppose, you can add a method to any class without having the source code.
I’ve given up being excited about anything coming from the Java/C# world.