There's more than one way to do things | |
PerlMonks |
Re^4: As Efficient as Possibleby roboticus (Chancellor) |
on Apr 03, 2010 at 00:38 UTC ( [id://832582]=note: print w/replies, xml ) | Need Help?? |
mr_p: but, I still need my code to be as fast as possible. No, you really don't. You need it to be fast enough. You can spend incredible amounts of time and energy making things faster, prettier, more elegant, etc. There's no shortage of time sinks (aka rabbit holes) in our profession. If your requirements document tells you to "make it as fast as possible", you need to do one of:
Remember, a requirement is testable. A requirement that "it be as fast as possible" isn't a requirement--you can't tell when you've achieved it. A requirement that says "the system must return a response within 500 ms over 90% of the time" is a fine requirement. It's testable, and you'll know when it's time to move to the next item on your to-do list. </learned_from_experience> ...roboticus
In Section
Seekers of Perl Wisdom
|
|