File Size: 12038 KB
Print Length: 640 pages
Simultaneous Device Usage: Up to 2 simultaneous devices, per publisher limits
Publisher: Pearson; 3 edition (November 3, 2011)
Publication Date: November 3, 2011
Text-to-Speech: Not enabled
X-Ray: Not Enabled
Word Wise: Not Enabled
Lending: Not Enabled
Enhanced Typesetting: Not Enabled
Best Sellers Rank: #522,813 Paid in Kindle Store (See Top 100 Paid in Kindle Store) #121 in Kindle Store > Kindle eBooks > Computers & Technology > Systems Analysis & Design #135 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Structured Design #283 in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Java
I'm using this for my first algorithm course at college and I have to say that this is a terrible book for me at my current level. The book does not have a thorough explanation on any data structures. The analysis in algorithms are unclear. It skips a lot of fundamentals, too. And a lot of the time it gives superficial but confusing instructions on what you should understand. I'm assigned this book by a professor who basically can't teach, which makes this course a nightmare for me.
This book was used in my Data Structures and Algorithms course. I was not familiar with this particular book nor the author going into the course and tried to keep a fairly open mind. Typically when you hear about this subject, names like Cormin (CLRS) or Sedgewick pop-up... and with good reason, both of those authors manage to remove the abstraction from a fairly difficult topic and write in a descriptive, engaging manner.Weiss's book comes across as dry, abstract, passionless. Cover-to-cover, this book manages to consistently find a way to bore the reader to death by using technical verbiage, and non descriptive language. Whats worse is that concepts feel too generalized and incomplete. Making this book focused on Java I believe actually hurts the reader more than it helps. It introduces the authors own coding style which tends to distract from the concepts your studying since you have to take the time to decipher what the author is attempting to do, but it also becomes a crutch for the author to spend less time giving good explanations (a show instead of tell approach). This unfortunately does not work at all. In contrast, a book like CLRS which relies on psuedocode not only clearly explains algorithms but forces the user to learn/implement them on their own.
This book was required for my undergraduate class on Data Structures, but we almost never used it. I never found it useful when reading it on my own time and actually found it to be detrimental to my understanding of some concepts. Other people I've talked to have felt the same, unless your professor is requiring this for a class, don't bother.
Look, I'll be honest. I'm one of the few students that actually uses and appreciates textbooks. I don't like doing my reading online either because I like having a physical copy to mark, make notes in, and pass through. And I don't often groan about textbooks either. Sure, they're overwhelmingly boring. But for the most part, I find them useful (some more than others) and read them cover to cover. So to get me cranky about a textbook you have to do your fair share.And oh does Mark Allen Weiss deliver. The book is a complete nightmare. A great textbook is able to walk the reader through each part of the field he's learning, teaching it to him one piece at a time. I've always said if a textbook is great, you should be able to learn the subject from it without the aid of a teacher. Data Structures and Algorithm Analysis in Java isn't even adequate or below par -- it's straight garbage. It's the sort of book that makes one thankful for the premise of Farenheit 451.The author frequently likes to explain things while missing out important steps in the logic -- steps which may be obvious to experts in the field, people who have been studying computer science and mathematics for a long time, or exceptionally keen students, but which will utterly befuddle the rest of us. His English is clunky. He has a very unique talent for phrasing things in the most non-intuitive way possible. Relatively simple topics become a nightmare.I've spent the semester spending hours on Khan Academy, Google, or in my instructor's office seeking clarification of topics because trying to learn from this book is utterly hopeless. I'm learning Data Structures just fine, but this book has only been an obstacle to that process, not a help.Do not waste your money on this garbage. You won't use it. Even if you're a stickler for textbooks, trust me, this isn't worth it.
I find the concepts presented in my data structures very intuitive, so I haven't had to use this textbook much; however, the language the author uses is clear and concise, and I will likely keep this textbook as a reference after my class is over. Of course, I wish that the language weren't Java -- I'm a Pythonite. Even so, the code is easy to follow regardless of background, and you can always lean on the pseudocode algorithms as necessary.I recommend it strongly for undergrads pursuing a degree in CS who will be referring to these concepts again and again in future classes.
I was required to purchase this book for an undergraduate class in data structures. Many of the sections in the book try to explain data structures using code, rather than concepts. It would make more sense to provide a complete conceptual explanation, then show you the code. After reviewing external material from other sources (which I had to do to learn the material), it is obvious that the concepts are not as hard to learn/understand/apply as the book would make it seem. This book is not written by people that have an aptitude for education.
Does not offer clear explanations, believes reader is an expert in the field already. Has code / images all over the place in the book instead of corresponding it with the text. Stay away if you can, but this book was required for a class I was taking.