Life is like a box of chocolates... you never know which one will be slow :)
On Aug 12, 2010, at 5:06 PM, Mark Ritchie wrote:
> On 12/Aug/2010, at 11:43 AM, Ken Anderson wrote:
>> 3. If something is slow, figure out how to make it faster AFTER it already
>> works right
>
> Run slow case, MEAS
On 12/Aug/2010, at 11:43 AM, Ken Anderson wrote:
> 3. If something is slow, figure out how to make it faster AFTER it already
> works right
Run slow case, MEASURE, change, MEASURE again, keep or reject change.
Repeat until end of budget (time, money, space, whatever. ;-)
Notice that I didn't imp
Follow the golden software development rule:
1. Make it work
2. Make it work right
3. If something is slow, figure out how to make it faster AFTER it already
works right
Ken
On Aug 12, 2010, at 2:32 PM, Chuck Hill wrote:
> My vote: listen to Dave. Quick and Dirty usually ends up Slow and E
My vote: listen to Dave. Quick and Dirty usually ends up Slow and Expensive
and Dirty.
Chuck
On Aug 12, 2010, at 11:27 AM, Steve Peery wrote:
> You are probably right. I too have paid for trying to "make it more
> efficient" many times in my coding career.
>
> Steve
>
> On Aug 12, 2010, at
You are probably right. I too have paid for trying to "make it more efficient"
many times in my coding career.
Steve
On Aug 12, 2010, at 2:13 PM, David LeBer wrote:
>
> On 2010-08-12, at 2:05 PM, Steve Peery wrote:
>
>> I have an EO object that I want to have a to many relationship to a Strin
On 2010-08-12, at 2:05 PM, Steve Peery wrote:
> I have an EO object that I want to have a to many relationship to a String
> object. I could create an EO object to hold the string and do a standard to
> many relationship but it seems wasteful. Is there a better way?
>
> Steve
I will preface t
I have an EO object that I want to have a to many relationship to a String
object. I could create an EO object to hold the string and do a standard to
many relationship but it seems wasteful. Is there a better way?
Steve
___
Do not post admin requests
