Pragmatic Programmer Tips for Non-Programmers
I finally got around to reading The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt and David Thomas. While an excellent book for programmers, I believe that it is equally useful for testers (both doing automation and doing manual testing), project managers and technical writers.
In particular, I think many of the traits described in the first section of the book are as valuable (or maybe even more valuable) for non-programmers. The following tips leaped out at me as traits that should be shared by all team members:
Tip 1. Care About Your Craft Tip 2. Think! About Your Work Tip 3. Provide Options, Don’t Make Lame Excuses Tip 4. Don’t Live with Broken Windows Tip 5. Be a Catalyst for Change Tip 8. Invest Regularly in Your Knowledge Portfolio Tip 9. Critically Analyze What You Read and Hear Tip 10. It’s Both What You Say and the Way You Say It Tip 11. DRY – Don’t Repeat Yourself Tip 27. Don’t Assume It – Prove It Tip 46. Test Your Estimates Tip 56. Start When You’re Ready
Some of these tips require explanation. Please see the book for details. It is my belief that if every team member acts in these ways – regardless of position or seniority – then the team will be much better for it.
I agree with your idea…
Even if ones are not engaged in software development in the narrow sense, intellectual labor itself is like software development in the broad sense.