Re: Sheer Size

Well... just a suggestion, but try to keep your code as modular as you can, so that it'll be reusable later, and much easier to deal with. Also, make sure you are reusing code whevever you can... other than that... try to think ahead and design your code to be generic at the low levels... I guess my real thrust here is code reuse. Nothing is worse that having code in 20 different places that does nearly the same thing, and then realizing you have to change it all. :)

- Ant
- Some of my best work - Fish Dinner

Comment on Re: Sheer Size

Replies are listed 'Best First'.
Re: Re: Sheer Size by blackjudas (Pilgrim) on Sep 23, 2001 at 01:53 UTC
That goes without saying on any project large or small, all code used is created to be quite modular though I'm sure we've missed a few areas where code is somewhat duplicated, the end result won't have any of those issues (I hope :), though at this point all data access, interface and event handling are done by specific modules the rest is quite specific stuff that belong in their own modules, ie. accounting, and reporting etc.	[reply]

Replies are listed 'Best First'.

Re: Re: Sheer Size
by blackjudas (Pilgrim) on Sep 23, 2001 at 01:53 UTC

That goes without saying on any project large or small, all code used is created to be quite modular though I'm sure we've missed a few areas where code is somewhat duplicated, the end result won't have any of those issues (I hope :), though at this point all data access, interface and event handling are done by specific modules the rest is quite specific stuff that belong in their own modules, ie. accounting, and reporting etc.

[reply]