Re: Coding goals / requirements.
From: Gavin Beau Baumanis <gavinb_at_thespidernet.com>
Date: Tue, 18 Jan 2011 12:56:28 +1100
I'm pretty sure the context of the quote is along the lines of;
Poor design and implementation proves to be a burden in terms of maintenance costs, in the long run.
I guess it is an implementation / coding practice question;
Especially in an OSS project where resources are lean and transient, it is "my" (perhaps naive) view that spending x hours on writing an API that might not ever be used by another consumer is in fact x hours wasted that could have been spent on a more worthwhile task.
From my past experiences, I have created many an API that have never-ever been used, purely because the design standard said an API was required, though the engineering requirements of satisfying the task at hand negated that requirement entirely.
Again - I don't presume to know any better - and in fact I started the thread because of a desire to hopefully learn from it,
On 18/01/2011, at 9:13 AM, Branko Čibej wrote:
> On 17.01.2011 23:07, Gavin Beau Baumanis wrote:
This is an archived mail posted to the Subversion Dev mailing list.