最好的Java编程书籍
2011-07-31
《Thinking in Java》应该是目前为止市场上能买到的最好java学习书籍了，手头需要有一本以供时常翻阅。Bruce Eckel在书中不仅仅讲解了Java的语法，更重要的是将OOP编程思想循序渐进、浅显易懂地表达出来。从这点上来说《Thinking in Java》中文版翻译成《Java编程思想》非常恰当!
《Thinking in Java》第三版附录后面有一些Java编程规范，不知为啥第四版时却看不到了，有点可惜，就抄录顺便翻译了下，有的items加上了些自己的理解。
Java Programming Guidelines
1, Elegance always pays off.
优雅总是物有所值。
2, First make it work, then make it fast.
先让程序可以工作，再让它跑得更快。
3，Remember the "divide and conquer" principle.
记住“分而治之”原则。
4，Separate the class creator from the class user(client programmer).
分隔类的创建者和使用者。(让类和接口容易被正确使用，不容易被错误使用)
5，When you create a class, attempt to make your names so clear that comments are unnecessary.
给类取名时，让类名一目了然到无需写注释。(Single Responsibility Principal)
6, Your analysis and design must produce, at minimum, the classes in your system, their public interfaces, and their relationships to other classes, especially base classes.
7, Automate everything.
一切自动化。(Ant, hudson)
8,Write the test code first(before you write the class) in order to verify that your class design is complete.
测试代码先行（先于类）来验证你的类设计是完善的。JUnit
9, All software design problems can be simplified by introducing an extra level of conceptual indirection.
所有的软件设计问题都可以通过引入一层间接层来简化。(设计模式)
10, An indirection should have a meaning.
间接层需要有其存在的意义。(封装变化)
11, Make classes as atomic as possible.Give each class a single, clear purpose.
尽量保持类的原子性，给每个类一个简单、清晰的目的。(Single Responsibility Principal)
12，Watch for long argument list.
避免长参数列表.
13, Don't repeat yourself.
代码不要重复。(DRY)
14, Watch for switch statements or chained if-else clauses.
避免复杂的switch语句和链式if-else语句。(使用polymorphism)
15, From a design standpoint, look for and separate things that change from things that stay the same.
站在设计的观点，找出、分离不变之物与常变之物。(封装变化)
16, Don't extends fundamental functionality by subclassing.
不要通过子类继承来扩展基本功能。(优先考虑组合，Decorator模式)
17, Less is more.
少即是多。
18, Read your classes aloud to make sure they're logical.
大声朗读类名以确保它们是合情合理的。
19, When deciding between inheritance and composition, ask if you need to upcast to the base type.
在继承和组合之间难以取舍时，考虑该类是否需要向上转化为其基类。(是否需要使用polymorphism)
20，Use fields for variation in value, and method overriding fro variation in behavior.
值差异用域，行为差异用方法覆盖。
21, Watch for overloading.
避免重载.（使用好的方法名)
22, Use exception hierarchies.
使用层次化的异常。
23, Sometimes simple aggregation does the job.
有时简单的组合就能解决问题。
24, Consider the perspective of the client programmer and the person maintaining the code.
从client端程序员和维护代码的人角度考虑问题。(让类和接口容易被正确使用，不容易被错误使用)
25, Watch out for "giant object syndrome".
避免“巨型对象综合症”。(运用SRP分解对象泥团)
26, If you must do something ugly, at least localize the ugliness inside a class.
如果逼不得已必须写一些丑陋的代码，把这些代码局限在一个类中。
27, If you must do something nonportable, make an abstraction for that service and localize it within a class.
28, Objects should not simply hold some data.
对象不应仅仅只拥有数据。还需要有methods。
29, Choose composition first when creating new classes from existing classes.
从已有类中创建新类时，优先考虑组合。
30, Use inheritance and method overriding to express differences in behavior, and fields to express variations in state.
行为变化用继承和方法覆盖搞定，变量状态变化用域表示。(State模式)
31, Watch out for variance.
考虑变化。(使用接口，抽象类)
32, Watch out for limitation during inheritance.
当心继承的局限性。(类层次过多、Java单继承)
33, Use design patterns to eliminate "naked functionality".
34, Watch out for "analysis paralysis".
避免“分析瘫痪”。(避免过度分析，先快速做出原型)
35, When you think you've got a good analysis, design, or implementation, do a walkthrough.
当你认为你有一个好的分析、设计或是实现时，演练一下。