Agreed, but then they're probably aware of the situation and have made plans
to mitigate if they're going to be attending TC140.

On Mon, Sep 21, 2009 at 14:52, Caliban Darklock <cdarkl...@gmail.com> wrote:

>
> On Mon, Sep 21, 2009 at 1:42 PM, JDG <ghil...@gmail.com> wrote:
> >
> > Why wouldn't said developer partners have updated their code 2 weeks ago
> > when this was announced?
>
> Three reasons.
>
> A. Irresponsibility. Paying no attention to anything, they have no
> clue this is happening and indeed will not even find out what's going
> on until after it happens.
>
> B. Laziness. Knowing it is easier to fix something that has broken
> than predict where something is going to break, they voluntarily
> decided to let their application break and fix it then.
>
> C. Discipline. Having already fixed everything they thought was going
> to break, they are standing by to make sure they didn't miss anything.
>
> Contrary to popular belief, option B is not necessarily bad. We'd all
> prefer option C, and option A is clearly the Wrong Thing, but option B
> is actually a smart response to some business conditions.
>



-- 
Internets. Serious business.

Reply via email to