Would it be better if we used Javadoc to print out program documentation?
No, it wouldn’t. Focus on keeping the code clean and clear will pay off far more than commenting it and printing the comments. Working in pairs will communicate the details of the code far more effectively than Javadoc ever can. Now don’t get me wrong (again). You may well need some nicely formatted UML for your project, or you may need to print out Javadoc when you distribute your code to other users, or you may need to document the requirements for management or as part of a contract. If and when you really need these things, then by all means you should do them. But inside your collocated Whole Team, you most probably will not need them, because the information you need will be communicated through the more effective medium of conversation. It’s important, as early in an XP project as possible, that the Whole Team learn how effective these “low-tech, high-touch” mechanisms are. Therefore, we encourage newcomers to XP to stick to these basics until they’re intimately familiar with ho
