97 Things Every Programmer Should Know

1. Act with PrudencebySeb Rose
2. Apply Functional Programming PrinciplesbyEdward Garson
3. Ask "What Would the User Do?" (You Are not the User)byGiles Colborne
4. Automate Your Coding StandardbyFilip van Laenen
5. Beauty Is in SimplicitybyJørn Ølmheim
6. Before You RefactorbyRajith Attapattu
7. Beware the SharebyUdi Dahan
8. The Boy Scout RulebyUncle Bob
9. Check Your Code First before Looking to Blame OthersbyAllan Kelly
10. Choose Your Tools with CarebyGiovanni Asproni
11. Code in the Language of the DomainbyDan North
12. Code Is DesignbyRyan Brush
13. Code Layout MattersbySteve Freeman
14. Code ReviewsbyMattias Karlsson
15. Coding with ReasonbyYechiel Kimchi
16. A Comment on CommentsbyCal Evans
17. Comment Only What the Code Cannot SaybyKevlin Henney
18. Continuous LearningbyClint Shank
19. Convenience Is not an -ilitybyGregor Hohpe
20. Deploy Early and OftenbySteve Berczuk
21. Distinguish Business Exceptions from TechnicalbyDan Bergh Johnsson
22. Do Lots of Deliberate PracticebyJon Jagger
23. Domain-Specific LanguagesbyMichael Hunger
24. Don't Be Afraid to Break ThingsbyMike Lewis
25. Don't Be Cute with Your Test DatabyRod Begbie
26. Don't Ignore that Error!byPete Goodliffe
27. Don't Just Learn the Language, Understand its CulturebyAnders Norås
28. Don't Nail Your Program into the Upright PositionbyVerity Stob
29. Don't Rely on "Magic Happens Here"byAlanGriffiths
30. Don't Repeat YourselfbySteve Smith
31. Don't Touch that Code!byCal Evans
32. Encapsulate Behavior, not Just StatebyEinar Landre
33. Floating-point Numbers Aren't RealbyChuck Allison
34. Fulfill Your Ambitions with Open SourcebyRichard Monson-Haefel
35. The Golden Rule of API DesignbyMichael Feathers
36. The Guru MythbyRyan Brush
37. Hard Work Does not Pay OffbyOlve Maudal
38. How to Use a Bug TrackerbyMatt Doar
39. Improve Code by Removing ItbyPete Goodliffe
40. Install MebyMarcus Baker
41. Inter-Process Communication Affects Application Response TimebyRandy Stafford
42. Keep the Build CleanbyJohannes Brodwall
43. Know How to Use Command-line ToolsbyCarroll Robinson
44. Know Well More than Two Programming LanguagesbyRussel Winder
45. Know Your IDEbyHeinz Kabutz
46. Know Your LimitsbyGreg Colvin
47. Know Your Next CommitbyDan Bergh Johnsson
48. Large Interconnected Data Belongs to a DatabasebyDiomidis Spinellis
49. Learn Foreign LanguagesbyKlaus Marquardt
50. Learn to EstimatebyGiovanni Asproni
51. Learn to Say "Hello, World"byThomas Guest
52. Let Your Project Speak for ItselfbyDaniel Lindner
53. The Linker Is not a Magical ProgrambyWalter Bright
54. The Longevity of Interim SolutionsbyKlaus Marquardt
55. Make Interfaces Easy to Use Correctly and Hard to Use IncorrectlybyScott Meyers
56. Make the Invisible More VisiblebyJon Jagger
57. Message Passing Leads to Better Scalability in Parallel SystemsbyRussel Winder
58. A Message to the FuturebyLinda Rising
59. Missing Opportunities for PolymorphismbyKirk Pepperdine
60. News of the Weird: Testers Are Your FriendsbyBurk Hufnagel
61. One BinarybySteve Freeman
62. Only the Code Tells the TruthbyPeter Sommerlad
63. Own (and Refactor) the BuildbySteve Berczuk
64. Pair Program and Feel the FlowbyGudny Hauknes,Ann Katrin Gagnat, andKari Røssland
65. Prefer Domain-Specific Types to Primitive TypesbyEinar Landre
66. Prevent ErrorsbyGiles Colborne
67. The Professional ProgrammerbyUncle Bob
68. Put Everything Under Version ControlbyDiomidis Spinellis
69. Put the Mouse Down and Step Away from the KeyboardbyBurk Hufnagel
70. Read CodebyKarianne Berg
71. Read the HumanitiesbyKeith Braithwaite
72. Reinvent the Wheel OftenbyJason P Sage
73. Resist the Temptation of the Singleton PatternbySam Saariste
74. The Road to Performance Is Littered with Dirty Code BombsbyKirk Pepperdine
75. Simplicity Comes from ReductionbyPaul W. Homer
76. The Single Responsibility PrinciplebyUncle Bob
77. Start from YesbyAlex Miller
78. Step Back and Automate, Automate, AutomatebyCay Horstmann
79. Take Advantage of Code Analysis ToolsbySarah Mount
80. Test for Required Behavior, not Incidental BehaviorbyKevlin Henney
81. Test Precisely and ConcretelybyKevlin Henney
82. Test While You Sleep (and over Weekends)byRajith Attapattu
83. Testing Is the Engineering Rigor of Software DevelopmentbyNeal Ford
84. Thinking in StatesbyNiclas Nilsson
85. Two Heads Are Often Better than OnebyAdrian Wible
86. Two Wrongs Can Make a Right (and Are Difficult to Fix)byAllan Kelly
87. Ubuntu Coding for Your FriendsbyAslam Khan
88. The Unix Tools Are Your FriendsbyDiomidis Spinellis
89. Use the Right Algorithm and Data StructurebyJC van Winkel
90. Verbose Logging Will Disturb Your SleepbyJohannes Brodwall
91. WET Dilutes Performance BottlenecksbyKirk Pepperdine
92. When Programmers and Testers CollaboratebyJanet Gregory
93. Write Code as If You Had to Support It for the Rest of Your LifebyYuriy Zubarev
94. Write Small Functions Using ExamplesbyKeith Braithwaite
95. Write Tests for PeoplebyGerard Meszaros
96. You Gotta Care about the CodebyPete Goodliffe
97. Your Customers Do not Mean What They SaybyNate Jackson

References:

http://programmer.97things.oreilly.com

http://www.infoq.com/news/2009/09/97-things

END