• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Why OOP Can Be So Hard.

 
Desperado
Posts: 3226
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"This, then is the real reason why OOP is so hard. It necessitates that developers write perfect code the first time, freezes errors into the emerging framework, necessitates a programmer being reasonably familiar with hundreds or thousands of class objects, and assumes that each programmer will have perfect knowledge about the intent of all previous programmers who work on their project. When the degree of complexity in the project (or the degree of disorder) becomes too high, it is often easier to tear down the whole complex and start from scratch than it is to deal with the interdependencies that emerge because of poor design."
http://www.fawcette.com/discuss/forum.aspx?id=23&msg_id=566
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The real reason OOP is precieved as hard is because of naive and uninformed opinions like those.
I would suggest that the poster read Design Patterns or Refactoring or any number of books but I am too lazy to register yet another account with yet another website. I also doubt it would have much effect on the poster, he seems to be very closed to other points of view and very uninformed.
 
Ranch Hand
Posts: 672
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After reading a few OOP/design pattern books, I found it became much more effective and easier to code java. I would recommend a few books:
Java Design, Peter Coad
Object-Oriented Software Development , Jia, Xiaoping
Apply UML and Patterns, Larman
Java Design Patterns Work Book, Mutsker,
 
Sheriff
Posts: 17644
300
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Anything can be hard if you want it to be. All the "difficulties" mentioned are true of any kind of programming. What is difficult is "getting" it, "it" being whatever "theory" it is you are using to create the software, whether it is OOP, structured, assembly, etc. Without a good grasp of the theory behind the practice, execution will always be difficult. I agree with Chris, the poster is blaming the theory/practice rather than his lack of understanding of it.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic