[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Repository services and budget



Dave,

davidk@isi.edu wrote:
> 
> Jeff,
> 
> > Jeff Williams writes :
> > >
> > > I support the idea to keep everything as lean as feasible. But I don't
> > > think that it is a good idea to save the money on personnel. I found from
> > > my experience with running the RIPE database that it was of tremendous
> > > value to have a 'secretarial-type/catch all' person in the office
> > > (parttime is fine). Good personnel can save you more money by choosing a
> > > cheap location (if that is needed at all ;-)) and reliable but cheap
> > > computer equipment.

  I did not write this.  (Above).
> >
> >   I have found that reliable and cheap rarely go together.  In this
> 
> I didn't say the cheapest equipment. I put an extra condition there, it
> should still be reliable. Also, good personnel is supposed to know were
> to shop cheaply; you know: not every shop sells the same equipment for
> the same price. And then in general: reliability is more determined by a
> solid software design, implementation and good hardware maintenance team
> then the underlying hardware itself (on the assumption that you did at
> least some minimal quality checks) eg. get could implementors *and* they
> are rarely cheap ...

  You are so right!  Good implimentors are rarely cheap.  And cheap ones
are not worth anything by themselvs.  I frequently use the buddy system
in this area.  One good implimenter and one that is learning.  That way
I get a better implimenter over the long haul and save a little in the 
process.  This might be a approach to consider here as well.
> 
> David K.
> ---

Regards,
-- 
Jeffrey A. Williams
DIR. Internet Network Eng/SR. Java Development Eng.
Information Eng. Group. 
Phone :972-447-1878
E-Mail jwkckid1@ix.netcom.com