I myself read 400 pages at first, there everything was described as the most banal, I thought I read what kind of clever man, and even the syntax already seems to know how to write Javovsky .... Then I scored almost this book for half a year, with the thoughts I’ve been a programmer, it's time to teach the spring, and what's left in the book is probably a lightweight, then read it at your leisure. I started reading a book on spring, and I entered a stupor into a stupor for a couple of moments, for example, about Makito met there .... Then I looked at the table of contents and saw that in the book of Ekel almost at the end there was a couple of pages about Makito ... Well, I decided it's time for the book. And then I realized that I hadn’t even finished reading the floor of the book, and then less trivial things are discussed ... In general, this is some kind of kapets. + work turns out that I absorb very little material. Here now the question arises again. Well, maybe it's his stuff, read about those things that interest me. And all that remains is left. For example, less interesting is swing and that same makito, well, maybe another input / output system and lamdas .... And can another miss everything!? (Now I'm on 580 pages from 1150)
(I ask you to note that those who read the book online may not correctly imagine the volume of a real book, because many say they read and then give a link and I see there is a maximum of 100 pages of the most banal text about java, in general, a greatly truncated version)
Here are the questions:
- Who really read this book?
- How long did it take you?
Have you done all the examples?
Well, maybe a couple of tips ...
