3 ms·
His 'ineffective fumbling' and 'high school' seem to mirror my experiences. Using a bunch of mismatched books and computers with no real goals, no mentor, and n
by bluedino 9y ago
His 'ineffective fumbling' and 'high school' seem to mirror my experiences. Using a bunch of mismatched books and computers with no real goals, no mentor, and no real results.
However, it's amazing when you read about <insert famous programmer>. They grew up with Apple II's and Commodore 64's, but they mastered them. Or at least that's the narrative from the author of the articles that talk about them.
They don't just write silly BASIC programs like the rest of us, they started using assembler and learn the machine like the back of their hand. They learn how to optimize the living crap out of their code. Maybe their schools just had better books in their libraries or they subscribed to the good magazines of the day. Or they were just that much better at programming and smarter and more focused, one of the above, or all three.
- deleted 9y ago[deleted]
- yodsanklai 9y agoI grew up with a Commodore 64 and then an Amiga 500. What I remember is that I had few books and a lot of time to study them. Moreover, these were much simpler computers than what we have today. Kids could understand a lot of the hardware and the assembler by themselves. On the other hand, It was harder to learn about algorithms and data structures. I didn't have access to the adequate instruction before college.
- nurettin 9y agoInstead of switching to Amiga, I decided to defend my C=64 against the Amiga kids in the block by being amazing at it. That gave me an advantage in my early programming career because it taught me the discipline of persistence. I knew that bugs were solveable and existing code wasn't daunting.
- seanmcdirmid 9y agoI learned programming on Trash 80s in an underfunded Mississippi High School (well, I learned some BASIC earlier). I never got interested enough to learn assembler until college, but it was enough to set me on my way.
- 8note 9y agomaybe it's vision more than anything. you've got a thing you want to make, but you get stuck along the way. it's too slow, or doesn't fit in memory, so you have to figure out how to optimize what you've got before you can keep building.
- jacobolus 9y agoI think it depends on getting access to enough mentor guidance and/or stumbling over the right initial materials and tools (simple enough compiler/interpreter, some books/magazines, ...). In the WWW era this is in some ways getting easier than it used to be. Kids don’t necessarily know where to look, and it’s easy to get very stuck or discouraged if the learning curve is too steep to get something simple working within a reasonable amount of time.
- tluyben2 9y agoI learned electronics before computers (my father was an electronics engineer at the time) and I was more or less taught Turing (intuitively) on a hardware level. So the idea that anything is possible and their is no such thing as magic when it comes to computers (modern ones included) made me keep trying because I knew it had to be possible on the gate level so it was just a matter of trying. When I still had an Msx, my friends where getting Amigas with much better capabilities. I knew that, basically, my computer could do the same: by that time I was well aware of math and algorithms, so I was able to code up ‘real 3d’ but it was so slow that my poor system had to stand there all night to calculate a rotating cube and put it into screen 5 buffers. Now that is all silly stuff, however, it did make me remember my whole carreer that there is no magic. Something which some people who learn high level only, do not seem to have. They actually seem to believe that the provided abstraction (by libraries or language) is the limit to working the machine.
- sillysaurus3 9y agoEh. I wrote a quake-like engine at 17. But that cuts out the 4 years of fumbling that it took to get to that point. There's probably a lot of fumbling common to all computer users in their early days. But what separates people is how far you can go in a short time.
- tluyben2 9y agoThe timeline seems to match my experience, but the fumbling does not; I started reading books and magazines before I had access to computers in begin 80s. Those where mostly Basic but some asm (esp for the c64 and spectrum the basic code had fair amounts of data which was asm). When I had access to computers after that, I wrote monsters of Basic programs. I remember writing a music composition program for the MSX which, after I got it all typed in on a PC (I had only partly access to an MSX and part PC), it was too large for the MSX memory. It was too slow too, so I started replacing parts with z80 asm typed in hex. I still remember most opcodes in hex: it was much faster and more efficient to type than assembler. I guess I was lucky to have access to the books: I went to a (monthly?) Philips ‘old crap’ sale. If I remember it was in the bottom of the PSV stadium and they had old electronics and mags and books for sale for cheap. It was so lovely; we took a car full of old circuitboards to get components off, books, printed papers etc home and spent the next month working on them (this was summervacation usually as it was close to my grandparents).
- jacobush 9y agoSounds like heaven
- djaychela 9y agoI didn't really get past the 'ineffective fumbling', alas. Got good at BASIC programming on the ZX Spectrum, and read that (I think) Matthew Smith learned Assembly by reading 'Programming the Z80' by Zaks. So I got that for Christmas one year, and got totally drowned by it; had three concerted attempts to understand it, and while I had some idea, it wasn't enough to get going. Decided I was an idiot, and pretty much gave up. Here I am, 30+ years later, spending a couple of years trying to learn programming properly having been made redundant from 2 jobs... I don't think I'm an idiot, but I think it's a combination of others being smarter than me and more attuned to the task in hand, but also there's an element of luck to it. I think if some of the cards fall slightly differently and the things you try happen to work (mostly skill, but with an element of luck), you can get drawn into it, gain some resilience and make progress. If you stumble too much before you make real progress you can think you're stupid and give up. Have a similar parallel experience with playing the guitar (which is how I've mostly earned my living in the intervening years) - an element of picking technique which I didn't manage to work out in the 80s when I was learning and again put it down to my own inability; now with better resources and research in the current era, found out what the 'missing part' of the jigsaw was, and realise that if I had found it (I was close, but no cigar) then things could have been drastically different. Fortunately it happened at a playing level which was already beyond 'give up, you're useless'!
- geebee 9y agoI’ve wondered about this. I was keenly interested in programming as a kid, but I was never into hardware or operating systems. I wanted to write text based d&d style games, as well as simulate outcomes from dice games like risk (or know the odds of one character defeating a monster). Those are real programs, but looking back, I actually do think this might contain a seed of why I never did become as strong a programmer as my peers from those days. I floated away fr programming, got into writing and music, floated back in. Some of my peers from those days couldn’t take their eyes off computers, it was a deep fascination. There are lots of good ways to be a programmer. But the real experts do seem to have a deeper fascination with the inner core, the hardware, machine code, actual design of programming languages (debates about ruby vs python or similar almost always go beyond my depth, I just like how ruby looks on the page. I just like how quickly I can get my answer in python).
- deleted 9y ago[deleted]