In the meantime, “You can call me ‘Commander.’”

So lost me a little on the technical stuff..but I so get the enthusiasm from your post…plus I liked the journey back to the school days..

And Pink and the Brain rocketh majorly!!!!!!

Eh, we shall have said primer. ) We shall. It’s actually easy on the lower levels. It’s just harder to debug rogue code (pun !intended) but not hard to create the code in the first place. As this guy says, low level is easy.

The discipline required to keep programs from ending up too complex is what creates the illusion of difficulty. (One learns it as one goes. The rules are basic. Like “Don’t do too much in one place!” and “Divide the problem and conquer it!” and “Write helper scripts!” and “Don’t repeat yourself!” Et cetera.) It’s not, therefore, the assembly that’s hard, but rather the discipline. My way of approaching assembly has always been to learn it once so that I don’t have to keep knowing it (and exercising such discipline) ; that is, by learning it so that I can write a higher-level program to generate it for me (since programs are always going to be maximally-disciplined). Usually, they are not advanced enough to be called by the correct name: compilers. But if one is doing tiny bots, even this should be unnecessary. We will just kick assembly raw. It is not hard.

I zeroed in on PICS mostly for the price and support factor. They’re insanely cheap these days. And think about it, those “limitations” mean nothing to someone who’s never coded at machine level.

Actually, we should hook up so you can give me a primer on processor architecture. What say you?

And you’re the second person today to tell me Assembly is easy. Maybe I’ve been listening to the wrong crowd!