It's more important to worry about correctness than efficiency. Read Premature optimization for more explanation about this.
I've found that developers who constantly worry about whether or not something is fast enough tend to keep tweaking rather than developing. That's a bad thing. Once you get it working properly, you may very well discover that your application is fine. Remember: if it's fast enough for the customer, it's fast enough.
That's not to say you should never worry about performance up front. If you have a known systemic performance issue (manipulating 3-D graphics, for example), then this is appropriate to consider. Otherwise, pretend that speed's not important until you're close to finishing the app and you have a better opportunity to find out what, if anything, is really causing performance issues.
Cheers,
Ovid
New address of my CGI Course.
Silence is Evil (feel free to copy and distribute widely - note copyright text)
In reply to Re: Module Efficiency
by Ovid
in thread Module Efficiency
by Coplan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |