List price: $18.95 (that's 30% off!)
Plus, you can't beat hearing all the many great stories from the "classic" Bond directors like Guy Hamilton and Peter Hunt, Ken Adam (his account of Connery almost being eaten by a shark during the shooting of Thunderball was quite funny)as well as the many Bond Girls, Villains, cast and crew. I liked what Desmond Lewelyn told the author and I learned a whole new side about lovable old Q.
Also, the contributions to the book from Hugh Hefner, Kevin Costner, Harison Ford, and that infamous CIA spook E. Howard Hunt were quite fascinating and take this book to a whole new dimension than those other Bond books.
It's clear Mr.Giammarco knows the Bond legacy inside and out and his access to everyone is an invaluable resource for us Bond aficionados. I've been waiting a long time for a book like this - a really fun read. I highly recommend it. No Bond fan will be disappointed!!!
List price: $15.95 (that's 30% off!)
Not only does the book have an excellent tutorial which goes over major Ruby concepts and the majority of the language you will encounter on a daily basis, but it also has an indispensable language and standard library reference, as well as an overview of the C API and details on the inner workings of the Ruby interpreter.
This book is definitely worth picking up if you want to start dabbling in Ruby, and is almost a requirement to have on your desk during heavy hacking sessions.
I was also quite pleased with the depth and breadth of the book. The initial tutorial does not just gloss over the libraries. Rather, it gives you minor examples showing how to use most of them, and then leads to the library documentation in the back of the book. It's a very effective technique.
After two days with this book I was writing apps that query websites, manipulating html with regular expressions, maintaining persistent object stores, etc. Both the language, and the book are very very powerful.
I heartily recommend this book to anyone interested in Ruby.
But this book is no fantasy, however, it's great. Focusing on human characters on the scene of Mountain Hunt, Eddings creates intrigying book, which will delight the fans.
A must read, like everything by this author.
There are a few reviewers here who rated this book low. To these individuals I say "Hey, I think you missed the point by a mile!". This book is meant to give you some solid development "food" to digest. Every single page is worth the read from top to bottom. In a single summary, you are only doing yourself GOOD by reading this book. Don't agree with a particular point? Well, fine! Turn the page and continue on to the myriads of other valuable points and lessons. A waist of time or harmful, are two statements that do not even belong to the most general reference of this publication...for shame.
Trust me, take the time to read this book and add it to your collection, you'll be glad you did.
The book is nice and terse, covering the ground it needs to cover in little over 250 pages. Clearly the authors are applying the lessons they learnt from Unix, Perl, c++ and a variety of other sources. Rather than wasting words trying to beat home their lessons, the authors have trusted that the reader has some degree of intelligence. They present each nibble of wisdom in a few paragraphs of pithy text which helps to support the 70 tips they provide throughout the book.
The book covers a fair degree of ground in it's 258 pages. Testing, documentation, automation and even requirements specifications all get a look in. Most of the book however, is devoted to that part of the art which is harder to define and learn. It is usually learnt from painful experience, or passed on by a senior programmer if you are lucky enough to have one around. It is this knowledge that makes the book worth the read.
It's value is not so much that you will find anything revolutionary inside the book, you wont, but that the book provides a terse and approachable font of wisdom for programmers of all skill levels. It is filled with the sort of sensible advice that stops you getting third degree burns while cooking, or cutting your hand off while doing woodshop. Managing to convey that knowledge without sounding preachy or ivory tower in nature adds to it's charm.
This book will be required reading for all the programmers on my team at work. It will help them to understand the bigger picture of development, rather than focusing on the minutae of cutting code.
The techniques and habits the authors describe are very useful. Even if you may not have a use for every single one in every single project, I am quite convinced that you may over a career find all of them useful. The author's don't propogate that this set of ideas are a complete set - what they do propogate, however, is that programmers should work smarter not harder, and that one obviously achieves by thinking about what you are doing (and learning form other - like this book).
The writing style is very entertaining and thus makes a good read. I would say that this book is indespensable in your personal growth as a programmer. It may just prompt you to adapt your way of doing from being a "child" programmer to becoming a "real" ("adult") programmer. If you think you are already a "real" programmer, like I thought, then this book should make you realize that one is never to old to learn, that one should never stop thinking about what (and how) you are doing.
Enjoy a great read.