Part of this stems from a pre-internet mentality. "Of course I need a full function reference! Where else would I find it?" Now you just Google it. A thinner book can leave the reference to the search engines, but for some reason this older way has become entrenched.
Blunt and necessary review of programming language books.
41–50 of 112 posts
Re: Blunt and necessary review of programming language books.
#42So aside from K&R, what are some of the best small books?
Re: Blunt and necessary review of programming language books.
#43I'd been meaning to pick up a new language, and a few weeks ago I pared down my list of choices to two languages: Scala and Go. Then I went looking for "official" tutorials/references. For Scala I found Scala by Example , a 145 page PDF that comes with the Scala docs. For Go, I found the Go tutorial -- a very short tutorial with a bunch of examples. I picked Go because, seriously, I don't have time to read 145 pages…
Every book on a language needs this. The best I have seen was in a python book where the author stopped and told the reader enough had been learnt to write any program. The closet to the K&R model I have seen is with the Big Nerd Ranch books.
Re: Blunt and necessary review of programming language books.
#44I'd been meaning to pick up a new language, and a few weeks ago I pared down my list of choices to two languages: Scala and Go. Then I went looking for "official" tutorials/references. For Scala I found Scala by Example , a 145 page PDF that comes with the Scala docs. For Go, I found the Go tutorial -- a very short tutorial with a bunch of examples. I picked Go because, seriously, I don't have time to read 145 pages…
Re: Blunt and necessary review of programming language books.
#45I agree 100%. K&R is the standard all authors should strive for. The length of these books is also our fault. Bigger books sell better. I hope there is a backlash brewing. K&R, Little Schemer, Smalltalk Best Practice Patterns, were all great small books.
I tried to learn programming but I was discouraged by the utter lack of pedagogy in the books I've picked so far. The author pretty much nailed it. I even tried Land of Lisp only because it was supposed to be fun, but unfortunately it used this horrible and widespread format where the author writes all the code for you and proceeds to an explanation. There is no creation (or creative problem solving) ! And creation i…
I have seen most students prefer to presented with a whole working program and then expand on it in the challenges the book provides. The author of this article was expressing a desire for shorter books that give full code listings rather than code snippets and challenges that you seem to prefer.
Re: Blunt and necessary review of programming language books.
#46Addison Wesley
Appress
O'Reilly(cookbooks fare better)
Re: Blunt and necessary review of programming language books.
#47Too bad authors get paid by publishers by the number of pages, and publishers push the books to education, where the attention economy takes care of the rest. Good thing that programmers are more often self-learned, which makes the problem relatively benign compared to say, economics books.
This is not true. Authors get paid by the number of books sold, period. For my book we had an approximate target length, but that was a precondition. Past that gate, all we saw was $x/copy.
Re: Blunt and necessary review of programming language books.
#48It's sad really. I hope ePublishing fixes this.
Re: Blunt and necessary review of programming language books.
#49I've been begging publishers to let me have a go at a ~100 page F# tutorial book, but they've told me again and again that books without a wide enough profile on the shelf just won't sell. It's sad really. I hope ePublishing fixes this.
Re: Blunt and necessary review of programming language books.
#50Earlier quoted context omitted.
_The Scheme Programming Language_ by Kent Dybvig is also very good. _Structure and Interpretation of Computer Programs_ is my preferred "how to think in Scheme" book. I would recommend against _How to Design Programs_, which is entirely too pandering and focused on imperative programming for my tastes. http://www.scheme.com/tspl3/
It seems there's a fourth edition: http://www.scheme.com/tspl4/ Also, Wikipedia says that "Teach Yourself Scheme in Fixnum Days" is outdated in some parts: http://en.wikipedia.org/wiki/Teach_Yourself_Scheme_in_Fixnum...