Sponsored links

Valid XHTML 1.0!
Valid CSS!

Product: Book - Paperback
Title: Programming Perl (3rd Edition)
Publisher: O'Reilly
Authors: Larry Wall, Tom Christiansen, Jon Orwant
Rating: 5/5
Customer opinion - 5 stars out of 5
It is Really good

This book has absolutly everything you'll need to know about Perl. The only other book I would recommend is Learning Perl from O'Reilly. I develop CGIs for a job, and this book is an invaluable reference. I have been much impressed with this book. BUY IT! =)

Product: Book - Paperback
Title: Programming Jakarta Struts, 2nd Edition
Publisher: O'Reilly
Authors: Chuck Cavaness
Rating: 4/5
Customer opinion - 4 stars out of 5
A good struts reference

I am fairly new to J2EE and in particular Struts, but have the oppurtunity to use Struts. I had worked though some examples in another book, which was very example oriented, but was full of mistakes, so I was looking for something more of a reference that included details. This book seems to provide that detail. I found it full of useful information, particular for some of the more obscure material.
Now, if you like to sit and read an entire book, you might want to skip over a few parts as you read the book, because some of reference material provided, for example overriding various of the controller features by overriding some of framework classes or maybe some of the detail about how the RequestProcessor works is possibly more than you want to know when you are first learning, but too much material is usually not a serious complaint.
I found this book to be great intermediate to advanced reference book (but since I'm not an advanced struts user you can take that with a grain of salt) and will be keeping it around as I build struts systems.

Product: Book - Paperback
Title: The Practice of Programming
Publisher: Addison-Wesley Professional
Authors: Brian W. Kernighan, Rob Pike
Rating: 5/5
Customer opinion - 5 stars out of 5
stuff that matters

For the facts I have nothing substantial to add to the January 2001 reviews.
I do programming since 1983. Started with Fortran, Pascal, Modula 2 and C. Read Bertrand Meyer's "O-O Software Construction" which opened my eyes how to design interfaces. I created code and rewrote code. I worked together with programmers of many kinds of personalities.
Comparing my experiences with what Kernighan and Pike's book tells is, that this book really discloses the fundamentals of effective software development to produce maintainable software systems:
simplicity, clarity, generality.
And working with programmers who are on the way to discover or yet have discovered these pearls of wisdom is fun!
BTW: "The Pragmatic Programmer" written by Andrew Hunt and David Thomas is another great book to consider.

Product: Book - Paperback
Title: Programming Interviews Exposed: Secrets to Landing Your Next Job
Publisher: Wiley
Authors: John Mongan, Noah Suojanen
Rating: 4/5
Customer opinion - 4 stars out of 5
Great review, but lacking a few topics

I've heard that programming interviews sometimes involve wacky, off-the-wall questions ("why is a manhole cover round?"). I bought this book with the belief that it would shed some light on how to approach these kinds of questions. I was dead wrong.
There are only around 10 pages on actual interview/resume advice. The bulk of the book is taken up by mini-reviews of topics ranging from the utterly basic (arrays, strings, recursion) to the utterly unlikely to be asked in a programming interview (implementing linked lists, trees, graphs).
A few pages are spent on mini-reviews of topics that might be worthwhile. However, the reviews are so short and basic as to be useless. For example, 1 page on graphics programming and 2 pages on SQL. The author spends a half-page in the SQL review expounding on the following: "Lesson:If you don't indicate that you know SQL, you probably won't be asked anything about it."
The only redeeming factor (and the reason for 2 stars) are the 2 chapters on mathematical puzzles and brain-teasers. Readers would be better off buying a book on brain-teasers, but the chapters do give a general idea of how to approach these problems.
Overall, this book reads like a watered-down high school CS review book. The mini-reviews are useless, actual resume or inteview advice is scarse, and the brain-teasers are better covered in other books.
Programmers wanting interview or resume advice would be better served by a more traditional book on interviews/resumes.