> With me, it is not an issue of looking down at the documentation, but simply > that I don't know for sure how I want it until I have attempted to implement > it. Put it down to lack of experience or whatever, but despite what every > teacher and book will tell you, I feel much more comfortable implementing > first, and specing afterwards.
If that's what you're comfortable with, I can't argue. I generally do both side-by-side, because each one tends to bring out problems in the other. I just wanted to report on why the spec and the code don't match very well. That's pretty typical of an open-source projects where there are good coders and good documentors, and no real "management" to keep the two in sync. -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lcrocker.html> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
