（程序员必知）97 Things Every Programmer Should Know

英文原文：

1. Act with Prudence
2. Apply Functional Programming Principles
3. Ask, “What Would the User Do?” (You Are Not the User)
4. Automate Your Coding Standard
5. Beauty Is in Simplicity
6. Before You Refactor
7. Beware the Share
8. The Boy Scout Rule
9. Check Your Code First Before Looking to Blame Others
10. Choose Your Tools with Care
11. Code in the Language of the Domain
12. Code Is Design
13. Code Layout Matters
14. Code Reviews
15. Coding with Reason
16. A Comment on Comments
17. Comment Only What the Code Cannot Say
18. Continuous Learning
19. Convenience is Not an -ility
20. Deploy Early and Often
21. Distinguish Business Exceptions from Technical
22. Do Lots of Deliberate Pratice
23. Domain-Specific Languages
24. Don’t Be Afraid to Break Things
25. Don’t Be Cute with Your Test Data
26. Don’t Ignore That Error!
27. Don’t Just Learn the Language, Understand Its Culture
28. Don’t Nail Your Program into the Upright Position
29. Don’t Rely on “Magic Happens Here”
30. Don’t Repeat Yourself
31. Don’t Touch That Code!
32. Encapsulate Behavior, Not Just State
33. Floating-Point Numbers Aren’t Real
34. Fulfill Your Ambitions with Open Source
35. The Golden Rule of API Design
36. The Guru Myth
37. Hard Work Does Not Pay Off
38. How to Use a Bug Tracker
39. Improve Code by Removing it
40. Install Me
41. Interprocess Communication Affects Application Response Time
42. Keep the Build Clean
43. Know How to use Comman-Line Tools
44. Know Well More Than Two Programming Languages
45. Know Your IDE
46. Know Your Limits
47. Know Your Next Commit
48. Large, Interconnected Data Belongs to a Database
49. Learn Foreign Languages
50. Learn to Estimate
51. Learn To Say, “Hello, World”
52. Let Your Project Speak for Itself
53. The Linker Is Not a Magical Program
54. The Longevity of Interim Solutions
55. Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly
56. Make the Invisible More Visible
57. Message Passing Leads to Better Scalablity in Parallel Systems
58. A Message to the Future
59. Missing Opportunities for Polymorphism
60. News of the Weird: Testers Are Your Friends
61. One Binary
62. Only the Code Tells the Truth
63. Own ( and Refactor ) the Build
64. Pair Program and Feel the Flow
65. Perfer Domain-Specific Types to Primitive Types
66. Pervent Errors
67. The Professional Programmer
68. Put Everything Under Version Control
69. Put the Mouse Down and Step Away from the Keyboard
70. Read Code
71. Read the Humanities
72. Reinvent the Wheel Often
73. Resist the Temptation of the Singleton Pattern
74. The Road to Performance is Littered with Dirty Code Bombs
75. Simplicity Comes from Reduction
76. The Single Responsibility Principle
77. Start from Yes
78. Step Back and Automate, Automate, Automate
79. Take Advantage of Code Analysis Tools
80. Test for Required Behavior, Not Incidental Behavior
81. Test Precisely and Concretely
82. Test While You Sleep(and over Weekends)
83. Testing Is the Engineering Rigor of Software Development
84. Thinking in States
85. Two Heads Are Often Better Than One
86. Two Wrongs Can Make a Right (and Are Difficult to Fix)
87. Ubuntu Coding for Your Friends
88. The Unix Tools Are Friends
89. Use the Right Algorithm and Data Structure
90. Verbose Logging Will Disturb Your Sleep
91. WET Dilutes Performance Bottlenecks
92. When Programmers and Testers Collaborate
93. Write Code As If You Had to Support It for the Rest of Your Life
94. Write Small Functions Using Examples
95. Write Tests for People
96. You Gotta Care About the Code
97. Your Customers Do Not Mean What They Say

中文翻译：

1.谨慎行事

2.应用功能编程原理

3.询问“用户会做什么？”（您不是用户）

4.自动化您的编码标准

5.美在简单中

6.在你重新行动之前

7.小心股票

8.童子军规则

9.在指责他人之前，先检查你的代码

10.谨慎选择工具

11.域名语言代码

12.代码就是设计

13.代码布局事项

14.代码评审

15.带原因的编码

16.评论

17.只评论代码不能说的内容

18.持续学习

19.便利不是不可能的

20.尽早、经常部署

21.区分商业例外和技术例外

22.做许多深思熟虑的练习

23.Domain-特定语言

24.不要害怕打碎东西

25.不要对你的测试数据感到恼火

26.不要忽视那个错误！

27.不要只学习语言，要了解它的文化

28.不要把你的程序钉在正确的位置

29.不要依赖“魔法在这里发生”

30.不要重复自己

31.别碰那个密码！

32.封装行为，而不仅仅是状态

33.浮点数不是真的

34.用开源实现你的抱负

35.API设计的黄金法则

36.上师神话

37.努力工作没有回报

38.如何使用Bug Tracker

39.通过删除代码来改进代码

40.安装我

41.进程间通信影响应用程序响应时间

42.保持建筑整洁

43.知道如何使用Comman Line工具

44.精通两种以上的程序设计语言

45.了解您的IDE

46.了解自己的极限

47.知道你的下一个承诺

48.大型互连数据属于数据库

49.学习外语

50.学会估计

51.学会说“你好，世界”

52.让你的项目自己说话

53.链接器不是一个神奇的程序

54.临时解决方案的寿命

55.使接口易于正确使用和难以错误使用

56.让看不见的东西更显眼

57.消息传递在并行系统中带来更好的可扩展性

58.给未来的信息

59.缺少多态性的机会

60.怪事新闻：测试人员是你的朋友

61.一个二进制

62.只有代码告诉真相

63.拥有（并重构）构建

64.配对程序并感受流量

65.对基元类型的Perfer域特定类型

66.普遍错误

67.专业程序员

68.将一切置于版本控制之下

69.放下鼠标，远离键盘

70.读取代码

71.阅读人文学科

72.经常更换车轮

73.抵制辛格尔顿模式的诱惑

74.通往表演之路充斥着肮脏的代码炸弹

75.简约源自简约

76.单一责任原则

77.从“是”开始

78.后退一步并自动化、自动化、自动化

79.利用代码分析工具

80.测试所需行为，而非偶然行为

81.精确而具体地测试

82.在睡觉时（以及周末）进行测试

83.测试是软件开发的工程钻机

84.状态思维

85.两个头往往比一个头好

86.两个错误可以使一个正确（而且很难纠正）

87.Ubuntu为你的朋友编码

88.Unix工具是朋友

89.使用正确的算法和数据结构

90.详细的日志记录会干扰你的睡眠

91.WET稀释性能瓶颈

92.当程序员和测试人员合作时

93.编写代码，就好像你必须在余生中支持它一样

94.使用示例编写小函数

95.为人们编写测试

96.你必须关心代码

97.你的客户说话不算数