>> This is not the case with a lot of the
'toy' programming languages
>> and environments where you do have to re-learn things when you move
>> on to other languages and systems.
> Yes and no. [...]
Jsut as nobody tried ot learn the entire
vocabularly of a human
language at the start :-)
Not quite, but a few kids come remarkably close. There are some who
don't go through the usual babbling stage and remain silent for longer
I doubt that anybody knows the entire vocabulary of any living human
language.
Case in point. Compare the classic Philips
'EE' series of kits with
'Snap Circuits'. [...]
The later Philips EE kits included a circuit for
an FM radio
receiver. You got to wind the tunig coils, they were resoianted with
a varicap diode, etc. You got to understnad how such sets owrk. The
Snap Circutis one seems to consist of an 'FM radio module', an 'Audio
Amplifier module', a speacker, and not much else.
Now, if I might take a bit of a devil's-advocate position for a moment,
in what essential way does this differ from building something out of
74xx TTL? You have the "AND gate" module, the "XOR gate" module, the
In a sense it isn't. I guess it's a matter of degree...
For example, let's conisder 'buildign a computer'
You might start from various ores dug out of the groudn and refine your
own materials.
You might start with metals, etc and make your own electronci components.
Copper oxide transsitors, albeit poor performers, can certainyl eb made
at home. So can point-contact germanium transsitors if you have sutiable
germanium crystals.
I know of nobody who has made a computer startign there, though.
You might start from simple electronic components, discrete transistors
only. Peophe have certainly done that. You would prboably start by
designing and building flip-flop and gate circuits that could easily be
reproduced, and use those as the basis for your computer design
You might start with SSI and MSI ICs (TTL)
You might use an LSI procesosr (a microprocesosr)
You night bolt a ready-made moterhboard into a case, plug in the PSU
cables, the hard disk, some memory modules, etc.
To me, the last is not 'building a computer', it's 'assembling a
computer'. All the others do count as building one to me.
But if you claimed ot have 'made a processor', I don;t think that
soldering a Z80 onot a bit of stripboard is wqutie ewhat is normally
meant by that. To 'make a processor' you need to start with something
simpler than the processor.
And I guess that's how Ifeel about 'buidling a radio' by connecing an
RF/detector moduel to an audio amplifier module. The parts are too high
level.
The other thing is tghat TTL devices are somethign that are/were gernally
used. There are excellent databooks for the giving intenral scehatmics
for the simpler devices. But the FM radio module you find in an
electronics kit is not something you will come across elsewhere.
"J/K flipflop" module, etc. Yes, you can
build complex things with
them, but you can also build simple things, on the order of the
three-module radio you sketch - and I daresay you can build complex
things with Snap Circuits, too; while I am not familiar with them, I
have trouble imagining anything that provides an "audio amplifier"
module that you can't use to build interesting oscillators and such by
pasting them together with feedback, gain control, phase shift and
suchlike.
It's probably possible to do things like this, but there are no clues as
to how to go about it, and the modules are not that well docuemtned. A
true hacker can peroblaby do it, but the kits are not aimed at such people.
Indeed, I've been playing with ICs for at least thirty years, and it's
only in the last month or two that I finally understood how op-amps get
It ias _amazing_ how few prople truely understnad the 555 timer IC.
a differential amplifier out of a long-tailed pair, or
why/how a BJT
current mirror works. Have I been committing some heinous sin by using
them all this time without understanding how they work? If not, why is
it any worse to build stuff out of those Snap Circuits you mentioned?
IMHO there is a differnece between learnign and using (yes,this might
partly contradict my idea of not learnign things you have ot unlearn,
it's more that ymay have to learn thigns you don;'t actually use). There
is probalby nothign wrong with using an op-amp as a black box. Until,
that is, you tun into problems fro mthe input current, or the slight
offset, or... Or you end up using many mode components than you have to
becuase you don;'t realise you cna use a particualr IC in a different way.
And aexample of that. The 7474 Dtype flip-flop has acrtive-low direct set
and dirct clear inputs. They work like an SR flip-flop. And the behaviour
if both are asserted at the same time is docuemtned. Both ! and Q/ go high
at the same time. This condition is not latched, if either set or rest
goes high and the other remains low, the flip-fliop does what you'd
expect. What this means is that if you tie reset low (say, then Q/ is
high. But Q will be the inverse of the set input. It has rather more of a
porpaction delay than a 7409, but I once used this when I have half a
7474 unused, not other gates fee, and I needed ot invert a slow-ish
signal. A lot of people would have fitted anotehr IC.
Reminder: I said this was a devil's-advocate position. While I agree
with you, I don't understand why. Perhaps I could put it this way: I'd
I beleive it is impossible to be totally consistent. And to understand
why you reson the way you do.
Part of it is 'gut feeling; To me, here, it's the idea that at least when
learning you should use thigns considerablly simpler than the device you
are making And that you should, if at all possible, learn with real
components that you will come across later.
I also feel that if you are nto careful, just plugging modules together
(which includes things like Arduino boards), although economically
sensible in that it cuts development tiem and production coses, can end
up with an over-complex and less reliable device. If yopu are elarning
you should elaern how to start from first principles.
-tony