in reply to How do you program (again)?

Divide the program into discrete sections, then figure out what functionality (modules and/or subs) you'll need for each section. Design all necessary subs and perform proper testing; put together the sections and perform testing on these as well. Small programs can be thrown together willy-nilly, but larger programs will require several layers of coding and testing if you don't want to get into a terrible muddle.

Replies are listed 'Best First'.
Re^2: How do you program (again)?
by wazoox (Prior) on Jun 03, 2005 at 20:16 UTC
    Well I am in muddle, because I didn't take the time to really make the things just "right". However I test each new small code block (using small test scripts) while I write it, and I check that it pass perl -c every 5 seconds, and I stop to test the code I just wrote after 20 minutes max -- so it's not that bad actually; it pretty much works, but the apps I'm working on are very complex, multi-process (with possible deadlocks...) data management systems...
    So now that I'm about to close a project and while I'm already working on the next one (this one very late too, of course :) I'm trying to meditate about it to make it much better than the previous one :)