RE: [tlug] [OT] Good IT Resume

[<burlingk@example.com>]

> -----Original Message-----
> From: tlug-bounces@example.com [mailto:tlug-bounces@example.com On 
> Behalf Of Curt Sampson
> Sent: Thursday, August 02, 2007 12:24 AM
> To: Tokyo Linux Users Group
> Subject: Re: [tlug] [OT] Good IT Resume
> 
> 
> On Wed, 1 Aug 2007, Darren Cook wrote:
> 
> > My opinion, FWIW, is that if you have that many people on the same
> > *codebase* it is time to split it into products/libraries, each with
> > their own small public API, and their own release cycles, 
> and develop
> > each separately.
> 
> In my *experience*, introducing that kind of thing is an excellent
> way to slow down progress, increase code bloat, and prevent the
> development of good frameworks and libraries. It's fantastic at
> inhibiting refactoring.
> 

I am afraid that I have to agree.
I don't have any realdevelopment experience YET, but I have end user experience.  

I have on a number of occasions been frustrated by a package
that was not compatible with a newer version of a library, and
it was hell tracking down the older version.  :P  X11 is the
best example I think.

All it takes is for one set of developers to change directions
and everyone else suddenly has to choose between using what works
with their app as it currently stands, or doing a virtual rewrite
in order to bennefit from the new features of a newer version of
the library in question.

I am not saying that monolythic code blocks are the way
to go.  I am simply saying that splitting everything into
blocks and divying the blocks out is not the "Easy Way,"
or even the "Better Way" in all cases. ^^;

-- 
Ken