On Mon, Oct 20, 2008 at 1:35 AM, j o a r <[EMAIL PROTECTED]> wrote: > Some general suggestions for best practices wrt. optimizations: > > 1) Measure first > 2) Implement supposed optimization > 3) Measure to see the impact of the code change > 4) Based on the result of #3, either scrap your changes, or > document the optimized code
And don't forget step 0: 0) Don't even bother A lot of people optimize code that's already plenty fast. A lot of people optimize code that *hasn't even been written yet*. This is foolish. Write your code to be easy to understand and as bug-free as you can get it. And then, only if it's not running as fast as you need it to, should you even start to consider the possibility of thinking about beginning to investigate optimizing the code. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
