On Thu, Dec 06, 2001 at 04:13:51PM +0000, Timm Murray wrote: > > Arrrgh. This is silly. > > > > The cycle is > > > > Design > > Implement > > Test > > > > Rinse and repeat. > > No, that's what they teach you in pea-brained CS classes. >
Well, I never had a CS class. But you tell me how logical it is to say "I can't state the hypothesis until I design and run the experiment" Coding is a mechanical process. It *is* the translation of a design into a specific implementation. The only question is at what level the iteration happens, and whether or not you wish to collaborate with others in the process. If you are working by yourself, the iteration can be very fine grained, with the code being the design documentation, and the design evolving with every line of code you write. This will scale reasonably well to two people, it's called 'pair programming'. With a bigger project where you want to harness the capabilites of a group of people, you need to take the design to a higher level of abstraction, so you can parcel out the grunt work. Note that this has nothing to do with whether or not you think the design will work, or is valid. Nothing at all. David Schutt _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
