[Rails] Re: Re: Best way to handle multiple tables to replace one bi

Colin Law wrote:
> On 25 April 2010 00:45, Mike P. <lists@ruby-forum.com> wrote:
>>...
>> I think if people could just get over the "don't optimize too early"
>> mantra, and realize that this can't possibly be best move for everyone,
>> a lot of future stress could be avoided, for both the business owner and
>> the customer.
>
> Optimising "too early" is a bad thing by definition. If it was a good
> thing then it would not be "too early".

Exactly. You're trying to justify a bad idea, but it's still a bad
idea.

No one is saying that you shouldn't do research on possible future
optimizations. But don't implement them until you know where your
performance problems *are*, not where you assume they'll be.

"Premature optimization is the root of all evil." --Donald Knuth

>
> Colin

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
marnen@marnen.org
--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.