No comments about Hands-On Exercise Manual for LabVIEW Programming, Data Acquisition and Analysis (National Instruments Virtual Instrumentation Series).

2 comments about C# Software Solutions: Foundations of Program Design.

1. If you know Java or C++, much of this book will seem familiar. In any object oriented language, the same basic concepts come thru. Here of course, you see them implemented in C#. At this level, a lot of the code will also look familiar, if you squint a little. The syntax has considerable commonality with Java. No surprise, since it was put together after Java became successful in the marketplace. So for example the Java "import" is replaced by "using". Once you get used to stuff like this, then you can fluently deal in both languages.
   
   The widget library is well fleshed out and easy to start programming in, from scratch. If any of you have ever tried writing a graphics program in C and using the X11 widget library, then C# has a far easier learning curve.
   
   C# has one distinct difference with C++. Multiple inheritance from parent classes is not allowed. Just as in Java. Readers from a C++ background might find this to be the biggest adjustment in thinking.
   
   Keep in mind that no advanced topics are dealt with here. It is primarily an introductory text.



2. This is one of those books that you can know just a little about the programming language and have the author step you the learning process. Plenty of examples, and excercises to work through in order to retain information contained in the text.
   
   The book is presented in a very gradual manner that will allow a novice to come away with a better understanding of C#
   
   If you are already a master at C#, then this book more than likely isn't for you, but if you want to learn the basics of C# and not be dropped of in the middle of generics by the second chapter - this is a very good choice.

3 comments about Software Quality Assurance: From Theory to Implementation.

1. Although written as a college text (the publisher also has instructor manual, syllabus and discussion guidelines, and test material), this book sufficiently reflects real world SQA to be used by working practitioners. My review focus is on the latter use.

   Chapters that will be of interest to real world SQA include Chapter 3. Software Quality Factors (excellent foundation for a metrics initiative), Chapter 5. Contract Review (checklists for proposal and contract review are excellent), Chapters 7 (Integrating Quality Activities in the Project Life Cycle - especially the model for SQA defect removal effectiveness and cost) and 8 (Reviews, which includes supporting templates), and Chapter 11. Assuring The Quality of Software Maintenance, which is an often overlooked aspect of SQA.

   Note that this book has been written to support ISO 9001 and contains chapters that are specifically slanted towards that approach. Included are chapters on document and configuration control, auditing, and attaining ISO 9001 certification. The author also provides solid information on ISO/IEC Quality Assurance standards, IEEE/ANSI Standards, and MIL-STD-498, as well as on common assessment approaches (CMM and SPICE).

   As a textbook the coverage of every facet of SQA from why and what, to testing, metrics and its role in organizations and projects are thoroughly covered. The fact that the material is up-to-date and truly reflects the real world makes this one of the better texts for college level courses because it does prepare students for roles as practitioners.




2. Galin explains why software is usually far harder to test than hardware. The latter usually only has a few modes of operation, thousands at most. While the combinatorics of any nontrivial software package can easily produce millions of modes. Also, hardware defects (like parts missing) are often easy to detect by visual inspection. While software is often inherently opaque. It might have a corrupted or missing module that might not be found until the customer tries to use it. This is exacerbated by bugs being found essentially mostly in development and testing. And not in manufacturing. This latter step is trivial is software, but is the key step in hardware.
   
   His book then goes over the main types of Software Quality Assurance models. These might already be familiar to you. The Waterfall model, which forms the basis of most SQA standards. But for small software projects, you might be able to use the Prototyping model, which can be faster. If you have a complex project, then maybe try the Spiral model. Here the spiral is a useful metaphor that indicates a hopeful convergence of the project at the centre of a Spiral chart.
   
   Then there is the Object Oriented model. Which takes its inspiration from the rise of OO languages like C++ and Java. As you build up a library of classes, then the more useful this model becomes, at the project level.
   
   Each of the above models is concisely explained. The entire book has this flavour. With a continual emphasis on metrics, as these are crucial to permitting an objective assessment of your project. In some ways, without taking sides as to which model you might adopt, the book seems to suggest that doing the metrics may be at least as important. So that you get some tangible idea of how your project is progressing.
   
   It is also nice to see that he gives no mention of Extreme Programming. This is a dead end that was briefly popular amongst some developers, until its disadvantages became apparent.
   
   The book is structured somewhat like a textbook, with questions at the end of each chapter. Certainly useful in focusing your attention. But its usage as an actual text in a university course seems unlikely. Not due to any failing in the book. But simply that computer science departments rarely teach this topic in any detail. Mostly left to industry.



3. Up front, this is one of the most dry and boring techical texts that I have ever read. Reading the book is as interesting as reading your insurance policy. I had (as part of a class that I was taking) to read the book cover to cover and can definitely say that this was a hard experience. The book uses very few examples and for the most part, they are useless. They do not carry a point nor explain any of the material they cover. The material is arranges in a confused way and does not flow from one chapter to another, nor does the structure of the chapters make any sense.
   The reason I give this book 2 stars is that is does cover the various areas that SQA is concerned with. Going over the table of contents would give you enough information to look somewhere else for a better text.

No comments about LINQ for Visual C# 2008 (Firstpress).

5 comments about Intro to Programmable Logic Controllers.

1. I teach a basic course in programmable logic controllers. I have found this book to be a dream come true. While there are a lot of books out today dealing with PLCs most of them fall far short of this book. This is the first book that I have found that covers "Documenting Your System" which is a very important subject that has been ignored by other authors. I highly recommended this book.



2. What the publisher's blurb and the other reviews DON"T say is that this is a LAB MANUAL! If you don't have the appropiate software it's value is very limited. I will be returning it to exchange for a real "Intro to PLC's".



3. I recommend this book to my students who are getting started in PLC programming. It is a good beginner's book but more advanced readers will be disappointed. The reason I did not give it five stars is because the book is a little too pricey for basically being a lab manual. With this book and the PLC drivers at http://www.vhmiautomation.com/PLCCD.html my students have had great success with interfacing to various PLCs also.



4. This is a LAB Manual. It is no good unless you have the software that goes along with it. I will be returning it.



5. Excellent for getting a good training on PLCs. First half is general PLCs and second half mostly SLC500. This is the main book, not the Lab Manual. You can order the lab manual that has the large words "Lab Manual" on the cover. Just to be sure I requested NOT getting the lab manual. I also keep this book at work for ref book.

5 comments about Creating Emotion in Games: The Craft and Art of Emotioneering (New Riders Games).

1. "Creating Emotion in Games: The Craft and Art of Emotioneering" is clearly a guide every video game designer could read as long as they weren't dyslexic or something. And if they are dyslexic, maybe they could get someone to read it to them. Come to think of it, that would be a great pick-up line: "Excuse me... I know we've never met, but would you mind reading this book, 'Creating Emotion in Games: The Craft and Art of Emotioneering' to me? I seem to be dyslexic." In the midst of an everchanging world, it's nice to see that, throughout the centuries, one thing rings true: Games still can be emotional as long they are emotioneered properly with appropriate use of craft and art and creation.



2. I'm surprised by the reviews from people claiming to be game industry veterans who say they've found this book to be useful. Either they're not really in the game industry (possibly PR flaks?) or they haven't learned much in their time here.
   
   General comment on content: Between the massive amounts of interior artwork, the big body type, the big (and frequent) headers, unusually wide margins, and lots of white space, there's probably only about 75 pages of actual information in this "500-page" book. Think of it as more of a booklet.
   
   Mr. Freeman's credits are hard for me to verify. Web searches turn up some titles he's gotten credit for contributing to, but none of them were AAA titles. And there's no way to know for sure how much he actually contributed to them. Having been both a freelancer and internal writer/designer, I know outside writers who've been completely useless to games' development, so a claim of credit doesn't mean much, IMO. I have no clue what expertise he has with movies or other media, but I'm not too hopeful after reading his book on game writing.
   
   One big problem I have with his book is the jargon he insists on excreting everywhere. This isn't game industry jargon, movie jargon, or any sensible jargon that I know of. It's jargon he seems to have made up to try to claim writing techniques and mechanics as his own. And he really, really likes to capitalize the (sometimes excruciatingly long) names of "his" techniques. A sense of impending doom approaches when you first see the word "Emotioneering" (capitalized, of course), looms high overhead when you see such phrases as "Plot Deepening Technique" and "Dialogue Interesting Technique," and crashes down with skull-crushing force upon reading the phrase "Player Toward NPC Relationship Deepening Technique." Ouch. Lack brilliance? Try BS!
   
   How can anyone read a sentence such as "A Character Being Genuine is an NPC Rooting Interest Technique, but not a Character Deepening Technique" without laughing? (And, yes, the capitalization and comma fault are the author's.)
   
   The bottom line is that this book doesn't seem (to me) to have much of value to offer anyone who's been in the industry for any length of time. If you're trying to break into the industry, however, you could be deluded into thinking that you're learning something useful here. FWIW, that's the opinion of someone who's actually been in the games industry since 1984. I keep trying to read this book, hoping to get something out of it, but can't get more than 20% into it before giving up.



3. It does tell you a lot of techniques, but it doesn't tell proper practice. Its ok for game design since the (western) industry isn't very sentimental when it comes to games. Mostly the Japanese are coming out with RPGs with a lot of sentiment. I think its good that someone is trying to help with dry gaming. I do like games like unreal, tetris, street fighter, which have little to no plot, but I don't like to be a weapon of mass destruction without a cause.
   
   The book can be comparable to a core paper-pencil rpg book for storytellers.
   
   As far as "emotioneering," I think its a catch phrase. And many of the dimensions used for creating characters you could get out of a white-wolf book.
   
   Overall, the book is good at telling you how to use techniques for characters and story/plot. Its cheaper than taking a scriptwriting class or a creative writing class.



4. A definite don`t buy!
   This guy takes credit for something that`s not his own and he dares to Trade Mark it!
   Emotioneering is his! Hahahaaaa....
   He just took ideas for other authors that on story,acting,character...etc...
   Some of those authors might be furious about it when some others just rool in the grave.
   I could read only a quarter of it and I realized that I`ve read all this before!
   I feel lucky I didn`t buy it! Fortunately I`ve borowed it for the studio I work in.
   
   Anyways...KnockOff,ShowOff with a flavor of TV Shopping.How cool is that?
   
   Don`t buy.
   
   I am an 2D/3D animator.



5. I have to agree with the other negative reviews given here - this book was nothing more than a fluff filled, gimmick driven, repetition of screenplay advice which honestly isn't even all that good. What primarily irked me right off the bat (besides the horrendous titles and terms) was the blatant assumption the author has that games and movies are basically driven by the same forces, therefore, anything that works in movies would work in games too. They're both visual entertainment right? Poo on you sir, your assumption cannot possibly be wholly correct in that one is an active medium and the other passive. Are you really going to tell me then there are no differences in creating meaningful emotional experiences when the audience is passive in one and active in the other? I couldn't believe that he consistently used movies as examples and not a single real game. Shouldn't a book about games use games as examples? I'm not even going to attempt go in depth into all the basic concepts which were flawed and unsupported by any research - I'd basically end up writing a work as long as his. Just this - reader beware and save your money.
   
   I had to unfortunately read this for a class in my game design MFA and was severely disappointed and angered that this was considered good literature in the field. Its poor scholarship and reads like a time-share brochure, out to entice and enthrall the reader with flashy shiny things without providing any real content.

5 comments about php|architect's Guide to Programming with Zend Framework.

1. Didn't like the way the book is written. I do not understand the point of chapter called 'super ninja secret classes', why not use simply zend_registry? The author sounds so pretentious sometimes, it's really annoying. I've read Zend Framework In Action from Manning and Practical Web 2.0 Applications with PHP from Apress and there are really ten times better and richer.



2. Good book to start with if you know MVC but don't know ZF. If you're looking to learn the MVC model I'd suggest picking up something else along with book. There is some organization and placement talk but I think it could have been even more in depth. One thing I noticed is he refered to things that were in the sample code and not in the book directly. So if you hadn't downloaded the sample code and worked with it you wouldn't have known what he was talking about. Also the books editing was so so, as there were a good number of typos and thing improper english. But all and all if you want to see how Zend Framework functions it's a great starter piece for that.



3. Although there is some good information. You have to fight the book to get to it. Some of the code examples are broken. Nothing major, but when you buy a book to learn new coding techniques. It helps to not have to troubleshoot the example code. ( plus the author names the application directory "application" but in his paths he refers to it as app ). Also there is only one reference that I saw that points you to the example code. Maybe I missed it but I looked again before I wrote this, and I only found it listed once and within an explanation of some code. Since he doesn't print the entire files in the book and points back to the example code. I would think that you might make a bigger deal about making sure you download the example code. I don't mind not having all the files printed out. But if you going to do it make easy for the people buying your knowledge to follow.
   
   Also when showing you the code example the author doesn't give the file name that you are looking at. So you will be looking at code and you dont know if you are looking at Controller code model or view code ( although view code usually has a lot of print( echo ) statements )
   
   If given the chance to do it again. I would not buy this book.



4. I purchased this book, despite the negative reviews. As other reviewers have already mentioned, the book was poorly edited and several errors exist in code samples. The sample application is esoteric for a general guide. I'm not saying we need another blog tutorial, but jumping into consuming web services certainly doesn't consider what most readers will want to know.
   
   Discussion of the flexibility provided by the Zend Framework in comparison to other PHP frameworks is missing. I also think more references to generally accepted MVC design best practices should have been included.
   
   The Model chapter gets off to a good start describing conventional thought on data modeling in MVC but the rest of the chapter doesn't support the introduction. I did find the Data Access chapter helpful and appreciated the mention of Data Profiling.
   
   Until more ZF titles are available, I recommend reviewing the Zend Framework documentation and available blog posts.



5. Don't bother.
   
   I ignored the advice of others here and ordered this book anyway, mainly because it's the only book in print on the subject. It sucks...bad.
   
   I got the book this afternoon and had the RMA paperwork filed before bedtime. No thanks.
   
   Super thin on information, and it's not even basic of information. Lets skim the surface of some pretty important concepts and libraries, shall we? At least thats how it felt to me.
   
   The database chapter was the final straw for me. You're introduced to the basic db library then promptly directed to the online documentation for all the REAL db libraries that likely even the most trivial of web apps would require.
   
   Good job Nanobooks on being first to market, but don't pat yourselves on the back too soon. You may have hurt ZF more than you're helping it with this book.
   
   If you want a better (albeit not perfect) introduction to the Zend Framework then go check out Mannings Early Access Program and download 'Zend Framework in Action' (or pre-order here). A lot better footing after reading that plus some time spent with the ZF online docs.

5 comments about PHP 5 Objects, Patterns, and Practice.

1. Overall a very nice book. Certainly not a replacement for either "Gang of Four", OO design and PHP books, but a nice compilation. Don't expect any ground breaking strategies or patters. Good book for a person who wants to know HOW to use patters specifically for PHP. Pretty vague on WHY.



2. Zandstra has created a masterful overview of OO for PHP and provides the patterns to go with it. However, the code presented in a number of sections is far from self-documenting, particularly the Enterprise patterns section. A really great additional feature would have been to tie up, broadly, how the patterns interact with one another at various layers of enterprise design; as the book is written, it becomes hard to keep track of all of the objects Zandstra has created over the chapter, and many times he generates a new version of an old object without presenting a full overview of the newer version, making it difficult to see what his revision has actually done. A good example of this is during the ApplicationController pattern, when he rewrites the FrontController object.
   
   I appreciate the practical examples presented throughout, however, and the sections on UML, OO and Practice will very definitely help novice to intermediate designers.



3. This book does borrow heavily from the "Gang of Four" book as other reviewers have mentioned. But the latter is the definative book on Design Patterns.
   
   I would recommend buying both books as they do complement each other quite well. The examples in "PHP 5 Objects, Patterns, and Practice" tended be be a bit obscure but were clear and practical.
   
   I recommend this book.



4. The book gives an excellent introduction in object oriented programming (OOP), even when you want to learn OOP without using PHP. They first describe a clear problem and then show why and how OOP can be used to create a better solution.
   (Note that I already had OOP Java knowledge before reading the book.)
   
   The second part of the book focuses on Design Patterns, which I sometimes found not clearly explained; problems unclear and definitions not explained. The OOP part was clearer.
   
   The last part focuses on external tools to ease php programming, like testing, documenting, automatic deploying etc.
   
   A major problem about the book is that it focuses a lot on OOP and design patterns without simply showing how this can be directly applied on a webpage or website. The end of part II feels more like how to make a complete PHP Enterprise framework from scratch yourself, with a lot of details making it a bit hard to crasp. It will take a lot of (initial) effort if you want to apply the enterprise patterns described in this book. In a real project, you probably won't even make a complete framework like this yourself, but take an existing framework like CakePHP of Zend Framework, something where the book doesn't talk about....



5. Its probably one of the best books for understanding php5 concepts. It describes each and every feature of php5 with appropriate examples and is quite easy to comprehend.

5 comments about Beginning SQL Server 2005 for Developers: From Novice to Professional (Expert's Voice).

1. With the first chapter, you will learn details and techniques how to install and configure SQL Server 2005 for different editions. The second chapter inroduces the new client tools to interact with SQL Server 2005.
   To understand the concept and techniques of databases, the author walk you through a real world example to apply these concepts. This is a perfect way to relate what you lean to a practical complete project.
   The book ends with the advanced features that were added to SQL Server 2005 compared to SQL 2000. There is also a detailed chapters about security configuration for the installation and post installation phases.
   I will recommend this book for beginners and professional users as well.



2. WOW! I picked this book up with hopes of learning SQL and databases in general. I read Microsoft MCDBA book and also half of Microsoft 2000 SQL Server Unleashed Second Edition. I still wasn't clear about certain things. This book simply is amazing. I couldn't put it down and first day, I stayed up until 3am reading it. I am on page 200 right now and so far, I understand every topic written so far. The author does excellent job in explaining everything in VERY simple form. He tells you things that you need to know. The book starts off with introduction, then it moves on to Installation of SQL 2005 server. While you read the book, you are building database for financial company/bank from scratch, so this is really nice because you gain experience in doing it if you don't have a chance to work with it at your job. While you are creating database/tables/etc. the author shows up two ways of doing it. One with SQL Management Studio and then he shows you how to do it with T-SQL. The cool thing about the approach is that author goes over T-SQL code line by line explaining VERY clearly what it does. This is very nice for someone like me who doesn't have any programming experience and becomes confused the second I see code. I would strongly recommend this book to new people who just want to learn SQL and how things work. It's great. I am very happy with it. I read many technical books, with my favorite author being Mark Minasi. This book is written in same simple, easy to understand language.
   
   Get this book, setup virtual machine with server 2003 on your computer, download 120 days evaluation version of SQL 2005 from Microsoft website and you are on your way to go. I assure you, you will learn something and you will have fun doing it!
   
   Great job Mr. Dewson. I will search around and purchaser more books written by you!



3. 'Beginning SQL Server 2005 for Developers: From Novice to Professional' by Robin Dewson is a nice guide for someone new to working with SQL Server. While the content within is alright, I feel there are better books out there on the market for introducing this concept to developers. The title of this book says 'SQL Server 2005' but I don't find a lot of specific examples within, the chapter breakup is odd at times (chapter 8 is HUGE compared to all the others -- 14 in total), and I just don't care for the layout or writing that much.
   
   It's not a bad book, but it's not great either. Pick this up if you like Apress books, else look elsewhere.
   
   ***



4. This book was assigned reading for a SQL Server 2005 certification course that I am taking. It is well-written with a clear and concise database example that is followed through the entire text. The code that was given was not only good for teaching but I was also able to implement it in project work. It also has a pretty good beginner tutorial on Reporting Services and this book also goes into the basics of T-SQL.
   
   A deficiency that I found was there was discussion on triggers and sprocs but nothing at all regarding functions. Also, I think there should have been more time spent on indexes. I had to use a different reference to gain a proper understanding of the differences between clustered and non-clustered indexes. I also think that there should have been a few pages devoted to XML since it was mentioned in the book in quite a few places without proper introduction.
   
   All in all, this book is worth the buy if you are a beginner using SQL Server 2005 functionality.



5. Beginning SQL Server 2005 for Developers: From Novice to Professional
   
   This book did an excellent job of walking through all the basics required to get a beginner up and running with SQL Server 2005. I worked through the entire book and completed most of the sample exercises. The layout of the book made it easy to decipher between textual content and the steps the reader can try out.
   
   Before reading this book I had some hit and miss knowledge of SQL Server. Having read this book, I feel that some of the gaps in my knowledge of the subject have been filled in and now I'm ready to move on to more advanced SQL Server 2005 topics.
   
   I would definitely recommend this book for the individual who is new to SQL Server or SQL Server 2005!

4 comments about M Programming: A Comprehensive Guide.

1. M is a delightful applications language. Recently I've been struggling with C++ STL, trying to use the "map" container to get perhaps a tenth of the functionality you get from an ordinary M variable, and, believe me, I miss M.

   This is the M book we've all been waiting for, and it delivers exactly what it promises. It is, as the blurb says, "the only source M programmers at all levels need."

   The style and presentation reminds me a little of Stoustrup's book on C++: the organization and style are tutorial, but not elementary. It is up-to-date with the current standard.

   What I particularly admire about it, and what is all too rare in computer books (especially those written by professors of computer science) is that it displays an intelligent awareness of real-world commercial implementations of M. Too many books either describe a pure-standards abstraction on the one hand, or a specific vendor extension on the other. Walters identifies popular M implementations by name and calls attention to variations where appropriate. Like M itself, Walters' book is directed at real programmers trying to solve real problems in the real world.

   There are a few places where one can see that the book is an (extensive) rewrite of his older book, rather than a completely new work. I thought it was harder to locate the "argumentless DO" than it should have been, and I felt there should have been a coherent discussion in one place explaining the (historically weird) relations between the various forms of DO, and when $T is and isn't stacked. Similarly, it is disconcerting to see on page 199 that the "NEW" command is described as a "recent extension... not yet formally included in the standard." These are cosmetic problems that do not seriously mar the book I've been waiting for.




2. This book provides the needed instruction for a beginner with no knowledge to learn the fundamentals of M programming. Combine the book with a free M program downloaded from the internet and you are on your way to becomming a beginning programmer.



3. This book does a good job of explaining the reasoning behind the language's (sometimes strange) behavior--most of the time, anyway. The book suffers from numerous typos in the code fragments. Also, it would be nice to have a nice reference section where each command's syntax is explaned succinctly; this is important, especially because M is not a free-form language, i.e., the white spaces are significant.



4. Was trying to write a mumps interpreter. This book ended up being not so useful. Early in the book, he has a completely wrong definition of "bootstrap loader." This bothered me, because mumps is such an old language, you would think someone that knows mumps would know about the meaning of that phrase. In any case, I believe the author knows Mumps completely, but I did not find the book energizing or inspiring.