5 comments about Programming Windows Security (DevelopMentor Series).

1. I find this book amazing; it has the best of information i could find on this topic in one book.
   The topic on IIS and COM+ helped me learn a lot and taught me some design flaws i had in designing few apps for IIS.
   i would recommend every developer to have one in there shelf.



2. Keith Brown's book is a refreshing change from the 'stick in something about security in a side-bar' approach taken by so many authors. Finally a book which explains lucidly what amounts to a very complex topic; and does so in an understandable and enjoyable fashion. If there were 6 stars on the rating scale then it would get a 6...



3. This book does an excellent job of explaining Windows security at both the architectural and code levels. It's well written, even to the point of being entertaining at some points. Which is a lot to say for a security book.
   
   The book covers topics at a remarkable depth without feeling overwhelming. Though it's light on strict reference material (which is easily made up with the MSDN) it still has reference value because of the deep level at which subjects are covered. In particular, his coverage of network authentication is excellent. Which is fantastic because this is such a frustrating issue in practice.
   
   Definitely worth a look for anyone who wants to understand Windows security APIs at a deep level.



4. This is an excellent and well-written book on a topic that - sadly - shouldn't require a guide to be understood. The complexity and obscurity of Windows security APIs makes it somewhat of a futile attempt. But that doesn't mean you shouldn't be one of the few elite programmers who do comprehend it. In other words, highly recommended.



5. This book is a rare example of excellant background material and real world examples. The author's understanding of the intracacies of the Windows security model is unmatched. The writting style is easy to follow and even from time-to-time funny.
   
   The text is so chocked full of keen insights, I find something new everytime I re-read a chapter. If you're working on a project that requires understanding Windows Security (and what windows project doesn't), I strongly recommend you grab a copy of this book.
   
   There is only a single criticism I can make about this book, and that's about the binding. The cover is poorly attached stiff paper. After reading it a few times (ok, maybe a few dozen times...), the cover came off, and needed to be reattach (twice). The book now looks like it has been through a battle. For a reference text of this importance, hard cover binding would have been more appropriate.

No comments about Software Testing Practice: Test Management: A Study Guide for the Certified Tester Exam ISTQB Advanced Level.

3 comments about Pro SQL Server 2005 Integration Services.

1. Not sure how to study it since there is no source code to download. I can not believe it.



2. I've read several books on SSIS and this is by far the best yet. Explains it at a more advanced and PRACTICAL level than the others while still being easy to follow. Higly recommended. Source code is available at apress.com.



3. Not sure why even one reviewer can rate this bad, this author is awesome. He is very encouraging, he had me drawn by his enthusiasm and love for SSIS. I am still making my way through the book, but wow, I am truly impressed, not only with the way the author elucidates the info, but by the power of SSIS.
   
   Microsoft rocks......

3 comments about A Tester's Guide to .NET Programming (Expert's Voice).

1. I can't say enough nice things about this book. It is wonderfully written, beautifully organized, and chock full of details that everyone involved in software development and testing should know. It is also extremely practical and hands-on. If you are developing .NET software or testing it, you should stop what you are doing until you get your hands on a copy of this book and read every word. I've been a developer for over twenty-five years and learned hundreds of things from reading this text, yet it seems like it would be very easy for a relative beginner to get as much out of as I did because all of the explanations are plain and fairly simple.



2. This book is absolutely targeted to software testers. This isn't an in-depth discussion of why one should use C#'s "as" keyword for safe casting, nor will you find details on asynchronous communication. What you will find is a quick coverage of enough basics to enable testers to start hitting web services, Windows and ASP forms, and even deal with basic COM interoperability
   
   The book is well-written, concise, and in a good voice. The authors carry a common project through much of the book, using the development of a bug reporting system to lay out .NET fundamentals. They use a nice building block approach along the way, starting out sections with the extreme basics and moving on to mid-level topics. (You won't find anything particularly advanced in the book, but again, the focus isn't on pointy-headed developers, it's on pointy-headed testers.)
   
   There are several things I don't care for in the book, mostly from a software engineer's viewpoint. One thing would be the authors' notion of code reuse via copying in code or classes vice simply referencing a different assembly and keeping code in one central spot, but that's from a SE's viewpoint...
   
   This isn't a book for any developer to fool with, but it's an invaluable book for testers looking to learn programming in .NET, specifically tailored for their work as a tester.



3. This book is well written, with enough demo code to appeal to those testers with programming experience, yet understandable for those less technical. The organization is superb, with appendices to provide more in-depth information and quick reference, allowing the more experienced readers to jump right to the areas of interest. Definitely a valuable tool for anyone involved in testing .NET applications.

5 comments about Zend Studio for Eclipse Developer's Guide (Developer's Library).

1. I don't usually write negative reviews, because usually there are plenty of reviews already there if a book isn't being well-received. In this case, though, because it's new and because I'm having to spend a lot of money to find the "right" book on this topic, I thought I'd try to save others the expense. Save your money here. I stopped reading this book halfway through when I kept having to refer back to the "User's Guide" doc that comes with ZSE (which also has color figures making it easier to recognize the text descriptions).
   
   I would have given this book at least two stars for including a sample app (which the Zend user guide does not), but the app doesn't work! Even after correcting several typos in the sample app's code, you still get a fatal error (which I suspect has to do with a missing include path, but I shouldn't have to troubleshoot book code).



2. The help files that you get with Zend Studio for Eclipse covers much the same info and covers many topics that are only glossed over in the book. Most "chapters" are less than ten pages. One of the "longer" chapers in the book is the chapter on configuring your program preferences. That chapter is only 17 pages long and should have been shorter because it could have been condensed down into a few tables. So much of the text was wasted on instructions to tell you where to click the mouse. If you need to be reminded to click on "Save" buttons, maybe you shouldn't be a programmer.
   
   The back cover annoints this book "The definitive, comprehensive guide to Zend Studio for Eclipse." That's a bit of a stretch. It'd be more accurate to say this book is an intro to Zend Studio for Eclipse and a few related topics. I don't regret buying it because it was helpful to me. It did what I needed it to do, which was get my jumpstarted on my transition from Zend Studio IDE to Zend Studio for Eclipse, but if you're looking for a real reference that you can study and re-use, save your money. This book is basic and stops where a real reference book would have started from.
   
   By the way, the book is considerably shorter than the 216 pages that's listed. It's approximately 200 pages including blank pages and the index. Cut out the blanks and the index and it'll weigh in at a slim 174 pages.



3. Computer libraries strong in Zend Studio for Eclipse for PHP/LAMP developers will find Zend Studio for Eclipse Developer's Guide an excellent survey of the core techniques and terminology that make up Eclipse applications. From code editing and galleries to unit testing, debugging and more, Zend Studio for Eclipse Developer's Guide is an outstanding addition to any Eclipse developer's library.



4. I've never been a big fan of Eclipse but I now use Zend Studio so I had to get used to it. I could not have done it without this book. Eclipse operates so differently than any other IDE I've used that it was like visiting a foreign land but this book was my translator.
   
   Thanks Pete and Ian, I owe you guys a beer if we ever meet in real life.
   
   =C=



5. I cannot recommend this book to any target audience.
   
   For experienced developers the book lacks any detailed information on how (for example) to get remote debugging working or to integrate any version control software. The sparse overviews provided have nothing you won't already know if you've ever used any IDE.
   
   For beginners the book is rife with the kind of errors (the text does not agree with the sample code or images) that will drive them crazy.
   
   The writing is clumsy and full of grammatical and spelling errors. The actual information doesn't go at all beyond what you can get by simply browsing the help files you got with Zend Studio for Eclipse.
   
   Other than being able to read this away from the computer (not the most effective way to learn an IDE) there's no value to this book.

5 comments about Game Physics (Interactive 3d Technology Series).

1. Undoubtedly this is a must-have for people who are serious about developing real-time computer graphics simulations with physically based modeling.

   This book can be compared with Coutinho's "Dynamic Simulations of Multibody Systems". I believe the latter covers more materials, but Eberly's is easier to read. The book would be almost sufficient if you also have his previous book "3D Game Engine Design".

   I am not sure why the author wrote chapter 4 and 6. I suppose these can be left out. It would have been more compact.




2. My interest is physics and physics simulations, not gaming per se...so my observations should be viewed in that light.
   
   The main problem with this book is the treatment is incomplete, superficial, or just wrong (from a physics/math point of view), and the typical programmer/computer scientist is not likely to know it. I am reminded of the great fluid dynamicist von Karmen's definition of an engineer as that person who perpetuates the mistakes made by the previous generation. The REASON a game programmer can get away with this is that he is not testing his results by real experiment...his world is a computer generated simulation with arbitrary approximations to physical laws that the programmer deems to impose.
   
   The other problem is that there are usually a multitude of techniques that one can pick to solve a given mechanics problem...and what would have been really valuable is if the author had shown why a particular method is better (for example, Newton's Laws vs. Lagrange's Equations) when the time comes to code the algorithm. We are not looking for Eberly primarily to teach us physics (but if he makes the attempt, it should be correct!)-that is always going to be the job of physics courses. Instead, he needs to tell us which method is useful for coding and why-this, sadly, he has not done.
   
   As an illustration of what I mean...look at how Petzold in `Programming Windows with C#' discuss the elementary process of using GDI+ to draw a curve. There are two approaches, using rectangular coordinates, or using parametric equations (polar coordinates). Petzold explains WHY the parametric approach is superior from a programming point of view.
   
   Any advanced sophomore or junior physics student will know most of the physics presented here (classical mechanics)...but in addition, they will also know the CORRECT statement of conservation of angular momentum (the author got it wrong) ...AND they will have a deeper understanding, because they will have likely studied something like Marion's Classical Dynamics which is rigorous and physical. Especially egregious is Eberly's twice incorrectly defining an inertial reference frame. In classical mechanics, an inertial reference frame is one in which Newton's laws are valid.
   
   Same comment for the math...The math is maybe sophomore/junior level (except for the Quaternions)...but it is not rigorous nor is it motivated, and sometimes it is wrong. Compare Eberly's terse treatment of the delta function with Marion's motivated and physical discussion. Also, we see things like interchange of limits and integration, without explaining when this is mathematically legal. Then there is the unmotivated vector spaces treatment. Eberly goes to the effort to define a field, but then restricts his definition of a vector space to having real coefficients...Then why bother defining fields if you are not going to use them. We are given the mathematician's definition of the determinant (i.e., the unique, alternating, n-linear function with identity) but this is completely useless from a computational view! If Eberly wants to present some advanced linear algebra, then some tensor analysis would have served the game programmer better, as it is often used in continuum mechanics and fluids, neither of which are discussed by the author. He had a perfect opportunity in the Affine Algebra chapter when he stumbles upon the Levi-Civita tensor, which he then dismisses as unimportant! The Affine Algebra chapter is really bad from both a physics and a geometry view. First, a physicist does not think of a vector as something with direction and magnitude, and a geometer is more inclined to think of them as a derivation. Second, affine spaces are too weak a tool to use to distinuish points from vectors, though we do mod out the origin..this really needs a manifold with vector fields and parallel translation. Third, linear algebra is the study of vector spaces and isomorphism.
   
   There is a chapter on numerical methods, but again incomplete! We should have at least got Numerov's method and some Monte Carlo techniques.
   
   The chapter on shading is ridiculous from a physics point of view. Essentially we have Snell's law, and a cursory reference to Fresnel and that's it...Evidently, the author was not up to discussing some real physics ala Maxwell. Why spend so much time on classical mechanics, and then almost totally dismiss optics with a non-physical discussion? We don't even get Huygens principal. But we do get a wrong definition of polarization of light.Thankfully, he did not try to define helicity.

   In summary, this book has two uses:
   1) It presents a list of physics and some numerical methods which the game programmer will find useful, and which he will then go ELSEWHERE to actually learn. (I can recommend Landau (of OSU, not Russia) "Computational Physics" and also the CUPS Physics Simulations books for excellent starters.)
   2) There is the happy possibility that a budding game programmer, in his pursuit of the knowledge to build a better computer game, will discover the much more interesting game called Physics.




3. I always love it when scientists and engineers, and mathematicians come along and review a game programming book. They go "oh! This is just ALL WRONG!!! AHHH!!!"
   
   Please keep in mind this book is for physics simulations for video games. We can't yet simulate the universe on an atomic scale in a PC game and expect a frame rate of more than 1 frame per millenium at this point in time.
   
   I own all all of Dr. Eberly's books and I find them all my most useful books. The only other graphics book I use alot is my Graphics programming by James Foley. The nice thing about Dr. Eberly's book is that the code for most of this is on his website, so if you get stuck on how to implement something looking at the source code can help you further understand the maths and equations. I recommend to buy this if you are willing to put in the effort to understand the maths, but if you have a phd already you might not need it than.



4. This is a great book on physics simulation, covering most of the mathematical methods and tricks. Some people would complain that's very mathematically intensive, but I don't see another way to do it without being superficial. This book, however, goes very deep in almost every aspect of rigid body simulation, and covers some aspects of non-rigid body simulation as well, which is an emerging trend.
   
   I would suggest only one change to it: there's a chapter on shaders which is pretty much useless - it's very superficial as it doesn't teach shader writing, and doesn't teach hwo to use shaders for physics - I'd suggest that it be changed to include GPGPU methods for physics instead.
   
   Other than that, the book is great, and the only one I've seen that actually covers heavy-duty, real-world simulation and not just silly approximations for special cases.



5. This book has much good information if you know exactly what you are looking for. However, its tone is very dry and academic and lacks a big picture perspective. It glosses over essential information on mechanics and in just 200 pages covers Newtonian and Lagrangian concepts. There are lots of equations, but the examples all use variables, thus making the examples no clearer than the equations they are supposed to be illustrating. There are no numerical examples at all.
   
   Chapter 5, on physics engines, which the author himself says is the heart of the book, is woefully inadequate. He talks about the equations and features he wants to implement, and shows code snippets for the features, but there is one essential component that is missing - block diagrams and accompanying discussions that illustrate how all of these pieces fit together. A crate full of clearly labeled mechanical parts does not an automobile make.
   
   Next we come to one of my areas of interest and one of the main reasons I bought this book in the first place - Chapter 6, "Physics and Shader Programs". The author certainly hits some fascinating topics - ocean waves, skin and bones animation, etc. However, once again the author skips what is between the basic physics equations that comprise these effects and the implementation of these equations and effects in code. The code that he does show is in NVidia's Cg language. So if you don't know Cg, the code is undecipherable. I would have preferred algorithmic pseudocode. Then I could implement the effects in the language of my choice.
   
   The last four chapters of the book take an uptick in quality. These chapters are strictly on numerical methods, and I can't believe they are written by the same author that wrote the first six chapters. There are fairly good discussions and examples on the subjects of linear and mathematical programming, ordinary differential equations, numerical methods, and quaternions, and also how these mathematical methods fit into solving problems in physics. They are not self-contained tutorials, but they are a good summary and review for the physics student who has already had some exposure.
   
   I really can't recommend this book as anything but a reference. Its merits are mainly the tying of mathematical methods to physics and good basic discussions on some topics. But where the rubber meets the road - answering the questions of "How does one go about building a physics engine?" and "How do I implement physics within the confines of a computer game?" I think that this book is a failure. I give it three stars only because the author obviously put a lot of effort into the work, and what he does write is not incorrect.
   
   If you are interested in game physics I recommend "Physics for Game Programmers" by Grant Palmer. It takes an engineer's viewpoint of the subject and features plenty of examples in Java of how to simulate explosions, lasers, and the motion of various classes of vehicles. There is no discussion of game engines, though. A good reference on college level physics can be found in the most recent edition of Schaum's Outline of College Physics.

5 comments about Project Retrospectives: A Handbook for Team Reviews.

1. "Project Retrospectives" is one of the best written, best edited, most nicely presented, and most useful software books I've ever read. Norm Kerth presents a convincing argument for the value of taking the time to study past projects and learn from them. He then presents a rich tool kit of techniques for helping a project team explore what actually happened, what went well, what caused problems, and what happened that surprised them. Kerth's sensitivity to the complex interpersonal issues surrounding project retrospectives will help any facilitator, participant, or manager get the most out of these important learning activities.

   Despite the value of retrospectives, not every project team will find it possible to spend 2 or 3 full days reflecting on its experience. However, the methods described here can be scaled down so that any team can apply them. If a team doesn't take the time to learn how to improve, it shouldn't expect the next project to go any better than the last one. This unique book is a key enabler for any learning organization.




2. This book is intended as a manual for software developers intending to hold a project retrospective at the end of a large project. A retrospective is a little like a post-mortem. Much is learned during the course of a large project, and a project retrospective is a way to preserve that knowledge for use in later projects.

   A retrospective is different than a post-mortem in that a post-mortem sometimes implies that the project was a failure. Kerth makes it clear that as long as knowledge is gained from mistakes made, and that steps are taken to avoid the repetition of those mistakes, then no mistake is a total failure.

   Much of what Kerth writes about involves the tools and techniques of a facilitator. A facilitator is something like a psychotherapist for project teams. The facilitator's purpose is to get the members of the team, who sometimes do not work closely together either out of circumstance or preference, to share their opinions and observations about different aspects of the project in a non-threatening way.

   A facilitator must be an excellent communicator and should not offer his or her own opinion, only help others to express their own. In Kerth's opinion, much of what makes a project successful involves interpersonal communication and through a project retrospective a facilitator can help a project team improve their communication skills.

   I felt that the book offered some excellent suggestions. In particular, I liked Kerth's suggestions for illustrating to management of the value of a project retrospective. He provides an excellent checklist for preparing a proposal to management.

   I also liked his suggestions for demonstrating to project teammembers the value of failure. One suggestion is to have everyone watch a movie that involves project management, such as Kerth's favorite, Flight of the Phoenix. Another of Kerth's suggestions is to discuss the explosion of the space shuttle Challenger. Kerth suggests pointing out how the fact that four of the five books written on the explosion are oriented toward children shows how our culture shuns failure, and then discussing how analyzing the causes of the explosion helped NASA prevent similar accidents in the future.

   The book is intended for those intent on performing in-depth project retrospectives or project post-mortems. Much of the book consists of specific tips and techniques for those facilitating retrospectives. If I have a criticism of the book it is that much of the book is at a very practical level and that too little time is spent discussing how to make use of information garnered from project retrospectives in future projects.




3. Project Retrospectives is a must have for anyone who wants(or needs)to understand what happened on their last project. If you plan to conduct a retrospective, the book will show you how with exercises to use with your group. Even if you do not run formal retrospectives, the techniques in this book will help you get a more candid view of how things on your project work.



4. Norman L. Kerth is a professional with twenty years' experience in leading project retrospectives. In Project Retrospectives: A Handbook For Team Reviews, Kerth draws upon his extensive body of experience and expertise to crate an excellent and thoroughly "reader friendly" guidebook showcasing the process of reviewing, and revealing how to learn from the successes and failures of completed business projects. Case studies, preparing for a retrospective, leading a postmortem, and the skills for best learning and sharing knowledge gained from past ventures fill the pages of this down-to-earth and highly accessible guide which is especially recommended to those charged with the responsibility of improving corporate departmental and project team performances.



5. Norm Kerth's book introduces the retrospective ritual and a very good description on how and why to do them. Since published, Norm's book has become a mus-read in the field of software and I predict this will stay that way for quite a while.
   
   Project Retrospectives are review and improvement sessions which the project team does at the end of a project. A typical project retrospective takes a couple of days. During these days, there are a bunch of retrospective exercises which can be follows (and are described in the book). These exercises create a safe environment, help the project team remember the past and help them learn from it. An retrospective is not done properly if it doesn't also result in some improvement actions.
   
   I've used Norm's exercises in my own retrospectives and they work exceptionally well. This book is therefore a treasure of practical advise. If you feel uncomfortable when reading the first description (as some exercises might), try not to discard the exercise, but try it out. Often you will learn and find that they work surprisingly good.
   
   In the world of Agile Development, retrospectives have become an essential part of any agile method. These retrospectives are iteration retrospectives (or heartbeat retrospectives). They are shorter, but the ideas are the same. Much of Norm's exercises can also be used in that context.
   
   As mentioned earlier, a must read for anyone serious in product development.

1 comments about Pro SharePoint 2007 Development Techniques (Pro).

1. This book contains the following:(programming code)
   1. asp.net into sharepoint
   2. web parts using ajax.net
   3. sql 2005 reporting services business intelligence
   4. building handprinted workflows(windows workflow foundation)
   5. building a domain specific language for connectable web parts
   6. reusing presentation layers for web services
   7. security- change code priviledges using impersonation etc
   8 infopath
   9 deep tranversal of sql extensions
   This book is for people wanting to know web parts,web services for
   moss. Programming code is interesting. I wish more people
   would give their review.....

5 comments about Software Configuration Management Handbook, Second Edition.

1. This book is the second edition A Guide to Software Configuration Management (ISBN: 1580530729). The change in name is a bit confusing, but the author explains why the name was changed--due to the change in scope, magnitude and coverage of the book.
   
   Apart from the changed title, the most endearing features of the first edition--simple language, clear explanation of the fundamentals and lucid treatment of advanced topics--are still there. The first edition was a book that would get you as quickly up-to-speed on the basics and key issues. The second edition builds on the first edition. The language and writing style is still simple and easy to read. The fundamental concepts and the basic SCM functions are explained in clear and jargon free language. All the good aspects of the first edition are retained. But the chapters are revised, updated and enlarged to include the latest developments and to give a more thorough, comprehensive and in-depth coverage.
   
   The chapter on SCM standards is an excellent primer on the various military and commercial SCM standards. The strengths and weaknesses of each standard is explained. The comparison of four representative standards- EIA-649, IEEE Std-828, ISO 10007 and MIL-STD-973-is very useful and informative. The chapter "Software Process Improvement Models and SCM" gives an overview of various SPI models like CMM, CMMI, ISO SPICE, BOOTSTRAP, Trillium, etc. and explains the role of SCM in process improvement with the help of the SPI models. The chapters on SCM plans, SCM organization SCM tools, SCM implementation, SCM operation and maintenance, SCM in special circumstances give sound and practical advice on the various aspects of SCM from SCM system design, to implementation, operation and maintenance.
   
   In addition to providing a sound foundation on the SCM fundamentals, the book is an easy-to-digest reference to various practical aspects of SCM that are not found in most books and manuals. It is a virtual toolbox of information that can be readily put to use by the SCM practitioners.



2. The first four chapters of this book might be called: "Why do Software Configuration Management." And they are excellent. If these explanations make sense to you, you might implement SCM before you look around at the software project and find that part of the source code is missing, the source code of this sub-routine doesn't match the binaries, this bug that was fixed is back, and any number of other problems.
   
   The next several chapters go into the fundamentals of SCM. This includes such things as the mundane definition of configuration numbers and the reports that need to be issued.
   
   Just when you are getting to the point where you know that this can't be done, the book goes into the SCM automation tools that are available. Chapter 16 talks about the general functions that can be performed by the SCM tools. Finally he gives a list of the most popular high-end SCM tools. (Mr. Leon - in the next edition of your book I'd like to see some comments made about each of these tools. Just a short sentence or two would be nice to help me narrow down the list of likely suppliers.) For low-end (and low-cost, even free) tools, he points you to the cmcrossroads.com web site for a comprehensive and frequently updated list of suppliers.
   
   This book is a valuable introduction to the whys and wherefores of software configuration management. It will tell management what can be expected and if you're assigned to the task, it will get you well started.



3. I am the CEO of a software company and even though I knew the importance of good SCM practices, as a small company, we procrastinated on actually implementing anything formal. Anyway, when the fires got to a point, we decided it was time we took the medicine to get serious about SCM and I turned to Mr. Leon's book for help. I also sifted through a bunch of other books on the topic at libraries and bookstores and was immediately overwhelmed by the seeming complexity and all the jargon. The simple language, the concise explanations and the organization of content in Mr. Leon's book served as almost a how-to-manual for me as we went about implementing SCM concepts in our organization. I bought a couple of copies of the new edition for my two EPMs and they have been unanimous in their praise of this book as well. If you're looking to bring some order into your software development world through SCM, I would highly recommend you start with this book.



4. The book is an excellent addition to your SCM library. This should be you first read if your just beginning in Software Configuration Management. The author covers the descipline well in this easy to read edition.



5. I picked up this book because we recently started a project where management uses the term "SCM" a lot, and I had no real idea of what that means. This book provides a great overview of the ideas and genesis of SCM, and why it is useful. It also provided lots of detail and examples about the ideas presented to really cement them in my mind, and translate them to activities that we currently do. I can have an intelligent, scientific conversation about SCM now, which is exactly what I was looking for. This book is really excellent.

5 comments about Expert VB 2005 Business Objects, Second Edition (Expert).

1. If you are looking for a great deal of practical advice and a working sample on how to build a framework for your application I think you will get a great deal out of this book & the CSLA framework that it explains. I was really pleased with how this framework solves many of the problems that our company wants to solve in our new software design. Having read several articles and "patterns and practices" papers I still had more questions than answers until I read this book. I finally feel like I'm confident enough in a framework that our company can begin writing our new version.



2. Muy buen libro avanzado sobre el manejo de arquitecturas, le dedica bastante a la teoria. A mi criterio le faltaria mas ejemplos, pero sin lugar a duda es una lectura obligada para quien apunte a realizar aplicaciones escalables.



3. I think the book means well, but it needs a lot of editting. The problem? Bad grammar. I'll make up an example of bad grammar: Horses eat apples from trees so that their population can grow. Which population? Apples? Trees? Horses? Two of three? All of them? This type of poor grammar exists so much with this author.



4. This book seemed to jump around too much and did not flow with what he was talking about. Also, there are not really any good examples until the last couple chapters so it is difficult to follow what the auther is trying to get across.



5. I an experienced .NET developer looking to take my skills to the next level through use of design patterns, and perhaps even more importantly, good ways to code business objects that use relational data. Since the title is "Expert VB 2005 Business Objects", I thought I'd hit the jackpot by finding this book... but it has just turned out to be mediocre so far.
   
   I'm on page 113 and I probably won't finish reading this book. Instead of a methodology for the creation of business objects, including creating a business object interface structure, hints on how to reuse as much code as possible within a business object hierarchy while allowing to remain flexible and extensible, and pointers on how to effectively retrieve and store data, I basically got a 600-page long book on how to use a class library that someone else has already created, called CSLA.NET.
   
   Don't get me wrong, the author is obviously highly skilled, and I saw some interesting things in this book, but I want to write my own code - I just needed some help learning how to code business objects like an "expert" and this book isn't fitting the bill like I'd hoped.