[thelist] What's a Programmer To Do?

[Martin Burns]

On 6 Apr 2009, at 20:39, Jack Timmons wrote:

> On Mon, Apr 6, 2009 at 9:30 AM, Luther, Ron  wrote:
>
>> I think you're on the right track, but I think it's simpler than  
>> that.
>>
>> I think it's more:
>> * Clients really, really, really hate lock-in.
>> * Except for the ones who haven't yet learned how much they hate it.
>
>
> That's a more succinct and apt explanation. I just don't want to  
> imply that
> by -not- using a framework you're using a disservice, though,  
> because that's
> not always true.


Agreed, but the generality is that
1) Most business needs are pretty common therefore
2) Most business needs can be met through existing functionality, with  
a small amount of customisation therefore
3) Implementing customisation requires fewer function points than the  
full solution, therefore
4) Can be achieved faster.
5) Given that costs are generally closely related to time, the quicker  
solution will generally be the cheaper.

So, if you've got a good reason to custom code, then fine, persuade me  
of that fact. But default will be otherwise.

Cheers
Martin

--
 > Spammers: Send me email -> yumyum at easyweb.co.uk to train my filter
 > http://dspam.nuclearelephant.com/