One of the problems with OOSE and comments is that to debug an application or just understand it, you have to run in a bunch of different directions at once. This is why a tool like Visual Modeler or Rational Rose is so important, even if you never use it to generate code. That diagram is a lifesaver.

>Again from the XP list, the problem with lengthy and extensive comments, is if they aren't maintained, then they are worse than none at all. Their solution is to keep your methods short, and easy to read, with descriptive names for what they do. Make your objects relate in logical ways (and if they don't refactor). If you get this far then the code becomes somewhat self-documenting. Only really works for OOP'y code though.
>
>At least that's how I understood it.