13 ms·
I think I accidentally got a good order because of the ad hoc learning I did as a child. I first encountered Commodore/Apple II/IBM through text-mode games/Word
by pessimizer 4y ago
I think I accidentally got a good order because of the ad hoc learning I did as a child. I first encountered Commodore/Apple II/IBM through text-mode games/Wordperfect/typing programs in from magazines, then > learned C which gave me an idea of how they worked > learned microcontrollers then understood how the keyboard and monitor worked and how to drive things like that > then logic, electronics and transistors to figure out how microcontrollers worked (and how to make sense of digital voltages) > finally the D-latch.
I do have to admit I had a multiuser OS sized hole for a while. The computers in my head were Harvard architecture RISC, generally programmed in assembly, and were driving pin voltages. But it was close enough.
So an accidental process of being introduced to things as black boxes, then opening the black boxes. Still linear, but backwards. Needless to say, I loved Code when it came out and gave away at least four copies. I would tell people who thought I knew a lot about computers "this book contains pretty much everything I know about computers."
I actually think computing lends itself well to that because it is built in layers. You can talk about how a layer behaves before talking about how it was made to behave that way. The problem I think people run into is that some come to think lower levels of abstraction are a waste of time from a combination of pragmatism ("I don't care how it works") and sour-grapesism ("I don't know how it works so it doesn't matter.")