[MTOS-dev] RSS Support

[Jay Allen]

On May 2, 2008, at 5:34 PM, Bud Gibson wrote:
>
> My ONLY recommendation would be to write tests first such that they  
> serve as the spec. All new functionality is defined by tests.  
> Nothing goes out the door without passing all the tests.

While I *completely* agree with the last sentence, I sure hope that  
**the product specs** serve as the specs.  I kid but one thing I look  
forward to is the day when all of the specs and release features for  
MTOS are determined out in the open.  Without that (among other high  
ticket items), it's hard to say "MTOS" without a bit of detecting a  
bit of lingering irony.

> The rub starts to come when you decide to radically re-architect a  
> product, basically what happened between MT3 and 4.  At that stage,  
> you're potentially rewriting the contract (test suite) for important  
> elements of the app.

Exactly.  And while they are doing some pretty incredible work they  
are also incredibly *overworked* right now.  Seems to me like this  
would be a good place for MTOS devs to help, no?

> I guess my main hope is that the test suite gets a central enough  
> role during this relatively stable period post MT4 release, that  
> breakage caused by new releases will be minimal or non-existent. All  
> things point to this being the case.

Agreed.

--
Jay Allen
Endevver Consulting
415-200-6985