DCI -A better OO paradigm?

DCI(Data Context and Interaction) has come up as a paradigm to guide you back to the essence of oo(Object Oriented) programming. Then the natural question is what is wrong in the way we perceive OO now?.Well there are a lot .The main problem is OO is designed to capture the end-users mental model in a computer.Are we really successful in using OO in that way. Definitely not.what we are trying to do is to build software on the four basic pillars(Abstraction,Encapsulation,Inheritance and polymorphism) that we believe as the base of OO design. In addition to that we have identified so may concepts like coupling,cohesion ,design patterns,AO(Aspect oriented)programming,DDD(Domain driven Design) etc. What are we really trying to solve here and why we have these many paradigms?. Please watch this video and you may not get all the points the speaker is trying to explain. Thinking in a different way is always difficult especially in the programming world where we are getting trained to follow the so called best practices and design principles. It is better refresh the mind sometimes ! .I am planning to have a separate post on DCI later, once I get a clear idea on practicing DCI.

Video
http://www.infoq.com/presentations/The-DCI-Architecture
Other References
http://www.artima.com/articles/dci_vision.html
http://blog.jaoo.dk/2009/03/04/handling-architecture-in-the-agile-world/
http://vimeo.com/8235574