I have worked on systems that had turned into the classic 'big ball of OOP spaghetti'. Likewise I've also had to deal with a 'big ball of structured programmin

I have worked on systems that had turned into the classic 'big ball of OOP spaghetti'. Likewise I've also had to deal with a 'big ball of structured programming spaghetti'. My take on the difference in these two types of systems is they are generally the result of too much coding with too little design. Personally, I think the OOP approach does have a tendency to turn into that spaghetti ball more easily, only because it needs more up front design. Most of places I've worked who adopted an OO approach have tended to focus predominantly on the OOP with little or no attention to the OOD and that tends to be a recipe for disaster.