paper on design methodology
	
	factoring

	block design

	dataflow debugging

	time to create vs
	time to debug

	rapid prototyping vs
	rapid troubleshooting

	muralizing

	the cost of self-diagnostics

	the right amount of self-diagnositcs

	the cost of test jigs

	statistical quality control
		checking parameter boundaries rather than parameter spaces
		places where this doesn't work

	apparent complexity
		plain English

	time constants

	sockets

	reuseability

calculus related rate problems

point by point debugging

--------
most popular IC's

1) 7805 5V voltage regulator  7812, 7815
2) 741     operational amplifier
3) 555     timer
4) 7400 TTL

--------
the point of entry

electronics education for kids

audio amplifiers: http://is.gd/4jp7p

analog effects

digital effects

popular circuits


----------

a design grid

power and low frequency signals routed below the plane in the base plug-in grid

RF and high frequency signals routed above the plane.

rectangular topology

---------

LM386 audio amplifier

-------

filters: Maxim tutorial: http://is.gd/4jpv5

------


what if a dataflow diagram could be implemented (transparently) as a digital or analog component.

how could you support this in a simple way?  with wires, boxes, inputs and outputs.

----

what about using FPGA's as function blocks.

interconnecting FPGA's is a purely functional process

hacking their internals is an imperative process, doing whatever is necessary.

For example: implement QSort as a sequence of function blocks.


-----------

implement a simple function block editor where the blocks can be analog or digital

-------------

analog, digital, is there a third, orthogonal rep? as in, neural, using the branch tube branch construct?