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=VHIG6h2hC1oxJCJMHi6Gx18+ob1wS8XBya/mZjJqrNk=;
	b=vtZp3t6zNRrFQBrp6xGlxigs6meOjGUz54la+u7kmO5WAikCbwH84pK3ZZbVjuZyIM
	4WqTwXD6qZgZEh7fDbCeJp/9tIIXGqQvAJl8x438GZ1zihIn4LslWc/GD9C0KXWiJJXj
	s/Kq77kj1ANH+ogrJELrtdr2piLN1cYaGOkU5VEPuJmTDO46p1dDvP3wS+xbPCWW/MX/
	0KErkS5px/+C2T1F4NN4Otg/1GfkiZFnHgaEjowhDzF/QyezhiHyuZJlMkxeY8Snbdvj
	kkofznNRv/SeSos0ZlNOKFkwmtz2t7xLbG04gS9/hHnyTouean5T3re7C/h20uFb4vMv
	eIjw==
MIME-Version:	1.0
X-Received:	by 10.50.61.234 with SMTP id t10mr5263897igr.20.1450728595557;
	Mon, 21 Dec 2015 12:09:55 -0800 (PST)
In-Reply-To:	<20151221030451.02399163eb3e40f21c622c41@gmail.com>
References:	<CAOFvGD6OiYxcGkOiQRVnvXW3TLs42bt7PE5Ot9s09hsukYicKA AT mail DOT gmail DOT com>
	<20151221030451 DOT 02399163eb3e40f21c622c41 AT gmail DOT com>
Date:	Mon, 21 Dec 2015 12:09:55 -0800
Message-ID:	<CAOP4iL1PTdeCZdT+SthHwQtaxC4x06MbBQmxRcK3DZyQ-jfw=Q@mail.gmail.com>
Subject:	Re: [geda-user] Proposing a New Hierarchical Data Structure?
From:	"Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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

--047d7bdc07e29a9cc605276e12b9
Content-Type: text/plain; charset=UTF-8

If you want to create a new structure that actually works then you're going
about it all wrong. You are jumping in making all kinds of assumptions
about infrastructure for using this structure and then piling ideas on top
of assumptions.

Start by stripping away everything that you ever thought you knew about
electronic design and rebuild everything from the ground up. That way you
know exactly what you are building on top of and how it works.


We start with two statements that define our industry.


1) We are in a Design-for-Reuse environment. Everything that we create must
be deliverable to other designers for their use and we need to import
designs from others for our usage.

2) Our designs have grown to the point that they now behave as "Big Data".
Up until now we have all used tools in small data environments. Small data
is very forgiving. You can make all the mistakes in the world and still
manage to muddle through and get a successful design. In Big Data if you do
not follow good engineering practices then you will fail and your failure
will be spectacular.


An example of good engineering practice can be seen with gunsmiths from the
18th century. If you wanted a gun then you went to a gunsmith who would
handcraft the entire weapon for you. Then mechanical engineers developed
interchangeable parts were a gunsmith could produce a single part to a spec
that would work in any gun designed to that same spec. It produced quantum
leap in productivity. I mention this because three centuries later our
electronics industry still has not adopted this technique. You are still
trying to come up with a spec that everyone  can design to.



Start by creating a written definition for our design objects
(components,designs etc). Figure out a naming scheme that prevents
collisions from any other designs from anywhere in the world. Come up with
a packaging scheme to ship objects anywhere or store them in a library or
design environment. Then come up with a database structure for how our
tools will link all of this data together to operate on it.


Until you nail down your foundation it wont do you any good to start off
building on it.


John Eaton

--047d7bdc07e29a9cc605276e12b9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>If you want to create a new structure that actuall=
y works then you&#39;re going about it all wrong. You are jumping in making=
 all kinds of assumptions about infrastructure for using this structure and=
 then piling ideas on top of assumptions.<br><br>Start by stripping away ev=
erything that you ever thought you knew about electronic design and rebuild=
 everything from the ground up. That way you know exactly what you are buil=
ding on top of and how it works.<br><br><br>We start with two statements th=
at define our industry.<br><br><br>1) We are in a Design-for-Reuse environm=
ent. Everything that we create must be deliverable to other designers for t=
heir use and we need to import designs from others for our usage.<br><br>2)=
 Our designs have grown to the point that they now behave as &quot;Big Data=
&quot;. Up until now we have all used tools in small data environments. Sma=
ll data is very forgiving. You can make all the mistakes in the world and s=
till manage to muddle through and get a successful design. In Big Data if y=
ou do not follow good engineering practices then you will fail and your fai=
lure will be spectacular.<br><br><br>An example of good engineering practic=
e can be seen with gunsmiths from the 18th century. If you wanted a gun the=
n you went to a gunsmith who would handcraft the entire weapon for you. The=
n mechanical engineers developed interchangeable parts were a gunsmith coul=
d produce a single part to a spec that would work in any gun designed to th=
at same spec. It produced quantum leap in productivity. I mention this beca=
use three centuries later our electronics industry still has not adopted th=
is technique. You are still trying to come up with a spec that everyone=C2=
=A0 can design to.<br><br><br><br>Start by creating a written definition fo=
r our design objects (components,designs etc). Figure out a naming scheme t=
hat prevents collisions from any other designs from anywhere in the world. =
Come up with a packaging scheme to ship objects anywhere or store them in a=
 library or design environment. Then come up with a database structure for =
how our tools will link all of this data together to operate on it.<br><br>=
<br>Until you nail down your foundation it wont do you any good to start of=
f building on it.<br><br><br>John Eaton<br><br></div>

--047d7bdc07e29a9cc605276e12b9--

- Raw text -