4 ms·
I suppose it depends on your approach - my two cents - is your book . . . a. geared toward programming / learning a language? I've been surprised, given the sp
by vergeman 13y ago
I suppose it depends on your approach - my two cents - is your book . . .
a. geared toward programming / learning a language? I've been surprised, given the sparsity, the efficacy of a "showing-by-example" style of writing seen in the Apache Thrift documentation. K&R (to me) is decent for language acquisition, but even more useful as a quick "how did they do that again" refresher. I've found "Linux Kernel Development" (Love) as a very nice book blending concepts with programmatic examples. So the above is maybe a spectrum within this style of writing that I've found helpful.
b. a more "textbook" / algorithmic approach? I remember thinking "Computer Networking: A Top-Down Approach" (Kurose, Ross) was one of the lighter texts that didn't necessarily feel "textbook." "Introduction to Information Retrieval" (Manning, Raghavan, Schutze) also comes to mind, but more academic.
- chewxy 13y agoI don't think I am ever qualified to write text book material. Bits of the book I suspect will be "How I got to this point in the code". There will be a lot of show-by-example. I've written half a chapter so far and it does really feel like I'm just annotating my code, which isn't a good thing.
- vergeman 13y agoI hear that - skim through Love's Linux Kernel Development and see what you think. It sounds like you're going for something much lighter, so maybe something along the lines of the "Little Book on Coffeescript?"