Object Oriented Design and Programming

A lot of people would agree that design reviews can bring a lot of value to building quality software. However, when it comes to actually doing a design review we enter a somewhat blurry environment where everybody has another view on what a design is, how in-depth it should be etc, how it should be organised, etc.
Based on my own experience, I want to share some tips and best practices with you...

When I've contributed to projects with fewer global variables, I've noticed that the flexibility and maintainability of the code has been significantly greater, and I have more fun working with it. My theory: if there are no globals, we can predict that an object doesn't play with any toys that we haven't given it.

What the OO solution to this problem gives you, though, is some nice name-spacing, the potential for type safety in your map method and a potentially much more readable batch of code. What's the major issue with this?

Comments and discussion related to the developer.* article "Object Oriented CASE Tools: Lost Opportunities and Future Directions," by Mario Van Damme. In this article the author explores the past and future of Computer Aided Software Engineering (CASE) tools and finds that the future lies in the past.