blocks|key|3970875|text|Head+First有一些很棒的OOP书籍，涵盖了Object-Oriented+Analysis+and+Design和Object-Oriented+Design+Patterns。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3970876|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0596008678|1|https://rads.stackoverflow.com/amzn/click/com/0596007124^0|P|Z|0|1P|V|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

There are some great OOP books from Head First covering <a href="https://rads.stackoverflow.com/amzn/click/com/0596008678" rel="noreferrer" rel="nofollow noreferrer">Object-Oriented Analysis and Design</a> and <a href="https://rads.stackoverflow.com/amzn/click/com/0596007124" rel="noreferrer" rel="nofollow noreferrer">Object-Oriented Design Patterns</a>.

blocks|key|696426|text|我推荐你阅读David+West的Object+Thinking。书中只有很少的代码，但有很多关于如何建模的讨论。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|696427|当我刚开始的时候，我希望有人能告诉我几件事：|696428|696429|在对对象建模时，您应该更多地关注行为，而不是数据的形状。|ordered-list-item|696430|尽管许多面向对象的教程都对现实世界的事物进行建模，如动物和车辆，但我们在面向对象软件中建模的许多事物都是概念和构造(在现实世界中没有物理表示的事物)。|696431|696432|entityMap|0|LINK|mutability|MUTABLE|url|http://polymorphicpodcast.com/shows/objectthinking/|1|https://rads.stackoverflow.com/amzn/click/com/0735619654^0|6|A|0|H|F|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|16|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]]]

I recommend you read <a href="https://rads.stackoverflow.com/amzn/click/com/0735619654" rel="noreferrer" rel="nofollow noreferrer">Object Thinking</a> by <a href="http://polymorphicpodcast.com/shows/objectthinking/" rel="noreferrer">David West</a>. There is very little code in the book, but a lot of talk about how to model.

A couple things I wish someone would have told me when I was starting out are:

<ol>
<li>When modeling objects, you should focus on behaviors more than the shape of the data.</li>
<li>Although many OO tutorials model real world things such as animals and vehicles, many of the things we model in OO software are concepts and constructs (things that have no physical representation in the real world).</li>
</ol>

blocks|key|2600225|text|我建议主要使用强类型语言，如C#或Java，因为许多设计模式和一般OOP原则都是面向强类型的(GOF、Refactoring、Uncle+Bob)。Ruby很棒，但是很多常见的OOP原则都不适用，比如对接口进行编码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2600226|花点时间学习鲍勃大叔的SOLID原则。慢慢来，特别注意单一的责任。如果你没有从Bob叔叔那里得到任何其他东西，在你的头脑中获得SRP，并尽早并经常应用它。|2600227|我也喜欢Bob叔叔的编码katas的想法。我建议通过bowling+game+kata工作。|2600228|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0201633612|1|http://martinfowler.com/books.html#refactoring|2|http://butunclebob.com/ArticleS.UncleBob|3|http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod|4|http://butunclebob.com/ArticleS.UncleBob.TheBowlingGameKata^0|1B|3|0|1F|B|1|1R|9|2|0|B|5|3|0|Q|H|4|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]|$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|H|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]|T|$5|K|L|M|C|$N|U]]|V|$5|K|L|M|C|$N|W]]]]

I'd recommend working mainly with a strongly-typed language like C# or Java, as so many of the design patterns and general OOP principles are geared towards strong typing (<a href="https://rads.stackoverflow.com/amzn/click/com/0201633612" rel="noreferrer" rel="nofollow noreferrer">GOF</a>, <a href="http://martinfowler.com/books.html#refactoring" rel="noreferrer">Refactoring</a>, <a href="http://butunclebob.com/ArticleS.UncleBob" rel="noreferrer">Uncle Bob</a>). Ruby is wonderful but a lot of common OOP principles like coding to interfaces won't apply. 

Spend some time with Uncle Bob's <a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod" rel="noreferrer">SOLID</a> principles. Go slowly, paying particular attention to Single Responsibility. If you don't get anything else from Uncle Bob, get SRP in your head and apply it early and often.

I also like Uncle Bob's idea of code katas. I'd recommend working through the <a href="http://butunclebob.com/ArticleS.UncleBob.TheBowlingGameKata" rel="noreferrer">bowling game kata</a>.

blocks|key|190200|text|要真正熟悉面向对象编程，您可以做几件事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190201|190202|强迫你自己用对象来模拟现实世界的问题。创建类来表示对象，并创建方法来表示它们可以做的事情。|ordered-list-item|190203|使用的语言和/或框架确实迫使您使用OOP。直到我上了一个Java类，开始大量使用Swing，我才真正理解了OOP。我最近没怎么用过C#，但我认为C#或Java都是不错的选择。|190204|190205|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

To truly get comfortable with object oriented programming there are a couple of things you can do. 

<ol>
<li>Force yourself to model a real world problem with objects. Create classes to represent the objects, and methods to represent things they can do. </li>
<li>Use a language and / or a framework that really forces OOP on you. It wasn't until I took a Java class and started using Swing heavily that I really grokked OOP. I haven't played much with C# recently, but I think either C# or Java would be a good way to go. </li>
</ol>

blocks|key|190340|text|试着学习Smalltalk+--提高你的OO编程水平的最好方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190341|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|$]]

Try learning Smalltalk - best way to improve your OO programming.

blocks|key|3971075|text|在掌握了基础知识之后，最好的方法就是通过实例来学习。下载流行的开源项目并深入研究它们。一些我从中学到很多的项目：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3971076|3971077|Rhino+Tools|unordered-list-item|offset|length|3971078|ASPNET+MVC|3971079|Unity+-责任链pattern.|3971080|NHibernate|3971081|的一些很好的实现|3971082|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/ayende/rhino-tools|1|http://www.microsoft.com/downloads/details.aspx?FamilyID=53289097-73ce-43bf-b6a6-35e00103cb4b&displaylang=en|2|http://www.codeplex.com/Wikipage?ProjectName=unity|3|http://www.nhibernate.org/^0|0|0|0|B|0|0|0|A|1|0|0|5|2|0|0|A|3|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|15|8|@]|9|@$F|16|G|17|1|18]]|A|$]]|$1|H|3|I|5|E|7|19|8|@]|9|@$F|1A|G|1B|1|1C]]|A|$]]|$1|J|3|K|5|E|7|1D|8|@]|9|@$F|1E|G|1F|1|1G]]|A|$]]|$1|L|3|M|5|E|7|1H|8|@]|9|@$F|1I|G|1J|1|1K]]|A|$]]|$1|N|3|O|5|6|7|1L|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]|11|$5|S|T|U|A|$V|12]]]]

After getting a basic idea for the fundamentals, the best way is to learn by example. Download popular open source projects and dig your way through them. Some projects I've learned a lot from:

<ul>
<li><a href="http://github.com/ayende/rhino-tools" rel="nofollow noreferrer">Rhino Tools</a></li>
<li><a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=53289097-73ce-43bf-b6a6-35e00103cb4b&amp;displaylang=en" rel="nofollow noreferrer">ASPNET MVC</a></li>
<li><a href="http://www.codeplex.com/Wikipage?ProjectName=unity" rel="nofollow noreferrer">Unity</a> - has some good implementations of the chain of responsibility pattern.</li>
<li><a href="http://www.nhibernate.org/" rel="nofollow noreferrer">NHibernate</a></li>
</ul>

blocks|key|2608229|text|我最近把PHP转换成了C#，我喜欢它的每一分钟！我想说的是，给自己找一个有灵活时间表的新项目，然后投入进去。也可以买几本书，特别是关于OOP概念和设计模式的书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2608230|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've recently converted from PHP to C# and love every minute of it! I'd say find yourself a new project with a flexible timeline and just dive in. Get a couple books too, particularly on OOP concepts and design patterns.

blocks|key|190486|text|阅读Bertrand+Meyer's+OOSC2。这可能是有史以来关于面向对象编程的最好的书。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|190487|entityMap|0|LINK|mutability|MUTABLE|url|http://www.amazon.co.uk/Object-oriented-Software-Construction-Prentice-Hall-Resource/dp/0136291554/ref=sr_1_1?ie=UTF8&s=books&qid=1262273193&sr=8-1^0|2|M|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]]]]

Read <a href="http://www.amazon.co.uk/Object-oriented-Software-Construction-Prentice-Hall-Resource/dp/0136291554/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1262273193&amp;sr=8-1" rel="nofollow noreferrer">Bertrand Meyer's OOSC2</a>. It's probably the best book ever on OO programming.

blocks|key|688148|text|这取决于你懂什么语言。就我个人而言，我会推荐一些面向对象的脚本语言。例如PHP或Python，我相信这会帮助你顺利过渡。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|688149|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|$]]

It depends on what languages you know. Personally I would recommend some type of OO scripting language. IE PHP or Python, I believe this will help you transition semi-smoothly.

blocks|key|190393|text|我认为你可以研究一下测试驱动开发。这会自动引导你遵守面向对象原则的规则。这是一种实用的方法，但它是有效的。您还可以通过学习理论问题来支持此过程，如可靠原则和设计模式。阅读大型项目的源代码也是提高面向对象技能的好主意|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190394|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 think you can do research about Test Driven Development. This automatically orient you obeying the rules of Object Oriented Principles. This is the practical way but it works. You can also support this process with learning teorical issues, like SOLID principles and Design patterns. Reading the source code of big projects is also good idea to improve your object oriented skills

blocks|key|190430|text|我希望很久以前给我的一条建议是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190431|190432|不要过度使用继承。|blockquote|190433|190434|190435|对于初学者(imho)来说，这是一个非常容易的陷阱，因为它是每个人都在谈论的OOP中的一个重要概念。|190436|基本上，你应该只在真正有意义的地方使用继承-想想数据类型，一些小部件层次结构，关系是如此明显，任何人都会使用它。否则，您应该将对象注入到其他对象中并调用它们，以便更改功能(组合)。|190437|当您可以使用单个类并注入(构造器的参数)一个对象来实现一个接口时，不要试图只定义一个抽象方法的加载，并多次重写以不同的方式实现它们，您可以调用该接口来执行您本来会放在抽象方法中的任何变量功能。这将导致更简单和更可重用的代码(在我的经验中)，也更可测试。|190438|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

One piece of advice I wish had been given to me a long time ago is:

<blockquote>
 Don't over-use inheritance.
</blockquote>

This is a really easy pitfall for a beginner (imho) as it is one of the big concepts in OOP that everyone talks about.

Basically, you should be using inheritance only where it really really makes sense - think data types, some widget hierarchies, stuff where the is-a relationship is so obvious anybody would have used it. Otherwise you should be injecting objects into others and calling them in order to change functionality (composition).

Do not be tempted to just define a load of abstract methods and override multiple times to implement them differently when you could have a single class and inject (argument to constructor) an object implementing an interface that you call to do whatever variable functionality that you would otherwise have put in the abstract methods.
This will lead to much simpler and more reusable code (in my experience), and more testable too.

blocks|key|3971170|text|为了掌握你的面向对象技能，你需要大量的练习。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3971171|试着用“对象术语”来思考你对代码所做的一切。|3971172|应用它：|3971173|3971174|in+your+server-side+language|unordered-list-item|3971175|3971176|+your+Java+Script+code+|3971177|3971178|考虑让你的CSS代码易于重用，并且避免重复。|3971179|3971180|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|I|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|-4|5|I|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|I|7|10|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|R|$]]

In order to master your Object oriented skills you need a lot of practice.

Try to think in "object terms" for about everything you do with code.

<h1>Apply it :</h1>

<ul>
<li>in your server-side language</li>
<li>keep your Java Script code object oriented</li>
<li>think about keeping your CSS code easily reusable and contains low duplicity.</li>
</ul>

I understand procedural programming (well, who doesnt) and want to get a good understanding of OOP and after that functional. I'm just a hobbyist so it will take me an age and a day, but its fun.

Does anyone have any ideas for what I can do to help? Project ideas? Example well documented code thats out their?

I am currently using C++ but C# looks a lot nicer to work with.

How can I improve my Object Oriented Programming?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我理解过程化编程(好吧，谁不懂)，并且想要更好地理解OOP以及之后的函数式编程。我只是一个业余爱好者，所以这需要我花上一年零一天的时间，但这很有趣。有谁知道我能帮上什么忙吗？项目点子？示例记录良好的代码，这是他们？我目前使用的是C++，但使用C#看起来要好得多。

问我如何改进我的面向对象编程？
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何改进我的面向对象编程？EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何改进我的面向对象编程？
EN