Sign Your Work
Having feedback means knowing when you're done. And when you're done we feel you should sign your work.
Do we mean that you're claiming ownership of your work? No. Are we suggesting that you're signing to say "Look how clever I am"? No. Instead, we're saying that you sign it to say "I did this. I believe it's ready." In fact, we're not necessarily even saying that you should actually add your name to the source file. The value of signing comes from the seconds that elapse before you do it. During these seconds, you're asking yourself "Is this code good enough to sign?" That time of reflection often brings out issues that you go back and fix. If it doesn't, you get to experience a moment of quiet satisfaction, a job well done.
After all, as Pete McBreen says in Software Craftsmanship: The New Imperative (Addison-Wesley, 2001, ISBN 0-201-73386-2), "Software development is meant to be fun. If it isn't, the process is wrong." Find out what's wrong, fix it, and happy programming!
© Copyright 2002, The Pragmatic Programmers, LLC. All Rights Reserved.