I am a Pragmatic Programmer Part 7

This is Part 7 of 7 part series inspired from the book Pragmatic Programmer, read Part 6 here:

1. Use a Project Glossary: Create and maintain a single source of all the
   specific terms and vocabulary for a project.
2. Start When You’re Ready: You’ve been building experience all your
   life. Don’t ignore niggling doubts.
3. Don’t Be a Slave to Formal Methods: Don’t blindly adopt any technique
   without putting it into the context of your development practices and
   capabilities.
4. Organize Teams Around Functionality: Don’t separate designers from
   coders, testers from data modelers. Build teams the way you build
   code.
5. Test Early. Test Often. Test Automatically: Tests that run with every
   build are much more effective than test plans that sit on a shelf.
6. Use Saboteurs to Test Your Testing: Introduce bugs on purpose in a
   separate copy of the source to verify that testing will catch them.
7. Find Bugs Once: Once a human tester finds a bug, it should be the last
   time a human tester finds that bug. Automatic tests should check for
   it from then on.
8. Build Documentation In, Don’t Bolt It On: Documentation created
   separately from code is less likely to be correct and up to date.
9. Sign Your Work: Craftsmen of an earlier age were proud to sign their
   work. You should be, too.

This is last part of 7 part series.Thanks for reading!