Makes me wonder what motivated them to continue as well.
I personally learned at 16, so not super young. I guess what motivated me is that I knew nothing about my computer and wanted to better understand how it worked.
1–10 of 29 posts
Makes me wonder what motivated them to continue as well.
I personally learned at 16, so not super young. I guess what motivated me is that I knew nothing about my computer and wanted to better understand how it worked.
I’d wanted to design interactive interfaces since before I even knew what those were. HyperCard, although it’s mostly forgotten today, was nothing short of revolutionary if you wanted to experiment with GUIs in the early 90s and you weren’t already a software engineer.
That’s also what got me interested in automation and personal information management.
This was in the late 80s. I think there was more incentive to learn to code back then because it was the only way to do anything fun. Now it's a much tougher sell
I somehow just liked it. It had MS-DOS. So I learned that. I'm not sure if it had Basic. But it had a manual, and the manual talked about x86 assembly language, and gave examples of how to write programs using the debug command from the command line.
I was hooked. For a while. It was so interesting. I learned about interrupts and how to get the computer to do things. At that age, all I wanted to do was draw pretty colors and lines on the screen -- most of the examples (if I recall correctly) were for "business" apps, like accounting, or database entry.
So I have the hardcore story that I started with assembly at age 10! Haha. But when a 286 arrived, with QBasic on it, I got a book, "Idiots Guide To QBasic" -- that had the same color scheme aesthetic as a Yellowpages, and learned how to draw pretty colors and lines. It was pretty fun. I remember the first modems too, the sound they made, and when 56K was a big thing. I think there was a 14.4K at some point too :)
What motivated me to contine? I don't know--it was just interesting. I just found it fun. Making stuff. Come alive. On the screen. It was pretty fucking cool
To me code is magical; Even the small things like seeing a button click change something, or even seeing LED's light up in the way you programmed them, it's magic!
What motivated me is to build things. Quite uniquely to code is that you can build amazing products with very limited resources, the possibilities are endless. If you have a computer you can build. I always wanted to build stuff.
Now at 29 it is still what motivates me, I still enjoy building things, seeing something come to life that I designed and built still gives me so much fulfilment and joy. Seeing (quite a few) people actually use the things I build and getting value out of them is even better.
I also do a lot of product management type work atm, but the times I actually get to design & build stuff I realize how much I enjoy creating things. Code is such a great tool.
I also still appreciate the magic of code, now mostly in animations, transitions and well designed and programmed apps and interactions.
At school I searched (I believe it was on yahoo) "how to become a hacker"
The result that came back was Eric S. Raymond's post with that title. He actually keeps it up to date.
The older version was a little more vitriolic but it really hasn't changed that much otherwise. It's full of lots of fun hacker culture stuff. Encouraging curiosity, talking about the history of the word "hacker", vaugely anti-authority at every turn.
It doesn't shy away from the technical either. It had extremely practical advice like learn http, tcp/ip, python, Linux, and all kinds of stuff like that.
I had never run across anything like that before and I was instantly hooked by everything about it and started messing around with programming languages among other things outlined in the guide.
I followed it like an instruction manual and of course made up my own syllubus too as I went along.
Fond memories.
Got my first computer (Atari 1200XL) a little after a friend got an Apple ][. We learned by typing in games from books and magazines and modifying them.
I sold my first program around age 11 for $20. It was 6502 assembly subroutine to calculate an XMODEM checksum for a BBS. They had BASIC code that worked okay for a 300 baud modem, but took too long to calculate the checksum for 1200 baud modems. That was hand assembled from op codes in a book and represented almost $1/byte of object code. (Imagine if we got paid that much now. :) )
I (mistakenly) thought I was pretty good until I showed up at college and couldn’t breeze through an intro level actual programming class, so “starting at 7” didn’t really mean that much in terms of my professional career.