A pristine book is a book that has not been read. That is my motto. Unfortunatly, some other people do not get it. If you need your books perfect, don't read them. They can look nice on a shelf and take up space. However, I do not believe that books should be used that way. I care about one thing and one thing only when I get books, that is the contents of the book.
One of our developers was complaining that her book had food all over it. I do not notice or care that books are not perfect. I do not get distracted by pencil marks, doodles, crumbs, fingerprints, blood smears etc on a book. In fact I like the fact that it feels well used and worn, Some how it gets me more involved in the material. When a book is perfect, it feels like it is a harder book to comprehend with more difficult material that no one has understood before. When it is old and worn out, it feels like territory other people have gone through, so I can always ask some one else about the material if I do not understand it. Also, the more I read a book and practice with it, the better I understand the text. That is probably why I always feel more comfortable with old books rather than new ones. The other nasty thing about new books is they are more likely to lead to paper cuts if you are not careful. Certain kinds of paper is worse at this than others, and not that the book has particularly sharp paper, but I have learned that I have to be careful with paper because it could hurt me.
What does this have to do with wograld project development? I realized that we did not know what version of the game we were using. Our lead developer said he fixed it so the crash bugs are gone, and it seems to work fine on my machine. However on our other developers Solaris system, the thing crashes just like it used to, not the same crash bug actually though, because it doesn't get as far as loading the maps that were not finished. It doesn't even get to scorn. Just walk a few feet and the whole thing crashes. I realize that we need some way to keep track of different version of the game, and using tags in CVS seems to be the way to go. I brought up subversion and how people think it is better, but that would require either waiting for the book or reading the pdf files, neither of the other people on the project are particularly interested in version control. It just seems like a nessesary evil. The thing is how to use it effectively, something I don't feel that we are doing.
I read that some newbie developer on some other project team messed up the CVS. I hope we don't end up having that problem. Then again, I feel if someone does not want to learn version control, they should not be working on a project, because it is something that has to be done.
