Thanks, and how to move on..

[Andrew Duncan]

<snip>Balance, which I am totally happy with, deleted</snip>

> I hope I've made it very clear -- we're balanced on the sharp edge of a
> razor blade in the breakage area. That's why getting the teamwork right is
> so important. We just can't have people picking at us the way some do on the
> list where we do the work. We can't have a fiction that "Doug is good" and
> "Dave is bad" and be able to solve the problems. Fact is, I'm the one person
> who has been through the process from beginning to now. So for better or
> worse, I'm the guy you're stuck with if you use Frontier. If you give me the
> benefit of the doubt you'll be happy with the result.
>

I can totally sympathise with the breakage issues you have. I suspect that
people who have written a full-blown application will appreciate this most
acutely.

So, I'm only asking that you keep the breakage (if there must be any) to an
absolute minimum. Zero breakage is probably too much to ask, but minimal is
fine.

If there's some way to keep the breakage from happening all at once, so
much the better. I prefer my chaos in sips. :o)

> BTW, I had an idea a few days ago that's worth discussing. We used to have a
> validation suite in Frontier called SuperStress. With various personnel
> changes over the years, this suite has fallen into disrepair. It occurs to
> me that this is somethign Seth, Emmanuel, and many others far too numerous
> to mention (really -- this is our strength as a community -- so many
> excellent smart people) could write stress scripts that we could run to trap
> bugs, and make sure they don't come back.
>

I'd be happy to help out with this, me (us) know how you'd like to work it.

Cheers,
-- 
Andrew Duncan
----------------------------------------------------------------------
voice:    +64 9 623 2926
mobile:     021 297 3174
web:      http://web.webwerks.co.nz/
----------------------------------------------------------------------

Programmers do it while (1)