10 ms·

I read a lot & not all books were released in 2009-2013... if you look to the page more precisely - it has a separate section, called Recommendations where onl

by alexott 13y ago

I read a lot & not all books were released in 2009-2013... if you look to the page more precisely - it has a separate section, called Recommendations where only some of books are listed. Regarding the Amazon - the 2nd paragraph clearly says "if possible" - nobody forces you to buy books from amazon!

bad_user 13y ago
Lets do the math - this isn't fiction we're talking about, it takes at least 2 weeks to read a technical book and this is assuming you can read at least 1 or several chapters per day, or maybe skipping chapters, which can't happen for many of those books, as some of them are pretty challenging and you have to think about what you're reading, you have to try out samples, you have to do extra reading to clarify stuff and so on. But lets be generous and say that 2 weeks is the average for reading a technical book. And there are on average 52 weeks in a year. 132 * 2 / 52 = 5.08 So that's 5 years worth of book reading, assuming that (a) you're reading each and every single day, without exceptions, without breaks and (b) that you aren't reading anything else. Why the heck won't you admit that you haven't read some of them and simply pasted links based on Amazon's recommendations or something? Also, the section on recommendations is shallow. It references books for getting started, after which it gives advice to continue with the books above. And I'm not seeing negative remarks on the referenced books at all. Everybody has opinions on whether a book was good or not. What kind of review doesn't do that? "Functional Programming in Scala" is an awesome book on functional programming btw. You should put that as a recommended book.
- alexott 13y ago
  I at least briefly went through the almost all books before putting them into list (not counting early releases). It's not required to read every word in the book to understand what's in it. I've heard about "FP in Scala" and it's loaded into my kindle prepared for vacation (together with many other)...
  - deleted 13y ago
    [deleted]
- pseut 13y ago
  It doesn't take two weeks to read a technical book that covers material you already know. I have no opinion on the site's reviews, but it's completely possible to read hundreds of very technical books, as long as the material overlaps.

by alexott 13y ago

bad_user 13y ago

Lets do the math - this isn't fiction we're talking about, it takes at least 2 weeks to read a technical book and this is assuming you can read at least 1 or several chapters per day, or maybe skipping chapters, which can't happen for many of those books, as some of them are pretty challenging and you have to think about what you're reading, you have to try out samples, you have to do extra reading to clarify stuff and so on. But lets be generous and say that 2 weeks is the average for reading a technical book. And there are on average 52 weeks in a year. 132 * 2 / 52 = 5.08 So that's 5 years worth of book reading, assuming that (a) you're reading each and every single day, without exceptions, without breaks and (b) that you aren't reading anything else. Why the heck won't you admit that you haven't read some of them and simply pasted links based on Amazon's recommendations or something? Also, the section on recommendations is shallow. It references books for getting started, after which it gives advice to continue with the books above. And I'm not seeing negative remarks on the referenced books at all. Everybody has opinions on whether a book was good or not. What kind of review doesn't do that? "Functional Programming in Scala" is an awesome book on functional programming btw. You should put that as a recommended book.

alexott 13y ago
I at least briefly went through the almost all books before putting them into list (not counting early releases). It's not required to read every word in the book to understand what's in it. I've heard about "FP in Scala" and it's loaded into my kindle prepared for vacation (together with many other)...
- deleted 13y ago
  [deleted]
pseut 13y ago
It doesn't take two weeks to read a technical book that covers material you already know. I have no opinion on the site's reviews, but it's completely possible to read hundreds of very technical books, as long as the material overlaps.