Sponsored links

Valid XHTML 1.0!
Valid CSS!

Product: Book - Hardcover
Title: Understanding and Deploying LDAP Directory Services (2nd Edition)
Publisher: Addison-Wesley Professional
Authors: Timothy A. Howes, Mark C. Smith, Gordon S. Good, Tim Howes
Rating: 5/5
Customer opinion - 5 stars out of 5
This is the THE Ldap reference

And that is where it excells! I have actually read this book cover to cover once, and now I use it as a good reference on LDAP. It is not exactly geared to the implementor, but rather to both the Designer/Architect as well as those who have to "sell" LDAP to an organization. If you are new to LDAP, or are going to be doing any sort of design work, this is the first book you should read, its introduction to LDAP is the best I have seen, and although it is weighty (and not just the size of the book) it is quite comprehendable if read in order.

Product: Book - Paperback
Title: ASP.NET Website Programming: Problem - Design - Solution, C# Edition
Publisher: Wrox
Authors: Marco Bellinaso, Kevin Hoffman
Rating: 2/5
Customer opinion - 2 stars out of 5
Something's lost in the translation

I've read the reviews given to the original c# version of this book and based on them I bought the VB.NET version. I haven't seen the c# version yet, but based on the reviews I read and my experience with the book in front of me I should have gotten the c# version.
My basic complaint is that things are not completely explained in the book. I get the feeling that the authors went through a process of creating this example web site and then went back to tell people how to create it without explaining their methodology or the logic of the decisions that they have made. Either that, or something's lost in the translation to VB.
Right now I am working through the text and am in chapter 3. In chapters 2 and 3 they have you create base classes and other base sources that form the basis for the functional modules created later. I find that the explanations of the design are very lacking. They do not outline a philosopy or methodology. They do not do a satisfactory job of explaining their decisions.
Even something simple like explaining where modules are located in the directory structure is handled like the left hand didn't talk to the right hand. You're amazed after you've read their description of where this new class goes three times, poured over the diagrams and still don't have a clue as to where they want you to put this particular module. The source code that you download from WROX doesn't seem to jive with the descriptions in the book for directory structure either.
This is definitely not a book for beginners. The source code is not ready to run. It has definite problems. ...
So far I'm not very satisfied with the book. I'm hoping it improves by chapter 5. I'm sure I can get this bugger to work, ... I can understand a few syntax errors when the printer gets a hold of it, but so far this book has not satisfied. Between downloaded code that doesn't work well and half explained code in the book I'm getting just a little irate.
I'll revisit this review after I've gotten further in the book, but so far I'm not satisfied and felt that other readers deserve a fair warning.

Product: Book - Paperback
Title: Object Oriented Perl
Publisher: Manning Publications
Authors: Damian Conway
Rating: 5/5
Customer opinion - 5 stars out of 5
Awesome Book on OOP PERL

This is a great book. It reads fairly easily, and just the first few chapters give you a great understanding of how to use oop concepts in Perl programs. Also, I found it very helpfull in exlaining some advanced perl topics, that are used along the way. I got out of it exactly what I wanted, and then some.

Product: Book - Hardcover
Title: Managing Information Technology (4th Edition)
Publisher: Prentice Hall
Authors: E. Wainright E. Martin, Carol V Brown, Daniel W DeHayes, Jeffrey A Hoffer, William C Perkins, E. Wainright Martin
Rating: 1/5
Customer opinion - 1 stars out of 5
You've got to be kidding me.

This is literally the worst textbook I've ever used in my entire academic career. This book is jam-packed with jargon ("utilize"), acronyms (e.g.,"ERP," a term that the book does a poor job defining), and slashes. By slashes I mean, do you know how IT consultants love to use two synonymous words when one would suffice? For example: "I love/like to go jogging/running to the store/market."
My MIS professor was a moron, however, so it's understandable that he would choose this book. IF YOU ARE A PROFESSOR WHO IS NOT A MORON, DO NOT MAKE YOUR STUDENTS SUFFER THROUGH THIS BOOK. Thanks.