(by Jared Richardson, William A Gwaltney)
- Choose your habits
- Stay in the sandbox
- If you need it, check it in
- Script builds on day one
- Any machine can be a build machine
- Build continuously
- Test continuously
- Avoid collective memory loss
- Exercise your product--automate your tests
- Use a common, flexible test harness
- Use the best tool for the job
- Use open formats to integrate tools
- Keep critical path technologies familiar
- Work to the list
- Let a tech lead
- Use daily meetings for frequent course corrections
- It's OK to say "later"
- Always review all code
- The goal is software, not compliance
- Architect as a group
- If production uses it, you should too
- Solve the hardest programs first
- An encapsulated architecture is a scalable architecture
- You can't steer a boat unless its moving
- Don't change legacy code until you can test it
- Use test-driven refactoring to clean up untestable code
- Mock client tests do the most with the least
- Continuously test changing code
- It has to work for everyone
- Integrate often, build and test continuously
- Deliver live demos early & often
- Publicize what you're doing and why
- Face time builds teamwork
- Only fix what needs fixing
- Disruptive best practices aren't
- Innovate from the bottom up
- Show, don't just tell
- Cultivate management buy-in
- Test continuously
- Test where the bugs are
- The list is a living document
- If it's not on the list, it's not part of the project
- Always give feedback fast
Tags:
reading
books
Last modified 16 December 2024