[MTOS-dev] FYI: r1369: Broke CMS into smaller parts to reduce m...

[Byrne Reese]

I really hope people can see this is an iterative process. I am not sure the
best course of action is to rewrite MT. I think we need to understand
clearly what we want to build towards and then define milestones to reach
that vision for the product.

Rarely in my now 12 years of professional software development has a rewrite
of the codebase ever netted the gain we wanted or anticipated.

This is a step in the right direction though, yes?


On 2/14/08 1:53 PM, "Timothy Appnel" <tim at appnel.com> wrote:

> I was very pleased to see this earlier in my inbox. I won't comment
> much on the code itself other then to say it looks a bit nasty and I
> would have been more impressed if the switch to YAML files would have
> been incorporated here. I'm convinced that YAML files is a much better
> practice then what is found in MT. Since MT's code is reviewed for
> learning it is treated as a best practice guide that needs to be
> better supported.  <tim/>
> 
> On 2/14/08, Byrne Reese <byrne at sixapart.com> wrote:
>> Subcribe to these notifications at:
>>  http://www.sixapart.com/mailman/listinfo/mtos-commits