Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My anecdotes as someone who started to learn programming around 1992:

"Before Google" is probably what you really mean.

For me: Early on (age 7-14) it was how-to/text/learn-X-Y-days books + man pages and lots of playing with Batch files, GW-BASIC, QBASIC & ASM.

Later on in highschool I was lucky my school had AP programming classes (and a small C-S dept!). So that helped me move from BASIC to VBasic/C/C++. Along the way I picked up vbscript as an sysadm intern and bash playing with early desktop Linux.

When I started college, even though stackoverflow didn't exist, you could certainly now Google things, but results were often not as good and often paywalled. During this time using the same methods above + college classes I picked up: Java/Haskell/Scheme/Prolog.

Later on now firmly in the stackoverflow era I picked up C#/Perl/Go while working, but I did this more like I always had done than the "on-line academy/tutorial" ways people seem to do it now days.

My most recent languages are Go (I have been programming fulltime professionally in it since Go 0.8) and Rust (still learning), but I still have eschewed the "on-line academy/tutorial" way of learning. I guess I don't appreciate a highly curated learning path (when I used text books I tended up use them more as references when stuck or for learning theory).

Stackoverflow is of course something has a full time programmer I might use once or twice a month... but it really only shines (IMHO) for the most superficial of issues (glitches in toolchains etc), if you are going their to learn theory your mileage may vary.. all my opinion of course.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: