Write the code into art and realize the idea of object-oriented programming

See a stern post, make yourself afraid of the momentary tremble ....

Http://www.cnblogs.com/menglin2010/archive/2012/02/08/2342029.html

We are learning object-oriented programming languages such as: java,c#, we are in the banner of object-oriented programming, but do the work of process-oriented programming

Now we basically go to a company, go up to write code, the boss let us new features, we began to write a novel method, to do process-oriented programming, everyone constantly to the original net field to add their own code, the original code block like a public toilet, everyone in the inside of the poop, And no one to maintain clean, finally smelly, imagine we have no real use of object-oriented language of the three major features, encapsulation, inheritance, polymorphism, I think most people use the most is the entity class, the entity class just embodies the characteristics of encapsulation, inheritance does not manifest, a dragon, nine of different, The polymorphic nature of the mouse's son's hole-punching is even less evident.

I think when we leave one day from a company, we have to transfer all the documents of the project to the new colleague, he can work, it must be to modify your code, and scold you, I think we all know that the code to modify others far more painful than the code they wrote, see your countless files countless lines of code are painful to die , in fact, a good architecture, just tell you the interface, you just have to implement the details inside, no need to control other files or code

If you're still doing process-oriented programming, you'll never get to the architect's path and never grow

Write the code into art and realize the idea of object-oriented programming