Programming Books

OK, so perhaps you don't need this book, but you'll enjoy it anyway!
The best review and tutorial on clusters available, this book is also funny
enough that you probably don't want to read it in a quiet environment.

As other reviewers have said, this is an excellent book and is a *must have* for anyone exploring practically any aspect of cluster computing. Even beyond the quality of the information conveyed, the writing style is wonderful and the author makes an otherwise abstract and cumbersome topic quite readable and quite approachable. This book is regarded as the Clustering Bible worldwide, and I've seen copies placed prominently in the bookshelves of individuals in Beijing, Tokyo, Paris, and the US. Microsoft's own Cluster Server was codenamed 'Wolfpack', as an honerable reference to the cover art of this specific book.

Aaron McKee
Clustering Products Manager
TurboLinux Inc.

In a subject which is probably considered dull Pfeister has written a book which is actually entertaining as well as informative.If you are new to high perforamnce computing this book will begin from the basics and teach you all the way.If you are a pro you still will find it a great refernce material worth a read.You are bound to find something new in it.

This book provides a terrific introduction to the hardware, software, and systems architecture of parallel computing, candidly discussing the issues and trade-offs in various approaches. The emphasis is on clusters, but there is lots of information on the whole continuum from single processor machines to SMPs to clusters to distributed computing. Pfister will leave you with a better understanding of things like how SMP machines keep processor caches coherent, what the differences are between SMP, NUMA, and distributed computing, how various cluster products work, real world cluster issues (like system administration), programming models used in parallel computing, and why programming code that runs efficently on these architectures is usually the hard part.

The book is somewhat dated - nothing about Beowolf for example - but the concepts remain valid. Many of the issues are illustrated with reference to mainframe clusters, especially IBM's 390 sysplex, which I found particularly interesting since I don't have much experience with these systems.

The style is highly readable and informal, but not insultingly non-technical. The book is loaded with opinion and insights - it is not a dry textbook of issues related to clustering. Highly recommended for anyone in the business of creating information systems that need to run fast.

While struggling through this book, I spend more time thinking about the characters of this author than about cluster. He has this unique style of telling a subject like a friend telling you a story and it goes like : I am going to tell you this .. but first let me explain why I tell you this .. and now I want to tell you how I am going to tell you this .. and finally this is this, believe you me .. OK, truth is - I lied, it is actually this ... and on and on. He successfully made "this" simple and understandable to a certain degree, but the "how I, why I" portion mix with some high IQ humours did confuse me no end - though it is fun. I find that at some stage I have to use a finger to point to a key sentence and said " OK, Pfister is going to tell me this - lets see how" - then at some stage I will have to judge whether he has finished what he promised and is already on to new stuff. And, he does choose some words that I suspect is more often used in classical literature - rococco, dischotomies, litany, etc - which although harmlessly infrequent, does add some irritation to the already burden mind. All things considered, going through this book is fun. In case you are one of those like me that is quite lost and struggle a fair bit, I did find chapter 6 fairly readable - so perhpas you want to starts from there and work backward/forward if other chapters frustrated you a fair bit.

The only thing I can say is I bought it for my 16 year old grandson and he said it is awesome.

If you read the first book this is an excellent followup to help you increase you understanding of how to build a robot of your own. If you did not a good place is start with the first book Robert Building for Begginers. These books help get you in the thought process needed to build decent robots wather small or big.

This review is by my ten year old Robot fanatic:

This book introduces the most common parts (in a beginner type robot) step by step by defining them properly. So far I have made a line following robot almost from scratch. This book sets you up with many different options. It starts with safety and where to obtain parts then moving on to introducing parts. After that you are shown how to setup a solder-less breadboard.

This book (and it's prequel, Robot Building for Beginners by the same author) is extraordinarily good. It picks up where the previous book (which is the best book in existence for the beginning roboticist, in my opinion) leaves off, getting into details of milling parts, microcontroller circuits, and such. A truly wonderful book. If you read the previous book, and then read this book, you will have an excellent grounding in robotics, and have a very entertaining time doing it. Highly recommended!

I am a novice robot builder. I appreciate the thoroughness and practical approach of this book. I have understood and implemented several circuit ideas from this excellent book.

Books like this are refreshingly down-to-earth after reading the usual college text books.

This book can get you started just in the way you would like to. Mike understands what PB developers need to get started with Web development and Jaguar. Although EAS versions have changed, but the basic concepts suc as "stateless/stateful, instance pooling, transaction support, connection, etc" remain the same. This book is not for Java with EAServer - this is PowerBuilder with EAServer - as the name suggests.

This book was written for PowerBuilder 7 (now 7.03) and Jaguar CTS 3.0 (now Sybase Enterprise Application Server 3.6.1.08). While PowerBuilder hasn't changed much EAS most *certainly* has. When Jaguar 3.0 came out there was no database persistence standard for the Java platform, EJB was barely a spec (v 0.4), and a lot of things that we take very much for granted in the J2EE Specification simply didn't exist. Also, Jaguar 3.0 was a much 'clunkier' system to administer than that newer 3.6.1 release that Sybase has done. While many of the concepts discussed in this book from the PowerBuilder side are still applicable, some of the screen shots and processes are dated on the Jaguar side. Still, the book represents a good history lesson if nothing else. Being that this is the *only* book on the subject of using PowerBuilder as a front end to your Jaguar/EAS server-side code I'd say get it. But it's quickly become in *dire* need of a revamp. Are you listening, Mr. Barlotta??

The site was going to use PB7 and Jaguar - exciting! I ordered the book, read it, used the many fantastic code bits to get an n-tier PB7 app up and running. Fantastic book.

4 months later, the client decided to use Java, scrap PB development and sacked me without even a day's notice. Oh well. I still think Jaguar and the book and PB7 are tops! But the lesson learned is that Powerbuilder is on the way down and out!

I've been developing applications for over ten years. This book stands out as one of the best I've ever owned. It's very honest about how familiar you'd better be with PowerBuilder if you expect to use this book. The author takes into consideration the probability that you're new to Jaguar and yet doesn't 'dumb down' his guidance. It takes you through an explanation of CORBA, distributed processing, and gets you using Jaguar immediately. Excellent coverage of the administration of and development using Jaguar. If you plan on using EAS to build distributed apps, I highly recommend you read this book.

Excellant guide to getting started with Jaguar. Written for those users who know PowerBuilder and need to move to Jaguar. No distributed PB knowledge is required - Barlotta explains everything you need to know in plain english.

The time it will save you in figuring out what you are doing is well worth the cost of the book and more.

The examples in the book are good and source is available on line. The only complaint I would have is the code on the web is not organized in the zip file as well as it could be, but the author mentioned he was going to work on that. A little searching will find the code you need.

If you are thinking of doing distributed or web based applications using Jaguar, buy this book today.

This book covers most everything the wanna be Mac tech needs to know to be able to get into their system intelligently, without making expensive mistakes. It's not preachy or over technical from my standpoint, and it makes a great reference for when you need to tackle a problem yourself, rather than spending a lot of money for someone like me to come out and fix your computer.

I like the bredth and depth of the information given so much, that I am going to use it as the class text in my free Mac Troubleshooting class at Santa Ana College

This book is very good. It is one of the few books that is comprehesive of the entire Mac line (from the original mono-MAC to the iMAC). So many Mac books now only focus on the current models forgetting the earlier ones.

It is arranged by topic (memory, hd, input devices, etc.) and very easy to use. It is also suprisingly accurate. Twice I have found the information in the book's spec tables to be accurate where Apple's own ServiceSource specs were incorrect. (If only I had access to where they get their info!) :-)

Want to work on Macs? Get this book!

This book has really help me. It contains information about troubleshoting, installation, upgrade and more. Good graphics, easy to understand tables and easy to follow instructions.

Tremendous Trememndous. This book helped me upgrade my old SE-30 for use as a networked print server in my apartment. It got me set for networking 7 computers together on a LAN, including the fun ways that Macs talk with Windoze boxes and a Read Hat machine. I love this book!

Shortcuts, ways to speed up the machine, preemptive troubleshooting tips and more interesting info than you could ever retain.

If your Mac's out of warranty, you have nothing to lose by trying to fix it yourself. Stauffer's the man when it comes to clear explanations of needed repairs. I replaced the hard drive and CD-ROM drive following his book's advice. The book paid for itself.

There have been a couple of other books on message passing, but most of them have been anchored to a particular operating system or language. This book is the first to offer a general treatment of messaging, as a way to merge disparate middleware installations.

At the end of the day, messaging technology is just another way to allow distributed code to interact. Blunden takes the time to compare and contrast messaging against other distributing computing techniques. The result is that the reader can understands the relative advantages and limitations of messaging, so that they can use the right tool for the right job.

At every turn, Blunden grounds his explanations using concrete examples, so that the reader has a solid frame of reference (I can appreciate the author's humorous 10-page implementation of a DCOM server, basically to demonstrate how awkward a distributed technology can be... it's no wonder DCOM faded away).

The author of this book has obviously seen combat in the trenches. The fact that he would discuss deployment requirements like auto-update and secure network communication is proof enough.

I particularly enjoyed the bits of storytelling that Blunden hides in between technical discussions. In one part, he talks about working at a company in the throes of Y2K conniptions: "Like a 15-year-old kid studying for an algebra test, the company that hired me had waited until the last minute to do its homework. In September of 1999, the CIO put down his copy of Fortune Magazine long enough to realize that something needed to be done. Angry customers might file lawsuits, which would ruin the CIO's plans for a weekend cottage in Bermuda."

This book does an impressive job of looking at a "niche" of computer science and analyzing it in the backdrop of contemporary production requirements. The book provides an extensive presentation of background theory, a 10,000+ line working system, lucid documentation, and a discussion of alternative improvements and approaches.

To demonstrate the cross-platform/cross-language feasibility of his distribution, the author offers three different client pieces (C, Java, and Perl). This is a round-trip explanation of messaging passing that does a conscientious job of covering all the bases.

This is a very instructive learning-by-implementing book, in the tradition of Tanenbaum's MINIX. Blunden walks one through an in-depth analysis and implementation of a real message passing server.

I'm a little put off, though, by the fact that I find 10 5-Star ratings for this book, all posted on the same date by the same reviewer. C'mon.

I bought this book with the expectation that the Bluebox message server would be a token implementation.

Whoa! Was I wrong; this book shows the full monty! It includes a message server engine, a log server, a database interface, a license server, and auto update engine, recovery facilities, and a heartbeat monitor. Fortunately, the 100 or so classes that make up the distribution are well documented and a user manual is included in the book. The last few sections of the book also have some interesting anecdotes that are worth reading.

Easily the best book ever written on managing complex software projects. Even more relevant today than when it was written, it has been my project management companion for years.

I read many object oriented and agile books published recently. In a Mymocks book store near Townhall, this book is wrapped. It raised my curiosity since it is such an old book. I ordered a used book from Amazon.com and it is still cheaper than the discount book seller in Australia.

Half way through, I realized that Agile process is not a new thing, it exists before it was called Agile, just like AJAX exists before it was called AJAX. Do you know how Martin Fowler called Java POJO? Martin learnt from a joke in this book.

It is book on Agile practice even it never mentioned Agile in the book.

Half-way through this book I decided I wanted to burn every copy of the book. If other people read this book, then they'll all know how to manage object-oriented software projects too!

I swear that Booch was spying on several of the so called "projects" that I was a developer on. It is simply amazing to me how many times the so-called "Harvard School of Business" techniques are used to manage an OO project! I have learned through the school of hard knocks what Booch has written about in this book (wish I had discovered it sooner, a couple of pointy haired bosses could have used it!). Anyway, Booch breaks OO management into seven chapters: First Principles, Products and Process, The Macro Process, The Micro Process, The Development Team, Management and Planning, and Special Topics. I especially found interesting his descriptions on how NOT to run an OO project (oh, and he gives plenty of examples on HOW to run one too!). Booch covers OOA, artifacts, OOD, methodolgies (a biggy with me even on a one person project), evolution (gosh! who would have thought you could have cyclical development???). Identification of classes, objects, symantecs, relationships, etc. He then tackles the team environment: roles and responsibilities (especially the manager's responsibilities!), resource allocation, and tools (this book is not a plug for Rational Rose BTW). Finally: managing risk, planning and scheduling, staffing, costing (a tough one), Quality Assurance (this is not testing!), and he talks some about projects in crisis and what to do. The last chapter is kind of a catch-all containing: User-centric, Data-centric, and Computation-centric systems discussions, along with Distributed, Legacy, Information Management, and Real Time Systems. The appendicies contain: a summary of recommended practices (for those wanting to create a methodology), and rules of thumb. There is a great index, bibliography and glossary to tie up the package nicely. Booch has a terrific writing style presenting what would normally be a dry subject! Definitely for the computer Project Manager's shelf!

I had no hesitation to give 5 stars here. The book is really very good. Honestly, what do you expect with such a book ? To learn valable advices, to understand them, and to have fun while reading. Such a book exists : this one ! How many time I asked to myself "Yes ! What a good idea ... and so simple" or "Of course ! That's it". I really read it like a novel. You can bring it with you for your hollidays (like me), without the feeling to get boring with professional stuff !

Most of the robot books I've purchased rarely explained the detail of how you could create some kind of "intelligent" program and expand it as you need. This book give you an example using pseudo code so basically you could implement it in any programming language usually found in embedded programming such as C, Basic/Stamp or Assembler. I would highly recommend this book for robotics enthusiast who wants to make their robot behave like it has some kind of intelligent.

The book aims squarely at teaching the concepts of behavior based robotic programming without being simplistic or being overly technical. A good example is PID controllers -- the ID stand for integral and differential. He doesn't dive down into the mathematics of it but does point out that those two stages of the controller a not separately tunable.

The book doesn't present a lot of pseudo code nor does it focus on an type of microprocessor or language.

It gives very good conceptual descriptions of how to create architectures that allow multiple sensors and actuators to act together to produce meaningful and emergent behavior while pointing out pitfalls and problems that may crop up. The book is chock full of block diagrams showing the setups being discussed.

I have read dozens of robotics books over the years and most of them suck. They were either too academic or too basic. This book is excellent and was a refreshing change.

Written by one of the designers of iRobots Roomba, this book is indeed a practical guide to robotics. It is easy to read and full of practical advice that one would only get if they spent the last 20 something years working with robots. For example, the author repeatedly warns you to expect the unexpected.

Even though this book incudes access to a simulator tool, the author constantly reminds you of what could occur in the real world. This book is for anyone attempting to build a single-purpose mobile robot (whether as a commercial developer or a hobbyist). Rather than focusing on a specific language or platform, the author uses pseudocode to explain concepts. The pseudocode should save you hours of frustration. At the very least, the authors good sense of humor makes reading the book quite enjoyable.

The book is easy to read and a good introducion to behavior based programming. I always like it when the author uses some humor to turn a book that could have been a boring "must read" into an entertaining experience.

This is a nice little book. It introduces some important concepts in an overall very readable text. Of course the book doesn't offer much technical detail or any real code but sometimes it comes close. If you already have any experience in programming you can easily get the point in the example pseudo codes and adapt them for your own use.
There is a major problem about this book though. The online robot simulation program was available from the link given inside the book but this website is not active anymore so you can not practice the ideas using the "bsim" program.

I adore this book! It is one of those books that I just pick up and flip to a random page, and absorb the wisdom. It is full of tiny little things you can do to make your work look more professional. This guy is amazing.

One-Minute Designer Revised edition Roger C. Parker MIS:Press, 1997

Like it or not, if you use a computer you are a typographer, and that's anyone who arranges words within a given space: letter, report, bulletin, brochure, ad, billboard, book, sign etc. You don't have to be a graphic designer to create good typography because Roger Parker makes it easy to communicate clearly. The book is methodically organized. Each page is devoted to one subject, i.e. column width, placement, type sizes, word and letter spacing, font choice-all 204 of them. Parker writes easily, clearly, succinctly, and is always on the side of the reader, and the absence of verbiage and posturing is refreshing. Each page has direct, easy-to-understand two color illustrations that unambiguously define the text. Unlike program manuals that have incomplete or misnamed subjects, I'm impressed with Parker's contents page and glossary, which makes it easy for the reader to find information quickly. The soft cover book is a comfortable, easy to hold 7" x 9" portrait format. For quick review, the italic captions are printed in red. Text is set in one of my favorite fonts Minion, designed by Robert Slimbach one of the world's great type designers. The generous 11-point size makes is easy to read. This is a book that makes it easy to produce good looking, well organized layouts that communicate, a rarity in manuals. Parker's book should be within arm's length at a workstation, and [for the money], it's money in the bank.

Doyald Young, teacher and author: Logotypes & Letterforms and Fonts & Logos

This book is amazing. It lists 200 examples of good and bad design in a text/title/image/graphic perspective for business documents (which is just like a website). This book is a bible for begining or intermediate graphic designers who want to make the perfectly organized data (newsletters, website, newspaper, etc). Instead of long chapters of boring theory and idealism, it points out common design mistakes and shows a better way to do it and throws in a couple sentences of theory to it. In my opinion this is a must in anyone's library of books.

I bought this masterpiece after I read 'The Non-Designers Design Book' by Robin Williams. The content is much the same, but explored much more thoroughly, with clear examples and well-thought layouts.

If you want to get only one book on Desktop Publishing, THIS IS THE ONE! Don't waste your time with other books.

A paper design is self-explanatory and self-maintaining. This is why Roger Parker was able to write this superb book on design for paper. Web publishing involves collaborative maintenance of a collection of material. So one can never achieve such clarity. Anyway, this is a great book if you want to design some paper stuff and it is also good to think about why you'll never have it this easy in the Web world.

This book has short chapters and a lot of examples. It is a good "second" book for an Introductory SQL course.

This is a GREAT book for foundation skills in SQL.

I used this book to teach myself SQL when I was "elected" to implement an Oracle database system at a former job and have since gone on to become an Oracle developer and DBA. The concepts and techniques learned in this book have served me well along the way. I have taught Oracle development in a technical school, and insisted that they use this book in the classroom. The diagrammatic approach to learning about tables, columns, joins and SQL functions seems to "click" with everyone who encounters it.

I'm writing this review after buying my ?10th? copy of this book - don't loan it out if you need to keep your copy.

I used this book when I needed to pick up SQL fast. I worked in an organization where I had to build Teradata Data Bases and used SQL to select and move the data. The illustrations really help visualize every aspect of assembling an SQL program and how it interfaces with the data base. I still use it today when I need to be reminded of a particular syntax. Don't loan this book out if you ever want to see it again. I did and now I'm buying another book!

I am currently enrolled in a Database Management (Oracle/SQL) class at Boston College. Right off the bat, I knew I was in trouble when we were told the professor would be unavailable for help and most of students in class were computer science majors. (I was taking the class to broaden my computer skills above and beyond front-end web design.)

The textbook in class was the heinously monstrous 1200+ page Oracle 9i The Complete Reference by Kevin Loney. After struggling through many chapters and finding our professor's teaching style very unhelpful, I decided it was time for another resource.

I checked on Amazon ... and found Sam's Teach Yourself SQL in 10 minutes to be semi-helpful. Then at the Harvard Coop, I stumbled upon it - - A VISUAL INTRODUCTION TO SQL. The problem, I realized, was that I am a visual learner and need to see all the schema tables and step-by step actions to describe what happens as I develop queries. This books is key for any layman, like myself. It walks you through very basic (and more complex) problems in an easy-to-read visual approach. While using SQL on the PC, viewing the tables is difficult and this book helps you map out the problems to figure them out. I was especially impressed after emailing the author about a table question and getting a personalized response.

If you are in a bind to learn SQL on your own, this book is great and won't kill you lugging it around either.

P.S. A great addition I found to this book was a Mac client software (that can access Oracle Databases) called SQL Grinder. Like the book, this program is also very visual and the GUI (MAC) clearly reigns over any PC. Sorry Windows users! Thanks for your help, David Chappell! ;-)

This book doesn't assume that you are familiar with databases or the SQL programming language. It teaches you the programming language step-by-step using a graphic approach. A great way to learn SQL.

I agree completely with the other reviewers. This book is has an amazing wealth of information about VRML and will have you making some amazing worlds by the time you are finished. Many important subjects are covered, from beginning to advanced topics. I do agree that there isn't NEARLY enough information about scripting with VRML, just a brief talk of how to do it. Some more examples with this would have been a huge help, but otherwise, I'd recommend this book to anyone who uses VRML, no matter your expertise.

This book is perfect for beginners and those that already now the basics and want to advance further. It has many examples and is written in a intelligent manor. If you are advanced in VRML you may still benefit from this book however when it comes to scripting and adding Java to your 3d worlds you will need to invest in other books.

Even nearly nine years after it was first written, this book continues to be valuable for more reasons than when it was published. If you are still involved in VRML and have some need to learn this language, this book is a complete guide that starts from the beginning with the simplest concepts and shape definitions and then builds to advanced concepts such as textures, lighting, and fog. Throughout the book there are figures of the resulting images and plenty of sample VRML files for all examples. I do agree with the other reviewers that chapter 30, the one on scripting, is really the only chapter that is no longer worthwhile since so many changes have been made to the scripting part of VRML. Other than that, this is truly one of the best written and most instructive tech books I have ever bought. If you are going to study VRML, there is no longer any other book in existence but this one that is worth owning.
The second reason to own this book has only popped up over the last two or three years. Since Xj3D began to come on the scene several years ago as the XML-based open-source replacement for VRML, this book has become invaluable for evaluating that tool's ability to build virtual worlds. In fact, the Web3D consortium's "test files" for Xj3D, which continues to be a work in progress, are VRML files from this book that have been translated into Xj3D. Since the base tags are the same in Xj3D as they are in VRML, if you are able to understand VRML you should be able to understand what's going on in an Xj3D file with just a little investigation into the basic differences. This will allow you to intelligently evaluate Xj3D and determine if you can find any weaknesses or discrepancies in that tool's implementation.

Doesn't take you through the subject in the conventional manner. After the first couple of intro chapters, you can then easily delve into any other chapter for what you need. Very useful as a reference once you understand the basics. A bit weak on using scripts to control and interact with VRML worlds. Other than this minor gripe, a great book.

please informacion acerca de como cancelar