(by Jared Richardson, William A Gwaltney)

  1. Choose your habits
  2. Stay in the sandbox
  3. If you need it, check it in
  4. Script builds on day one
  5. Any machine can be a build machine
  6. Build continuously
  7. Test continuously
  8. Avoid collective memory loss
  9. Exercise your product--automate your tests
  10. Use a common, flexible test harness
  11. Use the best tool for the job
  12. Use open formats to integrate tools
  13. Keep critical path technologies familiar
  14. Work to the list
  15. Let a tech lead
  16. Use daily meetings for frequent course corrections
  17. It's OK to say "later"
  18. Always review all code
  19. The goal is software, not compliance
  20. Architect as a group
  21. If production uses it, you should too
  22. Solve the hardest programs first
  23. An encapsulated architecture is a scalable architecture
  24. You can't steer a boat unless its moving
  25. Don't change legacy code until you can test it
  26. Use test-driven refactoring to clean up untestable code
  27. Mock client tests do the most with the least
  28. Continuously test changing code
  29. It has to work for everyone
  30. Integrate often, build and test continuously
  31. Deliver live demos early & often
  32. Publicize what you're doing and why
  33. Face time builds teamwork
  34. Only fix what needs fixing
  35. Disruptive best practices aren't
  36. Innovate from the bottom up
  37. Show, don't just tell
  38. Cultivate management buy-in
  39. Test continuously
  40. Test where the bugs are
  41. The list is a living document
  42. If it's not on the list, it's not part of the project
  43. Always give feedback fast

Tags: reading   books  

Last modified 06 April 2022