←back to thread

377 points porterde | 1 comments | | HN request time: 0.217s | source
Show context
makmanalp ◴[] No.42142286[source]
Oh my GOD I have to comment. This is how I learned to program as a kid.

I found a copy of "Write Your Own Adventure Programs" (1983 - Usborne: https://colorcomputerarchive.com/repo/Documents/Books/Write%...) as a kid in my primary school's bookshelf. I remember the code was written in BASIC and my family didn't really own a computer back then.

Fast forward a few years later I saw this "Visual Basic" thing and thought it would be similar ... it was, but only sort of. I had no book to learn from at first so I remember clicking through every single menu and button available to see what it did. Then I remember using our dialup to download every possible 3rd party VB form control and throwing them in a Form to see what they did. I don't know why I found this entertaining enough to keep doing it.

Eventually by copy pasting and changing stuff I was able to write some basic "homework helper" programs: calculate the area of a circle and stuff like that. Soon after I tried to look up tutorials which taught me basic win32 programming to do things like have an icon in the status area next to the clock, and then hiding my window to run in the background and make annoying sounds so I could build a silly little prank program to install on my friend's computers which was fun but often would fail because they were missing some .dll file which wouldn't fit on the same floppy.

It could be frustrating at times but also I feel so blessed to have lucked myself into learning programming this way and my parents pretty much just letting me do whatever I wanted to this expensive device that probably was not a small thing for us to afford at the time.

Even tutorials felt more fun at the time, it'd be "hypnoMan37's windows registry tutorial!!! HEyyeyeyy Guuyzs :-)))) gzgzgz to my irc channel #blabla on EFNet! so first you call RegistryCreateNewKey32(...." because god knows I did not have an MSDN CD either.

Learning via a code camp feels way more efficient but also so much more dry in comparison. I wonder if there isn't a substantial cost to boring the newbies to death.

replies(9): >>42142679 #>>42142859 #>>42143066 #>>42143457 #>>42143619 #>>42144259 #>>42147804 #>>42148463 #>>42155834 #
rd07 ◴[] No.42144259[source]
We have similar experience with VB6, though I was the opposite. Instead of reading a book about BASIC, I was reading a book about VB.NET.

My first interaction with Visual Basic was through VBA in MS Word. The first time I opened it, I know that it was a place to code, but I don't know what kind of code I have to type. I don't know any programming language at that time.

And then sometimes later, I found a VB.NET book at a bookstore. I was overjoyed at that time, and immediately tried it on VBA to be dejected because the code didn't run at all. I still remember how I several times, until I swear that if the last trial I do also didn't run, I will give up. Fortunately, it does run!!!

Turns out, I didn't know that the VBA on MS Word in my computer is based on VB 6 while my book is about VB.NET. The code is a little different, and that's why my code didn't run.

After that, I bought every book I can find about VB 6. I also somehow stumble upon a VB 6 IDE installation on my relatives CD stash, and installed it on my computer.

And till today, I still think that VB 6 GUI Builder is the best I have ever tried.

replies(2): >>42145854 #>>42153651 #
1. makmanalp ◴[] No.42153651[source]
When .NET finally came out and I started learning about it (I had signed up for a course at this point) I remember it feeling much more complicated - I didn't understand why I needed objects and I also recall not understanding access modifiers like protected / private - who am I protecting my code from? The book I got for the course was like an encyclopedia. I failed the microsoft certification exam, not surprisingly. I was just finishing middle school and starting high school so it didn't really matter.

I think there's probably some lesson in there about microsoft misunderstanding the strength of VB as a RAD tool for mom and pop shops and non-software firms who have a single tinkerer, rather than an Enterprise Language. It died a slow death in favor of C# at that point. Embrace, extend, extinguish, perhaps.