David Hutto smokefloat at gmail.com
Sat Oct 9 20:30:02 CEST 2010

On Sat, Oct 9, 2010 at 2:23 PM, David Hutto <smokefloat at gmail.com> wrote:
> On Sat, Oct 9, 2010 at 1:58 PM, Alan Gauld <alan.gauld at btinternet.com> wrote:
>> "David Hutto" <smokefloat at gmail.com> wrote
>>>> should learn to program in assembler (or even microcode) then move
>>>> to C and then to Python(or similar) and finally to 4G languages.
>>> Even old schooler though would be that we're just directing electrical
>>> flow from an ac outlet through a dc converter and streaming it through
>>> the circuit board though. Which is not as easy as it sounds!
>> Yeah, but I don't think anyone would claim that was programming! :-)
>> Although I did first learn my boolean logic by having to translate
>> it into switch circuits - real mechanical toggle switches not
>> electonics...
>> AND => two switches in series
>> OR = two switches in parallel
>> NOT = an "off" switch - ie. on by default
>> etc/...
>> We then moved to relays and finally diodes and resistors...
>> But that was training us in electronics not programming.
> How can you distinguish the two, once learned though? I don't know C
> but I do know python, and the what's below the BIOS(muy basically).

Not How, but maybe , more importantly, why? To avoid the low-level
programming confusion, or for more control over user gui's(Meaning
client wants)?

>> Alan G.
>> _______________________________________________
>> Tutor maillist  -  Tutor at python.org
>> To unsubscribe or change subscription options:
>> http://mail.python.org/mailman/listinfo/tutor

More information about the Tutor mailing list