97 Things Every Programmer Should Know (oreilly.com)

Contributions Appearing in the Book

1. Act with Prudence bySeb Rose
2. Apply Functional Programming Principles byEdward Garson
3. Ask "What Would the User Do?" (You Are not the User) byGiles Colborne
4. Automate Your Coding Standard byFilip van Laenen
5. Beauty Is in Simplicity byJørn Ølmheim
6. Before You Refactor byRajith Attapattu
7. Beware the Share byUdi Dahan
8. The Boy Scout Rule byUncle Bob
9. Check Your Code First before Looking to Blame Others byAllan Kelly
10. Choose Your Tools with Care byGiovanni Asproni
11. Code in the Language of the Domain byDan North
12. Code Is Design byRyan Brush
13. Code Layout Matters bySteve Freeman
14. Code Reviews byMattias Karlsson
15. Coding with Reason byYechiel Kimchi
16. A Comment on Comments byCal Evans
17. Comment Only What the Code Cannot Say byKevlin Henney
18. Continuous Learning byClint Shank
19. Convenience Is not an -ility byGregor Hohpe
20. Deploy Early and Often bySteve Berczuk
21. Distinguish Business Exceptions from Technical byDan Bergh Johnsson
22. Do Lots of Deliberate Practice byJon Jagger
23. Domain-Specific Languages byMichael Hunger
24. Don't Be Afraid to Break Things byMike Lewis
25. Don't Be Cute with Your Test Data byRod Begbie
26. Don't Ignore that Error! byPete Goodliffe
27. Don't Just Learn the Language, Understand its Culture byAnders Norås
28. Don't Nail Your Program into the Upright Position byVerity Stob
29. Don't Rely on "Magic Happens Here" byAlanGriffiths
30. Don't Repeat Yourself bySteve Smith
31. Don't Touch that Code! byCal Evans
32. Encapsulate Behavior, not Just State byEinar Landre
33. Floating-point Numbers Aren't Real byChuck Allison
34. Fulfill Your Ambitions with Open Source byRichard Monson-Haefel
35. The Golden Rule of API Design byMichael Feathers
36. The Guru Myth byRyan Brush
37. Hard Work Does not Pay Off byOlve Maudal
38. How to Use a Bug Tracker byMatt Doar
39. Improve Code by Removing It byPete Goodliffe
40. Install Me byMarcus Baker
41. Inter-Process Communication Affects Application Response Time by Randy Stafford
42. Keep the Build Clean byJohannes Brodwall
43. Know How to Use Command-line Tools byCarroll Robinson
44. Know Well More than Two Programming Languages byRussel Winder
45. Know Your IDE byHeinz Kabutz
46. Know Your Limits byGreg Colvin
47. Know Your Next Commit byDan Bergh Johnsson
48. Large Interconnected Data Belongs to a Database byDiomidis Spinellis
49. Learn Foreign Languages byKlaus Marquardt
50. Learn to Estimate byGiovanni Asproni
51. Learn to Say "Hello, World" byThomas Guest
52. Let Your Project Speak for Itself byDaniel Lindner
53. The Linker Is not a Magical Program byWalter Bright
54. The Longevity of Interim Solutions byKlaus Marquardt
55. Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly by Scott Meyers
56. Make the Invisible More Visible byJon Jagger
57. Message Passing Leads to Better Scalability in Parallel Systems by Russel Winder
58. A Message to the Future byLinda Rising
59. Missing Opportunities for Polymorphism byKirk Pepperdine
60. News of the Weird: Testers Are Your Friends byBurk Hufnagel
61. One Binary bySteve Freeman
62. Only the Code Tells the Truth byPeter Sommerlad
63. Own (and Refactor) the Build bySteve Berczuk
64. Pair Program and Feel the Flow byGudny Hauknes, Ann Katrin Gagnat, and Kari Røssland
65. Prefer Domain-Specific Types to Primitive Types byEinar Landre
66. Prevent Errors byGiles Colborne
67. The Professional Programmer byUncle Bob
68. Put Everything Under Version Control byDiomidis Spinellis
69. Put the Mouse Down and Step Away from the Keyboard byBurk Hufnagel
70. Read Code byKarianne Berg
71. Read the Humanities byKeith Braithwaite
72. Reinvent the Wheel Often byJason P Sage
73. Resist the Temptation of the Singleton Pattern bySam Saariste
74. The Road to Performance Is Littered with Dirty Code Bombs byKirk Pepperdine
75. Simplicity Comes from Reduction byPaul W. Homer
76. The Single Responsibility Principle byUncle Bob
77. Start from Yes byAlex Miller
78. Step Back and Automate, Automate, Automate byCay Horstmann
79. Take Advantage of Code Analysis Tools bySarah Mount
80. Test for Required Behavior, not Incidental Behavior byKevlin Henney
81. Test Precisely and Concretely byKevlin Henney
82. Test While You Sleep (and over Weekends) byRajith Attapattu
83. Testing Is the Engineering Rigor of Software Development byNeal Ford
84. Thinking in States byNiclas Nilsson
85. Two Heads Are Often Better than One byAdrian Wible
86. Two Wrongs Can Make a Right (and Are Difficult to Fix) byAllan Kelly
87. Ubuntu Coding for Your Friends byAslam Khan
88. The Unix Tools Are Your Friends byDiomidis Spinellis
89. Use the Right Algorithm and Data Structure byJC van Winkel
90. Verbose Logging Will Disturb Your Sleep byJohannes Brodwall
91. WET Dilutes Performance Bottlenecks byKirk Pepperdine
92. When Programmers and Testers Collaborate byJanet Gregory
93. Write Code as If You Had to Support It for the Rest of Your Life by Yuriy Zubarev
94. Write Small Functions Using Examples byKeith Braithwaite
95. Write Tests for People byGerard Meszaros
96. You Gotta Care about the Code byPete Goodliffe
97. Your Customers Do not Mean What They Say byNate Jackson

http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book