Re: Summary of the situation with the composition process — thoughts wanted

John Hopkins jhopkins at
Thu Jun 23 22:49:44 UTC 2011

On 11-06-22 06:01 PM, Ehsan Akhgari wrote:
> On Tue, Jun 21, 2011 at 6:10 PM, Kent James<kent at>  wrote:
>> On 6/21/2011 2:36 PM, Ehsan Akhgari wrote:
>>> Implementation constraints should not really dictate the
>>> features of a product.
>> Welcome to the TB world of very limited resources. If we do not consider
>> implementation constraints, certain things would not get done. My New
>> Account Types (SkinkGlue) discussion was a good example, where I had a less
>> than perfect but available solution, and by the time we had everyone say
>> what the ideal feature set would be, there was no reasonable chance it would
>> get implemented.
>> Sometimes the best is the enemy of the good. Don't know if that applies to
>> composer or not.
>> That is all true, but we should also make sure not to dig ourselves
>> into a hole which we can't escape from later on.
With a faster release cycle, doing incremental, "XP style" releases 
makes a lot of sense to me.  Conversely, there's the "a large chasm 
can't be leapt across in several small jumps" argument.  Depends on the 


More information about the tb-planning mailing list