X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Js0XdzK5VYkH9FVzvzez9tWMheiGugOGvee/8hVd0/0=; b=mZYhgS7hhwDQutFosanoJOSSRJY7ZOBj9YpM7vESwXPLD9KEXzP+POlCdFUSUoZ9IS 9SYNnwGxK2k0cxZrh9C0a1QhpXgi7YczE3FDFsH+Jd2Y24MefCjcLZSU2OAgFSTrtxS0 IDw2wt+tg5HP5hQ7hPNVb/2hOnhy6Pu7ENmGeU4/TEaQt5y8o5d+Og1mXqL4PMZnbvJM vw3ciFbx+1a4TegJoqzJpMZ7uvnSaJlEC77HLhkvg89NqOP3vrDCHvWUhwe9EDiOnejt U6O8zPWDpc0aimFcIwnmSo9wYAxsmM+srSh5so6NYzHC58nR+GTlDUtsSAlU5VU8tDAl oMmQ== MIME-Version: 1.0 X-Received: by 10.50.79.230 with SMTP id m6mr7116061igx.86.1441375363642; Fri, 04 Sep 2015 07:02:43 -0700 (PDT) In-Reply-To: <55E94605.4060604@xs4all.nl> References:

<55E94605 DOT 4060604 AT xs4all DOT nl> Date: Fri, 4 Sep 2015 07:02:43 -0700 Message-ID: Subject: Re: [geda-user] Interesting blog post from a commercial EDA vendor - pdf From: "Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=089e01229aaa89df5e051eec5a4a Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --089e01229aaa89df5e051eec5a4a Content-Type: text/plain; charset=UTF-8 On Fri, Sep 4, 2015 at 12:19 AM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com] wrote: > > I have a couple of gigabytes of datasheets lingering in a Network Archive > Storage as well ;-) > > All sorted by vendor and part ID. > > And some (most) are old revisions, so called "uncontrolled copies". > > > Kind regards, > > Bert Timmerman. > > The number one rule for effective design-for-reuse is to NEVER copy data in a database. Everything is assigned to one particular location and any one who needs that data gets it from that location. If you start making copies and passing them along then you lose the link back to the original designer. Bug fixes get passed down stream but are never passed up stream to be passed on to all the users. The design starts to fragment and go viral. Eventually someone tries to build a design using components with two slightly different variants of a component and you have a train wreck. John Eaton --089e01229aaa89df5e051eec5a4a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Fri, Sep 4, 2015 at 12:19 AM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT c= om> wrote:

I have a couple of gigabytes of datasheets lingering in a Network Archive S= torage as well ;-)

All sorted by vendor and part ID.

And some (most) are old revisions, so called "uncontrolled copies"= ;.

Kind regards,

Bert Timmerman.

The number one rule= for effective design-for-reuse is to NEVER copy data in a database. Everyt= hing is assigned to one particular location and

any one who needs that data gets it from that location. If you sta= rt making copies and passing them along then you lose the link back to the<= br>

original designer. Bug fixes get passed= down stream but are never passed up stream to be passed on to all the user= s. The design starts to

fragment and g= o viral.

Eventually someone tries = to build a design using components with two slightly different variants of = a component and you have a train wreck.

John Eaton

--089e01229aaa89df5e051eec5a4a--