⌊ K™¦krizzna.web.id ⌉

First off, I was going to give this book zero stars, but (a) you can’t rate things at zero and (b) that wouldn’t be entirely fair to the book. It’s not really its fault. Let me explain.

Here’s the thing: two weeks ago, this guy I met online on one of those dating sites takes me out for a pretty nice date. He was kind of sweet and he’s telling me about some computer startup dot-com thing he used to work at in California. I figure he’s in programming or something, but I didn’t want to pry — I mean save something for the second date, right? Third date, you don’t even have to talk all that much, but the second date’s a good time for follow-up questions and details. I don’t need his whole resume the first time I meet him.

I mention this only by way of clarifying that this guy is in computers (except I think he’s sort of between jobs) and Java is a computer language. With me so far? Good.

Anyway, the date went okay. He says he wants to go out again, and then he sends me an email the next day and says he’ll call me and (again, he repeats) he wants to go out later this week…

… two weeks go by – TWO WEEKS – and no call, no email. Nothing. So I figure, whatever, he’s not interested. No big deal. He was nice, but he wasn’t George F***ing Clooney or anything. Then a couple days ago, he emails me and says sorry he didn’t call in all this time, but am I available to go out TONIGHT. And I’m all like WTF?

So not really this book’s fault, but seriously. Come on! Three stars for this book on computers because on the one hand people seem to like this book okay (I haven’t read it — don’t plan to) and on the other hand… MEN!
Rating: 3 / 5

I highly recommend the Deitel Java: How to Program book instead.

Liang over and over again introduces terms that he has never defined. He does not tell you why code is the way it is. He is terse, and there is just no true explanation.

The layout of the text is also in black and green, and that’s it. His code is hard to follow compared to the Deitel book.

I’m truly shocked at how people seem to like this book. It’s unintelligible in my view. I dread reading it and actually read the Deitel book instead.
Rating: 1 / 5

I’ve never liked reading tech books but this one I haven’t fallen asleep to. Not sure if it’s the book or because I’m reading it at the gym. In general the book is easy to understand, has good notes, cautions and examples. I’m however really annoyed with their examples with one character method and variable names. Somehow it makes it harder to read. I find myself stopping and saying to myself, where is that stupid A() or B() or a, b variable again? Where did they declare that? Were they trying to save money by printing one letter instead of a word?
Rating: 3 / 5