This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Some of reviews for "Structure and Interpretation of Computer Programs" are very entertaining: "However, I really bought it to see how the masters teach introductory programming. They don't, unless maybe you have a SAT score of 1500+, an IQ of 170++, and are an MIT student being taught by someone who knows and loves this book. Otherwise, don't touch it! There are better things to do with the money: burn it, give it to the rich, or buy drugs from a narc. " "From what I've read, I get the impression this book was written in a rush, and with the purpose of cramming tons of nonsense and filler in just to have an excuse to present Scheme (a pathetic language)." "Besides the heavy and dull material (which may not be that bad at all) this book has an unfriendly style, as if the authors are trying to elevate themselves above the crowd, instead of teach something. I won't recommend this text even to my enemies." "Try my SICP simulator. Close your eyes and have someone kick you in the teeth. This will be a good approximation to how you'll feel when readint this book." "This book is good to read when you have trouble falling asleep." "After taking my class, i burnt this book."
For the Miriam-Webster Dictionary: More like Kindergardenate Dictionary, March 20, 2002 Reviewer: Jon Dansby from Ft. Worth, TX USA Who let this guy write a dikshunary!! This is one of the dummest books I ever read!! I could have rightten a better one in 1/2 the book!!
Business Specifications: The Key to Successful Software Engineering by Haim Kilov Through the looking glass darkly (understanding this book) June 18, 2001 A colleague gave this book and challenged me to understand it, and if I truly understood it he further challenged me to write a review. Since I'm posting a review I obviously understood it. My first pass through the book was frustrating. I could not get a sense of what the author was trying to say, even though it sounded important. Each time I was tempted to admit defeat and toss the book back in my colleague's face some unseen force make me keep reading. By the time I reached the end I knew less about business specifications than I knew when I first started reading. I'm not a quitter by nature, so I went back through the book looking for clues that would point me to the elusive methods of business specifications. About mid way through I had a Zen-like flash of understanding and enlightenment. I'd figured it out! The author has skillfully blended the timeless work of the Grimm Brothers, Hansel and Gretle, with the surrealistic writings of Lewis Caroll. Here are the clues: like the Grimm Brothers' masterpiece the author drops little facts and ideas like bread crumbs throughout the labyrinth writing to subtly lead you to that supreme moment of Epiphany - understanding how business specifications can be married to object-oriented techniques. In case the reader is too dense to get it, he also draws maps in the form of diagrams. He fails, however, to explain the symbology in clear terms, and is equally obtuse when it comes to explaining the rules of his notational masterpiece. This is where Lewis Caroll comes in, and how I discovered the key to understanding this book in the first place. He litters the book with passages from Lewis Caroll's books. Not a subtle message, but one that certainly tells you how to read the book. Think surreal and pretend you are chasing a white rabbit and the quest for gleaning useful information from this book will suddenly have a purpose. As I said, I had a brief moment when the entire book made perfect sense, then, poof, it evaporated and I returned to the real world where I was utterly confused by the author's writing style and intent. The way I see it you have some options. (1) Avoid the book. Frankly you will not miss anything. (2) Buy the book and when or if your moment of clarity comes and you achieve enlightenment write it down before you forget it - and please share it with the rest of us. (3) Buy the book, attempt to understand it and, failing that, go ask Alice.
Reviews of Cary Jardin's books are usually a lot of fun. His SCJP 1.1 Cert Guide in particular generated quite a bit of excitement. Here's another set of reviews to remind you why carelessness is bloody and painful for technical books.
Originally posted by Michael Ernest: His SCJP 1.1 Cert Guide in particular generated quite a bit of excitement.
An excerpt from a five-star review of that book:
Unfortunately Mr. Jardin's books contains many mistakes. As many other books. As Java itself. As any software application. As software applications written by Mr. Jardin's critics. But if you are really Java programmer - it is not a problem to you. If you are not Java programmer - you can find of course mistakes-free book, read it then FAIL the test