5 comments about Object-Oriented Programming in C++ (4th Edition) (Kaleidoscope).

1. One of the very good references for study of Object oriented programming and understanding C++.



2. If you are a professional Software Engineer, this is the manual to have at your desk when you work.



3. I have been a C programmer for many years but had stepped away from it. Recently decided to jump to C++/C# and took a University course on OOP that used this book. The ideas are presented well, examples are great. Even as I take advanced courses I find myself refering back to this book for its examples and clear explaination of OOP theory as well as some of the gotcha's C++ can throw your way. I highly recommend this book, this book is used a lot in into C++ courses and there is a reason. Its Great!!!



4. This is a well written book and explains things in a simple form. Author does not add unnecessary items to examples which keeps things simple when you are trying to learn. For me it was a good refresher for the C programing part and was great at teaching me the C++ object oriented part. It explains how to use C++ and expands on why you would want to do it a particular way in the real world.



5. I have read versions 2 and 4 of this book and still find Robert's writing style to be the most entertaining of all the technical book I have read. His use of illustrations clarifies confusing topics such as classes, pointers, inheritance and polymorphism. I return to read these topics each time I start a job search to refresh myself on these concepts in preparation for interviews.

1 comments about Microsoft Office 2007 in Business: Core Edition.

1. Bought it used yet its practically brand new. The book cover is torn a little is all ;-).

5 comments about Designing for Interaction: Creating Smart Applications and Clever Devices (VOICES).

1. Designing for Interaction: Creating Smart Applications and Clever Devices (VOICES) is good book for me.
   I learn digital medea design so it is good for me.
   What is interation design?
   I don't know well now.
   But I will study more.
   I want be a good designer in this field.
   Be ambicious!



2. The useful information in this book could be condensed into a 10 page article. The rest of the book is just irrelevant or uninformative photos, self evident ideas, and short interviews with designers. There is knowledge for designers between the covers - but not a bookload. This book tells you how to go about researching for design, but doesn't tell you anything about what other researchers have learned.
   If you are looking for a book that helps you decide how to position the controls and labels on your latest widget, this isn't it.



3. I am an aspiring interaction designer and this book by Dan Saffer really nails it for me in terms of laying down a coherent and well-written overview and framework.
   
   This book is essential to the interaction design community in that it defines clearly what interaction design is (and is not) in this early stage of this new industry.
   
   It is also essential reading for all beginning or aspiring interaction designers.



4. This book reads like the author sat down on a weekend afternoon, typed out a draft and simply published it. The text is basically a sequence of obvious statements. In fact, this book is so bad I don't want to waste many words reviewing it. So I am going to randomly select 4 sentences from this book:
   
   - Most applications and devices that interaction designers design have some sort of visible controls for the user to use to manipulate the features of the product. pg 136
   - Designers should be open and nonjudgemental and should not assume that they know the answer beforehand. pg 80
   - It is more important now than ever before that our digital tools have the characteristics of good interaction design baked into them. pg 203
   - The system needs an assortment of responses to deal with a range of situations. pg 38
   
   Believe me, I haven't chosen these lines consciously - I closed my eyes, turned to some page, put my finger down and typed the sentence my finger landed on. The whole book is filled with such drivel.
   
   I wish I could give this item a rating of zero. Spend your money elsewhere.



5. This book is helping me to understand how i need to start to design interactivity for Digital Television. A must-have.

5 comments about Code (Dv- Undefined).

1. I picked up back on Ch.4 after the bus station stop. Very well done, Charles. A labour of love, indeed, very well crafted. I still don't know if Thevenin's theorem is for pure calculation purposes of being. The two parallel puzzle bc. Exit



2. This book is precisely what the doctor ordered; truly, there is no other book that even comes close to this one, in terms of actually capturing the most elegant, explicit essence of what the computer actually is, and does.
   
   This is the standard that all other computer books must now live up to, and I'm sure that no small number of rival authors are a little green with envy. After all, nine years after its original publication in 1999, this book is #27,439 on Amazon... a score that easily outranks the majority of newer books!
   
   It's a classic. I only hope Petzold does updated and, even, illustrated versions of this book. It is the "Cosmos" and "A Brief History of Time" of the computer industry.



3. I can't say enough good things about this book. I've recommended it to friends of mine coming from all levels of understanding. Few times have I been as enthusiastic about a book as I have about this one.
   
   CODE is perfect except for the end. For 3/4 of the book, everything is meticulously and wonderfully detailed. However, in the last quarter, Petzold explicitly focuses on limiting his book to a certain number of pages and gives us a whirlwind tour through some really interesting topics. I'd like to see another 1 or 2 books explaining these to the same degree of detail as all of the early chapters.



4. This book is a true creation of art. It is a must have for anyone who wants to understand how computers work at the lowest of the levels. It starts off with "What is electricity?" and builds up on the design of a truly working modern computer.
   
   Plus, you don't have to be an electrical engineer or have any knowledge on electronics, since the author assumes no previous knowledge on the field. No one but Charles Petzold could have ever written such an amazing master creation aimed at both the knowledgeable individual and the total newbie.
   
   Charles Petzold's writing style is delightful and attractive; it couldn't have been any better. Also as I read further into the bowels of the system, eventually I got these thrilling sensations like "No way anyone could have ever thought about this" or "No way this is possible". The way the text is put together allows for such moments of amazement.
   
   The book is loaded with diagrams. Every single step into the woods is clearly explained and illustrated.



5. This is the best book i've found on this subject. Reading CODE is like sitting in a well-taught class on the fundamentals of signals and computing.

5 comments about More About Software Requirements: Thorny Issues and Practical Advice.

1. Karl Wiegers is the person I recommend all my employees to read. This book is even better than 'Software Requirements, 2nd Edition' by Karl. He gives practical advises together with theory and important references. This book could be used as a tutorial for requirements engineers. One of the best books in this subject area.



2. This book addresses specific topics related with software requirements and the section "10 cosmic truths about software requirements" alone is well worth the read. The definitive book on software requirements remains the "Software Requirements" by the same author.



3. This is an excellent book which discusses the practical aspects of requirements engineering. Is a good companion to the original Weigers book.



4. I found it easy to read and very quickly full of my own highlighted pages and sticky notes for reference. This book will be in my must reread shelf at my desk. Since gathering requirements is a huge part of any quality product this book will help you get your hands around the task.



5. This book is easier to read than the book that it is the sequel to and has specific topics. They may or may not add value to your life, but does add value to the original book to get a little more insight into how real life works on software projects.

5 comments about BusinessObjects XI (Release 2): The Complete Reference.

1. It is a great book to give you an overview of the product from a user's perspective. Recommended for universe designers. Although it doesn't go in detail on best practices. This coupled with reading the business objects documentation online (which is REALLY good) shoulg get you pretty far.



2. I've been implementing and supporting BO since version 4.0.3, so I've read a few BO manuals over the years. It's difficult to encompass all the functionality of BO XI R2 into a single manual without turning it into a multi-volume text. This is a very good reference covering the major ground work of the new BO version. I recommend it as the starting point for all old and new users of BO, especially given the fact that they've totally rewired our favourite BI tool. And didn't it need it!



3. I bought the book hoping to get a sound overview of BusinessObjects - what it is, how it works, and how to use it. Instead, I found a combination of marketing gibberish and user documentation that has been recycled and updated so many times that it no longer makes any sense.
   
   This book might be useful for folks who already know some version of BusinessObjects and are looking for a refresher. But if you're trying to learn what BusinessObjects is all about, this book is a very expensive waste of money.



4. If you are new to Business Objects and need a good understanding of what Business objects does and can do then this is an excellent book. Where I work we have purchased several copies of this book. Doesn't go into tremendous detail on how to do some of the more complicated concepts of Business Objects but is more than enough to get you started.



5. I can see that a lot of work went into this book and it does a pretty good job of explaining Business Objects at a high level. This is a good book for you if you are tentative about working with computers and don't expect to do intermediate or advanced work with Business Objects.
   
   The notion that this book is a 'reference' or can replace a manual is completely off base. This book is a 'primer' not a reference. Any topic that is easily addressable through discussing the GUI is handled, but only for obvious cases. The function reference is incomplete and poorly documented. Insightful examples that make you think, "Oh, that's how you do X (where X is anything nontrivial)" are not found in this book. The kind of situations you will likely encounter if you want to create reports for a real business, are not handled. In these cases you are left to your own devices.

5 comments about Web Database Applications with PHP & MySQL, 2nd Edition.

1. If your having trouble deciding on a book for your php & mysql development buy this book. It covers all major aspects of php and mysql web development and then some. You will find something useful on every page of this book, and theres a good amount of book here.



2. The book got me off the ground with my first client application, a rudimentary database maintenance system. Most valuable were the techniques and thorough understanding required to build a satisfactory security component.
   
   However, it falls way short as a reference tool and could have included a more comprehensive list of mysql functions.



3. I really like this book--direct, no-nonsense, and intelligently written with a minimum of jokes.
   
   One thing that seems strange, that I'm hoping someone can clarify:
   
   In the section of chapter 8 dealing with transactions and concurrency, there is no mention of setting transaction isolation levels (SET TRANSACTION ISOLATION LEVEL command in MySQL). Instead, concurrency is achieved solely by setting table locks.
   
   I can sort of understand this in that the authors are using MyISAM tables. But why no mention of transaction isolation levels using INNODB tables, given that this is the more standard way of dealing with concurrency issues?



4. As usual in text books, there is a lot of useless information that is not necessary, but since writers are paid by the word, this is to be expected.
   
   I wish there was a section on MySQL commands.



5. This is a good book with a nice overview of the stated subjects.
   
   However, I cannot evaluate the application presented because the appendix on installing Easy PHP on Microsoft Windows has SO MANY ERRORS that I simply cannot get this software running. In particular the PEAR installation instructions are just completely wrong.
   
   I will try a Linux environment next, since I can debug better in that environment.

5 comments about Ajax: The Definitive Guide.

1. §
   There is a LOT of code in this 950 page book. I guess there is something here for everyone because there is code not directly related to Ajax but is directed to HTML structure or CSS presentational aspects or to frameworks that may include Ajax conveniences.
   
   In fact, the amount of code may interfere with the author's object of appealing to two very different types of people with this book: Web developers and project managers looking for a high-level view. Except for some intro chapters and the odd breather between 10-15 page code listings, I don't think any project managers *I* have worked with would extract much from the book.
   
   The book has 4 sections:
   Part 1 - Ajax Fundamentals: the basic technologies that could form the core of a typical Ajax application.
   
   Part 2 - Ajax Foundations: approaches to standards-compliant structure, separation of the presentational layer and client-side behaviors. Code code code!
   
   Part 3 - Ajax in Applications: describes the specific implementations of these technologies into Web applications. More code!
   
   Part 4 - Wrapping Up: tips on optimization.
   
   In addition, there are some reference appendices on XML and XSLT; on JavaScript frameworks; on Ajax implementation risks; and most interestingly, a catalog of freely available Web service APIs.
   
   One thing I did not like about the code listings was the use of Prototype style $() function syntax. This means when I see something like:
   var titleText = $('title').firstChild;
   I had to check whether .firstChild was a reference to a Prototype object or a reference to the standard DOM object. If the standard object, it would have been a whole lot clear just to have written document.getElementById().
   
   The book index is actually pretty good. With 950 pages stuffed with content, you will probably be thankful for that!
   §



2. 'Ajax: The Definitive Guide' certainly is definitive. With 950+ pages of content, this book doesn't know the word brevity. Spanning 23 chapters and 4 appendixes, this book covers everything you would want to know about AJAX. From its history to how it's grown to where things are today and in the future, this text is very complete. If you are new to AJAX and want to learn how to use it in an extensive way, this is a great resource. My only qualm with this book is that I feel it is just TOO big in size. A 'Learning AJAX' book at around 200-300 pages would be a great companion book to have on the side, then switching over to this bible-size book would be a good transition. Overall this is written well, laid out in detail, and typical O'Reilly quality.
   
   ***** RECOMMENDED



3. My previous favorite, and most recommended, book on AJAX was the one by Crane et. al. because of it's completeness in covering the subject by taking a big picture view of Web 2.0 rather than just one technology. For developers though, the book by Holdener is probably the one to own.
   
   This book has some excellent information that seems to escape other books on this subject or is found across multiple titles. So even though it is certainly a large volume, I think there is some definite value in having quite a bit of related material in one title. For example, there are insights into JavaScript and use of JSON in programming the DOM (to name a few) that in my opinion made sense to include.
   
   If you are going to do rich, browser-based application work, you definitely want to consider this book.



4. While "Ajax: The Definitive Guide" is certainly exhaustive, it's hard to have confidence in a text so riddled with errors. Other O'Reilly titles I've purchased in the last few years suffer from the same problem: very poor copy editing. In a "Definitive Guide," this is inexcusable.
   
   Furthermore, he author's decision to rely on the Prototype framework is misguided. It saves a few lines of code per page, but one expects a "Definitive Guide" to define, explore, and use the actual objects and methods defined by the language itself, not those defined in one of many, many external libraries.
   
   It is also somewhat comical to read on page 10 that developers, rather than browser vendors, "are to blame for not adopting standards" and that they are "stuck with the mentality of the 1990s, when browser quirks mode, coding hacks, and other tricks were the only things that allowed code to work in all environments," and then to read on page 191 that "Yes, there are always caveats in the world of standards compliance" and that "Example 7-2 will not work in Internet Explorer because Internet Explorer does not support the CSS2 rules that are used to make this work." And on page 187 that "Internet Explorer does not natively support :hover on elements other than . For this reason, instead of using the CSS that will work for all other browsers, we must use this...."
   
   (It's hard not to laugh, too, at a sentence that begins with "To take the file menu example fully to the Web 2.0 level....")
   
   By the time all the errata are corrected and a second edition issued, it might be appropriate for the author to wag his finger at developers who can't yet afford to to be totally standards-pure, but by then the faddish jargon will seem very dated.
   
   And until O'Reilly starts employing copy editors, I'm not buying the first edition of any title they release.



5. i always trust "The defenitive guide" titles from oreilly and this book is no exception , it covers everything in the Ajax world begin with the fundamentals and every related technology , then dive into how using these technologies for real world applications , then covers WEB dervices ,mashups and API , then end up with modular coding best practices during all app developements phases , and the most interesting part is the reference which covers the most popular ajax frameworks , popilar web services api , and what you need to know about Xpath and XSLT .

5 comments about Implementing Lean Software Development: From Concept to Cash (Addison-Wesley Signature Series).

1. This is excellect book for seasoned software developer. I had trouble with some books on XP pushing process as rigid thing ... here in this book there are reasons behind XP process, knowing them allows one to modify process to fit environment... This is just what I needed - this book was excellent investment of my time and money



2. While the book contains many interesting ideas, it is very tedious reading; an in-depth article could have adequately covered the same material. The book is often fairly repetitious with the same story used to make the same point in multiple places. While the title might lead one to expect a fairly "applied" book ("Implementing" and "concept to cash", the actual purpose is to sell you on the concept of lean software development.
   
   The authors like to bring in real-world examples to help bolster their arguments but frequently get the facts or their interpretation wrong. While the authors need not be experts in areas outside their expertise, one would expect that they would fact-check the basis of some fairly definitive statements; here are some examples: "... 16 is the standard number of missiles in a submarine to this day" (wrong since 1979 when first 24 missile Trident sub was launched); "... in 1985 the value of the yen started its steep fall" (actually the value of the yen rose). Nitpicking?---perhaps, but I find them wrong on areas that I know a little bit about, it makes me wonder how well they are doing when citing knowledge that is unfamiliar to me.
   
   The authors belittle an "efficient expert" (the subject of "Cheaper by the Dozen") for believing there is only one way to efficiently do things. They later turn around and advocate that all developers be subjected to inspections---not inspections of their software but inspections of their desks to insure that they are tidy. They opine that a developer with a messy desk will probably be responsible for messy software; do they feel that a little maid-service will massively reduce software defects? (Why is it that morning people and neat-freaks always so self-righteous?). Sounds pretty "one-way" to me.
   
   The bottom line is that you could probably find a good article in print somewhere that would provide you with most of the content here saving both time and money (sounds like the "lean" way to do things). Still you will get some value for your time and money if you do invest in this book.



3. This book brings some discussions around concepts that comes "in a black box". It's always important to review our concepts. To reinforce then, or to change then.



4. This book explains how to apply the lean manufacturing principles developed by Toyota to Software Development. It focuses on increasing the development speed, since a faster speed results in higher efficiency, lower costs, better value for the customer and also drives higher quality. I strongly recommend it as an introduction to the Agile software development methodologies.



5. Implementing Lean Software Development is an essential resource if you want to understand the value of lean software development. It explains the theory of lean manufacturing and how it applies to software development. It contains practical advice for implementing Lean and anecdotes to help you to understand the value of Lean. This is a great addition to the library of any agile developer or project manager.

5 comments about sed & awk (2nd Edition).

1. In a nutshell, if you don't have this book, you are probably not a serious programmer or system administrator.
   
   Both sed and awk have been around for ages, and they are part of the fundamental toolkit of any Unix/Linux professional. Furthermore, there are versions available both for native Windows and for Linux-like environments under Windows (cygwin, MKS, mingw.)
   
   If you are a Perl hacker, you probably use Perl for a lot of the tasks that would otherwise be performed with one of these tools. Nevertheless, they are worth your time.



2. This book is a timeless classic, the information on sed is invaluable to anyone who regularly works with text files or streams (after all sed is short for stream editor). Not only is it very informative it's also a fun and easy read... You'll be seeing uses for sed almost every day once you learn how powerful it can be!
   
   
   The last 1/2 or so is on awk and although it's also very well written and informative it's not quite as useful if you're already experienced with a high level language with excellent text processing facilities like Python or Perl. However, it's work reading even if you keep thinking "I could do this in _____" because sometimes awk really is the right answer.



3. If you want understand all the sed advanced commands, this book is for you !
   
   I recommend using perl instead sed or awk



4. This book is like a big tutorial series, packed with tons of applicable examples. It is not a reference, that's what the man pages are for, although the index if very good. In fact, the combination of the *BSD man pages and this book would give any man all the SED and AWK documentation he would ever need.
   
   SED and AWK are these two very terse programs that, if you don't use them everyday, you tend to forget their syntax and functionality. I am not an everyday user. Before I bought this book, I often visited one of my many SED/AWK bookmarks. After years of using both programs, I never really understood them. I knew just enough to do small one-liners. However, I recently needed to build a fairly complex script to perform an automated OS upgrade via the network. I knew SED and AWK could help me accomplish my task, but I didn't have a full understanding of their potential. That's when I decided to buy this book. I have since then deleted all of my SED and AWK bookmarks.
   
   After studying this book and highlighting the hell out of it, I have a clear understanding of these two tools and how to effectively utilize them.



5. I found understanding/writing sed/awk commands/scripts a daunting task until I bought this book. This book empowers you. I rate it at par with "the vi editor" from same publisher