logo

New Response

« Return to the blog entry

You are replying to:

    • avatar
    • Ferdy
    • Posted on Wed 5 Oct 2011 01:10 PM

    Goob job Jake, and do cherish the moment where you are having such insights and are proud of your own work. It's a rarity for many.

    On another note, the thing with OO is that it is often explained in an easy way. Take any text book and it will explain to you that object "Horse" is inherited from "Animal". Perhaps you inherit the property "legs" as an integer and "breathe" as a method. People understand this stuff, since they understand the actual classes/objects and their relationships from the physical world.

    Then you get to see some real world code and suddenly the objects are abstract. You get things like "FactoryEntityImplementerInterface". You can't imagine or visualize what it is, what it is supposed to do, and what relationship it would have with any other abstract object. It becomes a lot harder then.

    And as objects get more abstract, the amount of ways you can design them increases. It will not be neutral, it will be designed according to how that specific developer thinks. Finally, there is armies of developers really doing procedural development wrapped in OO static classes.

    It's hard to determine the right way and it's hard to get it right. Don't think the world is full of OO wizards and you are late to the party. Almost everyone struggles with it.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: