3 ms·
Hmm, I never liked those books on subjects like operating systems or programming languages or something. Tried a few times, but they generally have a low inform
by lucb1e 12y ago
Hmm, I never liked those books on subjects like operating systems or programming languages or something. Tried a few times, but they generally have a low information density (telling it in the typical book-like fashion) and go into details that you don't need or remember. I usually learn by googling or asking others when I don't know what to google.
Perhaps a short introduction might have been useful, but it depends on the person what you want to use and thus what you should be taught first. I'd be bored if it introduced me to things like the difference between /dev/random and /dev/urandom when I didn't even know what executable permissions were. Fun fact: last semester we got Linux lessons in school and this (u)random difference is one of the things they taught (alongside the basics like rm and grep usage). Nobody even knows what entropy is.
- eru 12y ago> Hmm, I never liked those books on subjects like operating systems or programming languages or something. Tried a few times, but they generally have a low information density (telling it in the typical book-like fashion) and go into details that you don't need or remember. I usually learn by googling or asking others when I don't know what to google. This works well when you already know enough to have a mental framework. For learning something new, say Forth or Prolog or Haskell, a longer document might be worth reading.
- lucb1e 12y agoGood point, I did start reading a tutorial for Prolog once (though didn't get far before getting bored). I think if I wanted to do anything in Prolog now, I'd read a bit more from that tutorial and then start googling specific needs, so yeah the tutorial (which is comparable to a book) was needed to build a mental framework.