Try to learn WHY some particular technologies exists and popular. Try to understand the Ruby's style (describing, rather than coding) and the Python's way (simplicity, clarity, readability). Try to realize bloatedness, meaningless syntax fluff and limitations of Java (NIO2 is just a spec). The approach to C programming of Linus (once again clarity and readability), and then compare it to FreeBSD and OpenBSD projects. Look at webkit, chromium, qt and try too figure out which sub-set of C++ is portable and safe to use, and when it a right tool. Read the source code of nginx, varnish, openssh, sqlite, v8 or whatever you like.
Ask HN: What should I learn?
31–34 of 34 posts
Re: Ask HN: What should I learn?
#32This is the mother of open-ended questions. There are many questions like this on Stackoverflow, be sure to check those answers, too. Deciding on what to learn is hard, however, deciding on which one to choose from a list of things is much easier. The important aspects are (in order of importance IMO): (i) How does this help with my bottom line, i.e. will knowing this technology earn me money (ii) How "sexy" is it, i…
That's the good parts, not the goof parts, heh. I second the recommendation, but I think it should be the second Javascript book read after the latest edition of Javascript (The Definite Guide, by Flanagan). JQuery follows.
Re: Ask HN: What should I learn?
#33Try to obtain expertise on a domain.
Re: Ask HN: What should I learn?
#34Learn whatever looks fun to you. When it stops being fun, repeat process.
I recommend Forth at least for the ideas. It's interesting because its a language that avoids needing a lexer, parser, or optimizer. It has the most beautiful ideas I've seen since I found Lisp.