blocks|key|1473775|text|卷起你的袖子和代码！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473776|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1259113|text|最简单的方法是学习SOLID、DRY、FIT、DDD、TDD、MVC等概念。当你查阅这些首字母缩写时，它会把你带入许多其他的洞穴，一旦你读完了，你应该很好地理解什么是更好的面向对象编程！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259114|实况播客：http://www.hanselminutes.com/default.aspx?showID=168、http://www.hanselminutes.com/default.aspx?showID=163|offset|length|1259115|固体分解：http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod|1259116|DRY：http://en.wikipedia.org/wiki/Don%2527t_repeat_yourself|1259117|适合：http://www.netwellness.org/question.cfm/38221.htm|1259118|DDD：http://dddcommunity.org/|1259119|DDD必读资料：http://www.infoq.com/minibooks/domain-driven-design-quickly|1259120|测试驱动程序：http://en.wikipedia.org/wiki/Test-driven_development|1259121|MVC：http://en.wikipedia.org/wiki/Model%25E2%2580%2593view%25E2%2580%2593controller|1259122|是的，卷起袖子编写代码总是一个好主意。尽你目前的能力做一个小项目。然后从上面读一篇文章。然后重构你的代码，以满足你刚刚读到的内容。重复这个过程，直到你把你的代码从地狱中重构出来。最后，你不仅应该知道面向对象是什么，而且你应该能够解释为什么它很重要，以及如何在第一时间获得它们。学习如何重构也是编写好代码的关键。现在的事情明天就不会好了。|1259123|entityMap|0|LINK|mutability|MUTABLE|url|http://www.hanselminutes.com/default.aspx?showID=168|1|http://www.hanselminutes.com/default.aspx?showID=163|2|http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod|3|http://en.wikipedia.org/wiki/Don%2527t_repeat_yourself|4|http://www.netwellness.org/question.cfm/38221.htm|5|http://dddcommunity.org/|6|http://www.infoq.com/minibooks/domain-driven-design-quickly|7|http://en.wikipedia.org/wiki/Test-driven_development|8|http://en.wikipedia.org/wiki/Model%25E2%2580%2593view%25E2%2580%2593controller^0|0|5|1G|0|1M|1G|1|0|5|1K|2|0|4|1G|3|0|3|1D|4|0|4|O|5|0|8|1N|6|0|7|1G|7|0|4|1U|8|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]|$D|1O|E|1P|1|1Q]]|A|$]]|$1|F|3|G|5|6|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|H|3|I|5|6|7|1V|8|@]|9|@$D|1W|E|1X|1|1Y]]|A|$]]|$1|J|3|K|5|6|7|1Z|8|@]|9|@$D|20|E|21|1|22]]|A|$]]|$1|L|3|M|5|6|7|23|8|@]|9|@$D|24|E|25|1|26]]|A|$]]|$1|N|3|O|5|6|7|27|8|@]|9|@$D|28|E|29|1|2A]]|A|$]]|$1|P|3|Q|5|6|7|2B|8|@]|9|@$D|2C|E|2D|1|2E]]|A|$]]|$1|R|3|S|5|6|7|2F|8|@]|9|@$D|2G|E|2H|1|2I]]|A|$]]|$1|T|3|U|5|6|7|2J|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]|13|$5|Y|Z|10|A|$11|14]]|15|$5|Y|Z|10|A|$11|16]]|17|$5|Y|Z|10|A|$11|18]]|19|$5|Y|Z|10|A|$11|1A]]|1B|$5|Y|Z|10|A|$11|1C]]|1D|$5|Y|Z|10|A|$11|1E]]|1F|$5|Y|Z|10|A|$11|1G]]|1H|$5|Y|Z|10|A|$11|1I]]]]

The easiest way is to learn concepts such as SOLID, DRY, FIT, DDD, TDD, MVC, etc. As you look up these acronyms it will lead you down many other rabbit holes and once you are done with your reading you should have a good understanding of what better object-oriented programming is!

SOLID podcasts: <a href="http://www.hanselminutes.com/default.aspx?showID=168" rel="noreferrer">http://www.hanselminutes.com/default.aspx?showID=168</a>, <a href="http://www.hanselminutes.com/default.aspx?showID=163" rel="noreferrer">http://www.hanselminutes.com/default.aspx?showID=163</a>

SOLID breakdown: <a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod" rel="noreferrer">http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod</a>

DRY: <a href="http://en.wikipedia.org/wiki/Don%27t_repeat_yourself" rel="noreferrer">http://en.wikipedia.org/wiki/Don%27t_repeat_yourself</a>

FIT: <a href="http://www.netwellness.org/question.cfm/38221.htm" rel="noreferrer">http://www.netwellness.org/question.cfm/38221.htm</a>

DDD: <a href="http://dddcommunity.org/" rel="noreferrer">http://dddcommunity.org/</a>

DDD required reading: <a href="http://www.infoq.com/minibooks/domain-driven-design-quickly" rel="noreferrer">http://www.infoq.com/minibooks/domain-driven-design-quickly</a>

TDD: <a href="http://en.wikipedia.org/wiki/Test-driven_development" rel="noreferrer">http://en.wikipedia.org/wiki/Test-driven_development</a>

MVC: <a href="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="noreferrer">http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller</a>

And yes, rolling up your sleeves and coding is always a good idea. Make a small project to the best of your current abilities. Then read an article from above. Then refactor your code to meet the needs of what you just read. Repeat until you have refactored the hell out of your code. At the end you should not only know what OO is all about but you should be able to explain why it is important and how to get their the first time. Learning how to refactor is a key to good code too. What is right now is not right tomorrow.

blocks|key|1473874|text|TDD在提高我的整体技能方面帮了我最多，包括OOP。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1473875|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Test-driven_development^0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow noreferrer">TDD</a> has helped me most in improving my overall skillset including OOP.

blocks|key|1259257|text|http://misko.hevery.com/code-reviewers-guide/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1259258|这些小而简单的规则会让你成为更好的OO程序员。在编写代码时严格遵守规则，您会发现您的代码比没有代码时更好。|1259259|您还需要学习可靠的原则：http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod|1259260|尽管这些编程原则和方法引起了争论，但它们是真正编写优秀代码的唯一途径。|1259261|您可能已经以这种方式编写了代码，但却不知道--如果是这样，那就太好了。但如果你需要一个目标去努力，这些就是黄金标准。|1259262|entityMap|0|LINK|mutability|MUTABLE|url|1|http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod^0|0|19|0|0|0|C|1K|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|4]]|S|$5|O|P|Q|C|$R|T]]]]

<a href="http://misko.hevery.com/code-reviewers-guide/" rel="nofollow noreferrer">http://misko.hevery.com/code-reviewers-guide/</a>

Those small simple rules will make you a better OO programmer. Follow the rules religiously as you code and you will find your code is better than it would otherwise be.

You'll also want to learn the Solid Principles: <a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod" rel="nofollow noreferrer">http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod</a>

As much as these principles and ways of programming cause debate, they are the only way to truly write excellent code.

You may already write code this way and not know it-- if so, great. But if you need a goal to strive towards, these are the gold standard.

blocks|key|1259306|text|变得更加敏捷，学习junit测试和研究领域驱动设计。我推荐Domain-Driven+Design:+Tackling+Complexity+in+the+Heart+of+Software这本书，尽管它在某些方面有点难。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1259307|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321125215^0|T|1U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Become more agile, learn junit testing and study about Domain Driven Design. I suggest the book <a href="https://rads.stackoverflow.com/amzn/click/com/0321125215" rel="nofollow noreferrer" rel="nofollow noreferrer">Domain-Driven Design: Tackling Complexity in the Heart of Software</a> although it's a bit tough at some points.

blocks|key|1474029|text|你们是我的目标观众。看看Building+Skills+in+OO+Design|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1474030|也许这能有所帮助。|1474031|entityMap|0|LINK|mutability|MUTABLE|url|http://homepage.mac.com/s_lott/books/oodesign.html^0|C|S|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You're my target audience. Look at <a href="http://homepage.mac.com/s_lott/books/oodesign.html" rel="nofollow noreferrer">Building Skills in OO Design</a>

Perhaps this can help.

blocks|key|1474080|text|你自己说过答案:练习。最好的解决方案是开发一款游戏。使用你在书中学到的概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474081|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You said the answer yourself: practice. Best solution for this is to develop a game. Use the concepts you learnt in the books there.

blocks|key|1474115|text|把事情计划好。问问你自己，你希望你的对象如何相互关联，并找出事情如何改变和模块化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474116|以这样一种方式编写代码:如果您想要更改一段代码，您只需更改这一段代码，而不是50个实例。|1474117|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Plan things out. Ask yourself how you want your objects to relate to eachother and seek out how things can be changed and modularized. 

Code things in such a way that if you wanted to change 1 piece of the code, you only have to change that 1 piece of code and not 50 instances of it.

blocks|key|1259450|text|学习一门不同的语言！大多数只使用Java+(仅作为示例)的开发人员对OO的理解有限，因为他们无法将语言功能和概念分开。如果你还不知道，可以看看python。如果你懂python，那就学习Ruby吧。或者选择一种函数式语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259451|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Learn a different language! Most developers using only Java (just as an example) have only a limited understanding of OO because they cannot separate language features and concepts. If you don't know it yet, have a look at python. If you know python, learn Ruby. Or choose one of the functional languages.

blocks|key|1474171|text|你读过Scott+Meyer第一版"Effective+C%2B%2B“一书中关于OO的章节了吗？它没有出现在后来的版本中，但它是一个很好的解释。标题基本上是关于合适的约定的“说出你的意思，意味着你所说的话”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474172|实际上，你可能想在here上看到我对类似问题的回答。|offset|length|1474173|HTH|1474174|干杯,|1474175|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/369402/book-opinion-the-object-oriented-thought-process-3rd-edition/369455#369455^0|0|9|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Have you read the chapter on OO from the first edition of Scott Meyers "Effective C++" book? It didn't make it to later editions, but it was a great explanation. The title was basically "say what you mean, mean what you say" about suitable conventions.

Actually, you might like to see my answer to a similar question over <a href="https://stackoverflow.com/questions/369402/book-opinion-the-object-oriented-thought-process-3rd-edition/369455#369455">here</a>.

HTH

cheers,

blocks|key|1259572|text|如果您不知道如何设计面向对象的系统，请从数据开始。弄清楚你需要跟踪什么东西，以及什么信息自然地组合在一起(例如，一个车型的所有规格都很好地组合在一起)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259573|您决定跟踪的每一种类型的东西都会变成一个类。|1259574|然后，当您需要能够执行特定的操作(例如，将一个型号的汽车标记为退役)或提出特定的问题(例如，询问给定型号的汽车在给定的一年中售出了多少辆)时，您可以将该功能加载到与其交互最频繁的类中。|1259575|一般来说，在你的类结构中应该总是有一个非常自然的地方来存放给定的代码。如果没有，这表明有一个地方的结构需要建造。|1259576|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you're lost as to how to design object-oriented systems, start with the data. Figure out what stuff you need to keep track of and what information naturally goes together (for example, all of the specs of a model of car group together nicely).

Each of these kinds of thing you decide to track becomes a class.

Then when you need to be able to execute particular actions (for example, marking a model of car as decommissioned) or ask particular questions (for example, asking how many of a given model of car were sold in a given year), you load that functionality onto the class it interacts with most heavily.

In general, there should always be a pretty natural place for a given bit of code to live in your class structure. If there isn't, that signals that there's a place where the structure needs to be built out.

blocks|key|1474278|text|放弃吧！你为什么需要那个面向对象的东西？只要写一些有用的应用就行了。不用OOP，过程化或函数式方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474279|无论您选择哪种方法，Python语言都应该适合于实践它。|1474280|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Give up! Why do you need that that OOP? Just write some usable app. Doesnt metter using OOP, procedual or functional approach.

Whataver approach you choose Python language should be sutable to practice it.

blocks|key|1259686|text|OOP技能是随着时间的推移而来的。阅读1、2本...10书籍并不能解决这个问题。练习编写一些代码。如果你从事的是编程工作，enviornment...that可能会很有帮助。如果不是，试着进入其中。提供免费开发一些应用程序。你得弄脏你的手。Remember...no应用程序从一开始就是完美的，这就是重构的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259687|另外，不要随着时间的推移而被OOP和much...it的某些东西所迷惑。担心开发功能齐全的应用程序。|1259688|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

OOP skills comes over time. Reading 1, 2 ...10 books doesn't cut it. Practice writing some code. If you are working in a programming enviornment...that can be helpful. If not try getting into one. Offer to develop some application(s) for free. You have to get your hands dirty. Remember...no application is perfect from the ground up.That's why there is re-factoring.

Also...don't get carried away with the OOP too much...it somes over time. Worry about developing fully functional applications.

blocks|key|1474373|text|OOP不是你可以通过阅读数千本书就能掌握的东西。相反，你必须感受到内在的概念。阅读任何东西，而不是试着去感受你读到的东西。在你的脑海中建立一个概念，当你面对一个新的场景时，试着匹配这些概念。在探索新事物时，验证和更新您的概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474374|祝好运!|1474375|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

OOP is not a thing you can master by reading thousands of books. Rather you have to feel the inner concepts. Read anything but try to feel what you read. Build a concept in the back of your mind and try to match those concepts when you face a new scenario. Verify and Update your concepts as you explore new things. 

Good luck!

blocks|key|1259767|text|在我尝试编写一个类似银行的程序来处理交易、计算利息并跟踪所有这些之后，OO终于对我产生了兴趣。我是在学习Java的时候做的。我建议你试一试，完成它，然后当你完成的时候去看看一个好的解决方案，看看你还可以做得更好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1259768|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

OO finally clicked for me after I tried to program a bank-like program that handled transactions, calculated interest, and kept track of it all. I did it while I was learning Java. I would suggest just trying it, completing it, and then when you're done go look at a GOOD solution and see what you could've done better.

blocks|key|1474450|text|我也认为OOP的技能主要是通过实践来增强的。如果你已经在公司工作了3年以上，可以考虑换个公司。当然，这并不适用于所有的工作，但通常情况下，一个人会习惯公司的项目和实践，并随着时间的推移而停止前进。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474451|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also think OOP skills strenghten mostly with practice. Consider changing your company, if you've been there for more than 3 years. Certainly, this is not valid for all jobs, but often a man gets used to the projects and practices at a company and stops advancing as time passes.

blocks|key|1474504|text|啤酒有帮助。我是认真的。躺在沙发上，拿着A3大小的便签簿，一支笔和一瓶啤酒。把狗、猫和妻子锁在外面。在放松的时候思考这个问题。甚至不敢在上面画API！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1474505|流程图、责任卡(CRC)和啤酒(但不是太多)起了很大的作用。|1474506|重构代码最简单的方法就是从一开始就不必这样做。|1474507|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

beer helps. seriously. lie out on a couch with an A3 sized scribble pad, a pen and a beer. Lock the dog, cat and wife outside. And think about the problem while relaxed. Don't even dare draw an API on it! 

Flowcharts, Responsibity cards (CRC) and beer (but not too much) go a long way. 

Easiest way to refactor code is to not have to in the first place.

blocks|key|1259903|text|+++++++public+void+MasteryOfOOP()+
++++{+
+++++++while(true)

++++++++/*+My+suggestion+is:+*/
+++++DO:+find+a+lot+of+well-written+object+oriented+code+and+read+it.++Then+
try+to+use+the+insights+from+it+on+your+own+coding.++Then+do+it+again.++Then+
have+a+colleague+who+is+a+good+OOP+look+at+it+and+comment.+Maybe+post+a+chunk+
of+your+code+on+SO+and+ask+for+how+it+could+be+improved.

++++++++Then+read+some+more+of+those+books.++Maybe+they+make+a+little+more+
sense+now...?

++++++++Now+go+back+to+the+top+of+this+post,+and+do+it+again.+

++++++++Repeat+Forever.

++++++++}
++++}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1259904|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> public void MasteryOfOOP() 
 { 
 while(true)

 /* My suggestion is: */
 DO: find a lot of well-written object oriented code and read it. Then 
try to use the insights from it on your own coding. Then do it again. Then 
have a colleague who is a good OOP look at it and comment. Maybe post a chunk 
of your code on SO and ask for how it could be improved.

 Then read some more of those books. Maybe they make a little more 
sense now...?

 Now go back to the top of this post, and do it again. 

 Repeat Forever.

 }
 }
</code></pre>

I have been programming in object-oriented languages for years now but secretly I look at some of the things my colleagues do with envy. A lot of them seem to have some inner OO instinct that I don't have - no matter how hard I try. I've read all the good books on OO but still can't seem to crack it. I feel like the guy who gave 110% to be a professional footballer but just didn't have the natural talent to make it. I'm at a loss and thinking of switching careers - what should do I?

How can I practice better object-oriented programming?

Python

Java

我已经用面向对象语言编程很多年了，但我会偷偷地看看我的同事们所做的一些令人羡慕的事情。他们中的许多人似乎都有一些我没有的面向对象的内在本能--不管我怎么努力。我已经读过了所有关于面向对象的好书，但似乎仍然不能破解它。我觉得自己就像一个为成为一名职业足球运动员付出了110%的努力，但却没有天赋的人。我不知所措，想着换个职...

问我怎样才能实践更好的面向对象编程？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我怎样才能实践更好的面向对象编程？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我怎样才能实践更好的面向对象编程？
EN