2 comments about The Ultimate HTML Reference.

1. This book has become my go-to reference for anything HTML. Why do I like this book so much? Let me count the ways:
   
   (1) Every HTML tag past and present is covered in this book.
   (2) Each tag description is covered by telling you the proper open and closing tag, and available parameters;
   (3) An example HTML segment is given on how it's used;
   (4) Whether this is still valid HTML or an old, deprecated tag;
   (5) A brief text description on what the tag is used for, and when you should use it;
   (6) Browser support for the tag, with four browsers covered: IE, Firefox, Safari, and Opera. What version of the browser supports the tag, and its compatibility with past browsers. No other HTML reference that I know has this.
   (7) An index of each tag for quick look up.
   (8) A table of contents in logical segments: HTML Concepts, Structural Elements, Head Elements, List Elements, Text Formatting Elements, Form Elements, Image & Media Elements, Table Elements, Frame & Window Elements, Common Attributes with three appendixes: Deprecated Elements, Proprietary & Nonstandard Elements, and an Alphabetic Element Index.
   
   Now, to the aesthetics. The book is gorgeous. Type is well spaced, large, and laid out beautifully. Each tag is laid out in the same format with shaded areas for quick reference. And the piece-de-resistance, this is a hard-backed book, so when you pull it out of the bookshelf it feels solid and nice in your hand, not like a floppy fish you get with the soft covered tombs.
   
   What this book is not. A text on learning HTML. This is not a step-by-step guide. It is a beautiful dictionary for fast look up of HTML tags when your not sure of allowed options, format, whether it is a supported tag, or what browsers are supported.
   
   Five Stars for exactly what it is, "The Ultimate HTML Reference."



2. §
   
   I strongly agree with the first reviewer that the aesthetics of this book are outstanding. The typography and layout are superb. Astute attention to these simple elements remarkably enhances the usefulness and readability of this book. An important aspect of my own job is transferring the same approach to the visual interfaces of Web applications, so I appreciate the sweat that went into this simplicity.
   
   Since I made my enthusiasm clear, I guess I can belabor my quibbles. I am not sure I would call this an "ultimate" reference because much has been left out. This is not particularly bad since the emphasis of the book is simplicity and usability. Most Web workers will surely want to use this book's approach, with all its fine organization and examples, rather than the W3C specs.
   
   What might you want more of? Well, there is no index for attributes. Each tag, like BUTTON, has plenty of attributes. Knowing what attributes are appropriate and most effective is important. For instance, this book covers the most critical attributes for BUTTON -- but not all of them. It mentions that IE has an incorrect default value for the TYPE attribute. This is very good to know, but even more important to know is that client-side script does not work for Firefox if the TYPE attribute does not have an explicit value of BUTTON.
   
   The world of HTML is fairly simple but can be treacherous. That is exactly why someone moving into this world will find this book a ready aid.
   
   §

5 comments about PgMP: Program Management Professional Exam Study Guide.

1. I like Paul's style very much, so it's a good book for me. The major problem with this guide is the practice questions. I have not taken the PgMP exam, but I expect it to be even more scenario based than the PMP exam. Paul's practice questions are way too old style, memory regurgitation types. The CD replicates the questions in the book, and the final exams replicate the chapter questions, in the memory regurgitation style.
   This is a bad sign I think, because to pass the PMP exam, wannabes need to do a lot of good quality practice questions that are scenario based. I am sure this will be true of the PgMP as well.
   The book does include the content needed to pass, and I like his style.
   Jim SLoane, PMP, OPM3CAC, CM



2. To me, this book is an order to a perfect chaos of PGMP material. What I mean that the material required for the PgMP exam is scattered in bits and pieces across several references such as Program Management Standard (full), PgMP Exam Specifications (full), PMBOK 3rd Edition (pieces), Maturity models (pieces), and so on. This book integrates all the pieces seamlessly at one place, and by connecting the different concepts to each other creates a beautiful big picture of program management that makes sense. The author adds tons of value to the standard pieces. I commend the author for that. I personally don't care if the questions are easy or difficult (nothing is going to substitute for our experience); but the book presents the material required for the PgMP exam in an excellent way. I have gone through many program management books; none of those even come close to this remarkable book...Books like this one don't come that often...Exam or no Exam this book is a keep; a must have...
   Recommended highly.



3. This book is not at all readable; very dry kind of book. But most of all, this book does not help at all in preparing you for the exam. The questions in this book are totally different kind that what you will see in the exam. I took the exam and the questions are largely scenario based. Paul's book will help only about 10% at the most. My recommendation would be to read PMI's standard on Program Management and may be refresh your study from a PMP book like Rita Mulcahy. As such PMI's Program Management Standard book is more readable than Paul's book. Good luck in your preparation.



4. Waste of time and money. Too briefly. A lot of processes names, inputs and outputs don't match The Program Management Standard processes.
   This book can't help to pass PgMP exam.
   
   Serge Goncharov, PMP, PgMP



5. I've read this book from cover to cover and the PgMP exam? Tough! Been there, done that. My recommendation: this book is a must to prepare for the exam just like the Program Management Standard is. I'm puzzled at a couple of harshly negative reviews about this book: useless, waste of time, dry? These words do not describe this book....I have read other books from Dr. Paul Sanghera as well, and I love his style that puts life into even dead boring topics and make them interesting. Same is true about this book. All concepts are explained well and woven together, and there is a perfect logical flow...it's almost like reading a story... If the inputs and outputs for a process are re-organized to help you make sense, and explained why they are there, I think it's a feature and not a problem...
   
   I do agree however that the questions in the exam are much more difficult than the one in the book, but the book presents the material that you must know before taking the exam...In the exam, of course, your experience will count..no book can substitute for that...This material can be obtained from different references, scattered around...but the book does an excellent job to put all the pieces together and integrate them seamlessly... The author should be congratulated for that...Another great PLUS of this book is that it"s organized along the official exam specifications.
   Actually I would recommend this book even if you are not planning to take the exam; it's a great program management book, too.. All program managers should have it on their desk. Program Management Standard will make much more sense after reading this book.

5 comments about The Practice of Programming (Addison-Wesley Professional Computing Series).

1. Apart from Brian W. Kernigham being the author, which automatically makes it a must read, this book is full of real life examples, pointers, and crafty exercises that will benefit anyone from novice to a master programmer.
   
   It's well written in a easy prose to follow; full of great advices, among others, on style, debugging, notation. And will serve as eye opener for those who are just fooling around with high level languages and never had any experience a the lower level language. Were you wondering what exactly is a hash table is, or how does a parser and interpreter work? Well this book will show you the fundamentals in easy to follow examples while teaching you practices that come from years of experience and a lot of mistakes.
   
   The code quality, of anyone who reads this book, will improve significantly.



2. If you've limited yourself to reading only one book about programming, this might be the one. It does touch on many of the down-in-the-details practical aspects of programming, in a compact 200-page paperback.
   
   But I think the authors try to do to much at once, and end up not doing it as well as they could for any specific audience.
   
   Better to look at the table of contents, and then read the best entire book out there on each topic, when you're interested in that topic.
   
   (If you happen to choose chapter 1, then it's just as easy to read Kernighan "in the original": the classic "Elements of Programming Style" he wrote back in 1974 with Plauger.)



3. When I began my first career as a writer, I was constantly referred to "Elements of Style" by Strunk & White. This short, lucid, and concise handbook, written in 1957, has become the most frequently used text to instruct beginning and veteran writers how to perfect their style. "The Practice of Programming" does for software professionals what "Elements of Style" did for writers. In its short 267 pages, "Practice" addresses the basic elements of writing good source code, by consistently adhering to the principles of simplicity, clarity and generality. In a world where poor programming style is all too common, "Practice" reminds programmers that good programming style is just as important as their functionality. It is not enough that source code is executed well by the computer. It is also critical that other programmers can understand and interpret the code as well, especially during the later stages of a project when changes, bugs and integration difficulties predominate. Other books on programming are far better at teaching technique and functionality. This book shows how you can pull it all together to produce elegant, concise and compact code which optimizes both computer and human resources. As a project manager, I heartily endorse these principles to produce software which maximizes scope, cost, schedule and quality performance.



4. This book isn't bad. If you have any formal academic education in the area, you will probably want to just skip the first 2 1/2 chapters: they will have nothing new for you.
   
   The later parts of the book cover enough topics that there will probably be some things to pick up from it here and there. This book will definitely not make your brain sweat; easy reading for a weekend you don't have anything better to do.
   
   On the flip side, it isn't really going to give you any immediately useful skills.



5. This book is perfect for any computer engineer who wants to get more information about programming.

5 comments about C++ Coding Standards: 101 Rules, Guidelines, and Best Practices (C++ In-Depth Series).

1. This book is a very readable reference book. The authors have read several books and condensed the best coding rules to prevent many errors. If you code in any language other than C++, read this book because many of the hints are useful. (If you code C++, then all of the hints apply.) And if you don't like rules and guidelines, then just read the "exception" section provided in each entry to be sure that your code meets the exception.



2. It's Sutter! It's Alexandrescu! It's both of them together! And the dark lords of C++ have combined forces to produce... er, some coding standards.
   
   Yes, another book of best practices. Some readers may therefore be a tad disappointed that the combined fruits of the authors' labours will not be shattering their puny human minds with the sort of C++ that cause lesser compilers to accidentally create black holes that destroy the entire universe.
   
   But let's evaluate the book on what it sets out to do, which is to give 100 bite-sized pieces of advice on C++ coding. And it's very good. You might prefer to see it as an annotated guide to the state of the art in intermediate C++ programming, in particular to Sutter's Exceptional C++ trilogy, which has become sufficiently sprawling that a reorganisation of the material, plus pointers to which book said what, has become quite welcome.
   
   Yes, it's true that C++ is hardly short of books telling you when to pass by value. But take a look at the bibliography - it's a synthesis of all those other tomes (the Effective series, Sutter's own Exceptional series of course, and older books like C++ Strategy and Tactics) plus magazine articles, into a neat and compact whole.
   
   Few of the items are longer than one or two pages. This is good because the advice stays simple, clear and direct. On the other hand, some of the items feel a bit squeezed into the available space, with discussion deferred to the books in the references, which is a little frustrating on occasion. After all, a lot of the best parts of the Exceptional C++ and Effective C++ series and their ilk is not so much what to do (or not to do), but the why behind it. There's plenty of the former, but not so much of the latter.
   
   If you've read any other coding convention books (like those in Steve McConnell's Code Complete) then the first quarter of the book may feel like the same old same old. And of course with there being exactly 100 items, some are more heavyweight than others. But there's definite C++ meat here, in particular with the items on Exceptions and the STL.
   
   C++ Coding Standards is as well-written as you'd expect from the authors - their friendly, slightly conversational writing styles mesh nicely and I couldn't tell who wrote which bits. And it's a great summary and unification of C++ best practices that someone just starting out could easily refer to in their initial forays. Perhaps even more experienced hands will discover a few tips, implications or issues that they hadn't considered before. It could also be a good way to ensure that a team are all up to date on best practices.
   
   Essential for those with a large C++ library? Probably not, but it does the job it sets out to do very well.



3. If you own the 3 "Exception C++" books, do not buy this book. It is just a mirror copy of those. And the explanation in this book is brief. Typically, if you are familiar with the content of this book, it works as a quick reference manual or pocket book.



4. I had high expectations about the fruit of the association of 2 authors that I appreciate but the result did not meet these expectations. Basically this book provides 101 rules or guidelines that you can get for free by looking at the table of content. Each of these rules is then followed by a very short explanation (1 or 2 pages usually). In my opinion, most of them are common wisdom that you can get from other sources. This is it. That is all you will get from this book. For that reason, I recommend to skip this one except if a convenient and compact collection of common knowledge is something that you are looking for.



5. I think this is one of the most useful C++ books one could have if working in a team. Most companies don't have a very large set of coding standards, and every now and then there will be a discussion about which is the best way to implement something. That is the time to when this book shines:
   
   1) You can show your co-workers the page for the related item, and the explanation for the underlying rationale will be so concise, they can read it while standing.
   2) Every item is backed with heavy references to standard works by the top names in C++.
   
   Basically it is a tool for effectively ending discussions in the most constructive way possible.
   
   It's the supreme index into the world of collected C++ knowledge.

2 comments about Learn FileMaker Pro 9 (Wordware Library for FileMaker).

1. Stars quickly introduces the concepts you need to design a truly useful database. Most other books (including the three mentioned at the end of this review) discuss each module of FileMaker separately and in the abstract, similar to the FileMaker User Guide, leaving you wondering how to get started designing your own database. For example, most books defer "related tables" until halfway into the book because relationships are considered a difficult topic, but Stars introduces related tables in a very basic way in chapter 2.
   
   Perhaps the best feature of Stars is that he offers far more practical tips, including pitfalls to avoid, than any other book I've read.
   
   Stars explains how to design a database the way you'd do it in real life. He initially designs an elementary database, then adds more sophisticated features. (One of the beauties of FileMaker is that you don't need to design an all encompassing database in one fell swoop. You can start simple, then add features a little at a time, and adapt existing features to your evolving needs.) He uses many brief examples throughout the book, so there is no problem understanding the examples if you jump in the middle of the book.
   
   I agree with Stars' philosophy that it is hard to learn FileMaker by reading a book cover-to-cover away from your computer. His book is designed to be read while you are near your computer so you can experiment with his examples. FileMaker is well adapted for learning by experimentation. (If you are beyond the neophyte stage, the book is self-explanatory without requiring access to a computer.)
   
   The downside of Stars is that he is not the most articulate writer, so a few explanations are too vague. However, you almost always can understand him by context or by briefly experimenting with his examples.
   
   Stars is much better for beginning-to-intermediate FileMaker users than the FileMaker Bible, FileMaker Missing Manual, or Que Special Edition. Stars has far more practical advice than the first two. The Que book is too difficult for a neophyte and covers only selected topics in depth. Although the Missing Manual is thicker than Stars, it actually conveys less information because it consumes too much space with the mechanics of pressing each button in a series of dialog windows. Stars presents the same info more concisely, yet is even more approachable for a neophyte.



2. Learn FileMaker Pro 9 is a great book for the beginner to intermediate user. I actually reviewed this book for a FileMaker newsletter, and I was extremely pleased with the content.
   
   Jonathan has a knack for explaining technical tasks in a conversational tone. If you are just beginning to learn FileMaker his friendly explanations will be a breath of fresh air.
   
   Jonathan also knows when to turn to others for advice on some of the more technical topics and brings in other FileMaker experts to fill in the gaps.
   
   This book will definitely help provide jump start for anyone beginning FileMaker.

5 comments about Tomcat: The Definitive Guide.

1. Chap 3: Deploying servlet and JSP Web Applications in Tomcat.
   Writing a book about a servlet container whose app deployment methods have most users puzzeled is a challenge. I dont think this book does any better than the online docs (which are bad).
   
   Chap 4: Tomcat performance tuning.
   Capacity planning, now thats one area where my knowledge general and tomcatwise is a little thin - the chapter only list the topics but provide no hints or answers. Could have been interesting but wasted my time.
   
   Chap 6: Tomcat security.
   Locking down with java policy file, unix chroot and bsd chroot, request filter - wellwritten and very usefull.
   
   Chap 7: Config files and their elements:
   Hmm a new way to run the server on lower 1024 ports without root user - why present this now and not in chap 6? A few details from previous chapters repeated - dont the authors two talk together?
   
   Chap 8: Debugging and troubleshooting:
   Only the obvious things - too thin.
   
   All in all i found the chapter on security and clustering usefull but the book as a hole seems to lack a clear structure/vision and some chapters dosent do more for me than the lousy online docs. Configuring tomcat is not easy and this book dosent help much. Never the less i like working with tomcat! :)



2. This book is hopelessly incomplete. I'm always having to augment it's contents with on-line information. I just attempted to determine the difference between "path" and "docBase" in the "Context" tag in the server.xml file but again it struck out. All page 175 says is that "context" configures the web application directory within a host. End of story. I strongly suggest that you look to another source for Tomcat.



3. All of these other reviews, including some of the popular spotlights, seem to be about the first edition with quite a few people saying they were disappointed. I never read the first edition, so I can't remark on its content. However, this second edition seems to have all the details you need to get up and running, and Tomcat is not an area of my expertise.
   
   In many cases Tomcat is a good choice for a web server, and it is well suited as a high performance production web server. It is also a free and open source servlet and JSP engine. You can use it by itself or with other web servers such as Apache httpd. The book is a user's guide for Tomcat, not a tutorial on how to write web applications. That misunderstanding might have had some readers disappointed. Thus, you don't need to be a programmer to understand the book - it is targeted more at system administrators. The following is a run down of the table of contents:
   
   Chapter 1. Getting Started with Tomcat - explains how to install Tomcat, get it running, and test it to make sure that it's functioning properly.
   Section 1.1. Installing Tomcat
   Section 1.2. Starting, Stopping, and Restarting Tomcat
   Section 1.3. Automatic Startup
   Section 1.4. Testing Your Tomcat Installation
   Section 1.5. Where Did Tomcat Come From?
   
   Chapter 2. Configuring Tomcat - shows the various places to look for information about your server, how to find out why things aren't working, and gives you some examples of common mistakes in setting up and configuring Tomcat.
   Section 2.1. A Word About Using the Apache Web Server
   Section 2.2. Relocating the Web Applications Directory
   Section 2.3. Changing the Port Number from 8080
   Section 2.4. Java VM Configuration
   Section 2.5. Changing the JSP Compiler
   Section 2.6. Managing Realms, Roles, and Users
   Section 2.7. Controlling Sessions
   Section 2.8. Accessing JNDI and JDBC Resources
   Section 2.9. Servlet Auto-Reloading
   Section 2.10. Customized User Directories
   Section 2.11. Tomcat Example Applications
   Section 2.12. Common Gateway Interface (CGI)
   Section 2.13. The Tomcat Admin Webapp
   
   Chapter 3. Deploying Servlet and JSP Web Applications in Tomcat - shows web applications composed of servlets, JSPs, and other files, and several approaches for deploying them. It ends with a discussion of the Manager web application, which can handle some deployment operations for you.
   Section 3.1. Hosts
   Section 3.2. Layout of a Web Application
   Section 3.3. Deploying an Unpacked Webapp Directory
   Section 3.4. Deploying a WAR File
   Section 3.5. Hot Deployment
   Section 3.6. Working with WAR Files
   Section 3.7. The Manager Webapp
   Section 3.8. Automation with Apache Ant
   Section 3.9. Symbolic Links
   
   Chapter 4. Tomcat Performance Tuning - some ideas on performance tuning the underlying Java runtime and the Tomcat server itself so that you service requests more efficiently.
   Section 4.1. Measuring Web Server Performance
   Section 4.2. External Tuning
   Section 4.3. Internal Tuning
   Section 4.4. Capacity Planning
   Section 4.5. Additional Resources
   
   Chapter 5. Integration with the Apache Web Server - covers the use of Tomcat with Apache httpd and talks about the several ways of making Tomcat thrive in front of or behind an Apache httpd installation.
   Section 5.1. The Pros and Cons of Integration
   Section 5.2. Installing Apache httpd
   Section 5.3. Apache Integration with Tomcat
   Section 5.4. Tomcat Serving HTTP over the APR Connector
   
   Chapter 6. Tomcat Security - details about what security is and how to improve it in your Tomcat installation.
   Section 6.1. Securing the System
   Section 6.2. Multiple Server Security Models
   Section 6.3. Using the SecurityManager
   Section 6.4. Granting File Permissions
   Section 6.5. Setting Up a Tomcat chroot Jail
   Section 6.6. Filtering Bad User Input
   Section 6.7. Securing Tomcat with SSL
   
   Chapter 7. Configuration - Using realms this chapter shows how to set up an example JDBC domain to talk to a relational database. Realms are lists of users authorized to implement specific sections of your web site. Many of the other configuration changes you can make are discussed too.
   Section 7.1. server.xml
   Section 7.2. web.xml
   Section 7.3. tomcat-users.xml
   Section 7.4. catalina.policy
   Section 7.5. catalina.properties
   Section 7.6. context.xml
   
   Chapter 8. Debugging and Troubleshooting - Ways to look for information that helps discover why things aren't working and gives examples of mistakes that are commonly made but may not be obvious. Also discusses why Tomcat may not shut down gracefully and what to do about this common problem, as well as ways of preventing abnormal shutdowns from recurring.
   Section 8.1. Reading Logfiles
   Section 8.2. Hunting for Errors
   Section 8.3. URLs and the HTTP Conversation
   Section 8.4. Debugging with RequestDumperValve
   Section 8.5. When Tomcat Won't Shut Down
   
   Chapter 9. Building Tomcat from Source - How to compile your own Tomcat in case you don't want to run a prebuilt binary release of it. Gives step-by-step instructions on how to install the Apache Ant build tool, download all necessary support libraries, and build your Tomcat.
   Section 9.1. Installing Apache Ant
   Section 9.2. Obtaining the Source
   Section 9.3. Downloading Support Libraries
   Section 9.4. Building Tomcat
   
   Chapter 10. Tomcat Clustering - Some options for running multiple Tomcat servlet containers in parallel for both fault tolerance and higher scalability, while discussing the pros and cons of various clustering approaches.
   Section 10.1. Clustering Terms
   Section 10.2. The Communication Sequence of an HTTP Request
   Section 10.3. Distributed Java Servlet Containers
   Section 10.4. Tomcat 6 Clustering Implementation
   Section 10.5. JDBC Request Distribution and Failover
   Section 10.6. Additional Resources
   
   Chapter 11. Final Words - Overview of the Tomcat open source project's community resources, including docs, mailing lists, and other web sites.
   Section 11.1. Supplemental Resources
   Section 11.2. Community
   
   Appendix A. Installing Java
   Section A.1. Choosing a Java JDK
   Section A.2. Working Around Older GCJ and Kaffe JVMs
   Section A.3. Sun Microsystems Java SE JDK
   Section A.4. IBM J9 JDK
   Section A.5. BEA JRockit JDK
   Section A.6. Apple Java SE JDK
   Section A.7. Excelsior JET
   Section A.8. Apache Harmony JDK
   
   Appendix B. jbchroot.c
   Appendix C. BadInputValve.java
   Appendix D. BadInputFilter.java
   Appendix E. RPM Package Files



4. Jason Brittain and Ian F. Darwin's TOMCAT: THE DEFINITIVE GUIDE, 2ND EDITION has been updated for the latest version of Tomcat and offers a complete guide to installing the servlet container, from basics of installation to using web applications, securing Tomcat from online intruders, troubleshooting and customizing the program. Any advanced computer collection strong in Java programming needs this.



5. 'Tomcat: The Definitive Guide' is a great resource for all Tomcat programmers and administrators. Jam packed with 450 pages of material over 11 chapters, you will learn everything you need to know. Security, configuration, performance tuning, integration with Apache and building Tomcat from the source, this is a wonderful guide that should be on every Tomcat admin's desk.
   
   **** RECOMMENDED

2 comments about Windows Server 2008 Active Directory Resource Kit.

1. I've received my books on time in perfect condition
   Keep up the good work!



2. Just as Mr. Mulcare wrote the definitive resource for AD on Win2K3,
   Active Directory for Microsoft Windows Server 2003 Technical Reference (Pro-Technical References) he has done it again with this resource kit. His knowledge of the product and ability to pass along critical information on Active Directory is exceptional. Keep up the good work and I look forward to whatever you write for Win7!

5 comments about Facts and Fallacies of Software Engineering (Agile Software Development).

1. I like this book because it lists both well known facts and some that are not very publicized AND Glass backs it up with references if you want to do your own research.
   I do not agree with everything that Glass states, and he readily admits this is the general reaction to this book. In spite of the controversy on some points I liked this book and would recommend it as a good reference for any process improvement team to gain some real world focus on what is possible.



2. I actually agree with most of what this book says. I also like the references, which are for the most part to other books I like.
   
   This book is little more than a list of bullet points. Most of the writing doesn't say anything other than to reiterate the title and then claim that lots of folks just don't get it.
   
   What's missing are case studies, or even arguments as to why the points the book makes are even worth thinking about.
   
   I would recommend reading The Pragmatic Programmer by Hunt and Thomas instead.



3. This book covers all the mistakes we know about, but keep on making regardless.
   
   When it arrived in the mail, I was amazed by how small this book was. It's a short read, but every section is brilliantly distilled to the bare essentials.
   
   I've worked on several different teams developing software. There was very little in this book that came as a surprise. Every point seemed obvious, though in many cases, I was amazed by the wealth of research that Glass was able to cite to make his points. From the bankruptcy of hypesters to the importance of a work environment, Glass states the obvious with compelling and refreshing clarity.
   
   The "painful" part was realizing that at some point in my career, I've made almost every mistake he highlights.
   
   I found the tongue in cheek nature of the writing to be a bit much at times. That is my only complaint, and it's not so bad as to be unreadable.
   
   It probably won't make you a better programmer, but the knowledge in this book will provide magnificent insight into all the non-coding aspects of software development that we so often overlook. Human nature hasn't changed, and software will always be complex. The facts and fallacies he cites truly are fundamental, and will be with us forever.
   
   This book has given me a vocabulary with which to confront the absurd that we see every day in the world of software. Hopefully, I can now be a part of the solution rather than a part of the problem. Thank you, Dr. Glass!



4. This list of Facts and Fallacies usefully presents some of the more important and insightful learnings from decades of experience in Software Engineering.
   This book presents items in bite-size chunks of information that concisely detail the point being made in a non-technical manner that can be understood by upper management. Each Fact/Fallacy provides references to prior established works in anaylsing the effectiveness of Software Engineering.
   This is a great read.



5. As stated at the beginning of this book there are some controversial facts in there. But If you manage to put your personal bias aside you will find that it is quite useful in understanding what is going on around you and why some developers are like they are.
   
   In short this is a book which you can debate on your blog for ages or just enjoy reading.

5 comments about Micro-ISV: From Vision to Reality.

1. This excellent book deserves to become the definitive manual of the mechanics of software development for small (`micro') Independent Software Vendors. Not only for the in-depth content (some of which will quickly become obsolete given the speed of technical progress), but perhaps more importantly the description and outline of an approach to the business. Each of the seven chapters have right-now, to-the-point tips and tricks, along with the reasons for them, as well as an outstanding index and rich external references. This covers all the bases, and a few other things as well, and although well written by a seasoned and successful master, it has all the depth necessary to become a well-used reference manual. An excellent companion to this book is `The Business Of Software' by Eric Sink, from a broader perspective animated by anecdotes of his company's path to success.
   Eric Sink on the Business of Software (Expert's Voice)



2. Great book!
   
   As expected, it gives guidelines for becoming a Micro-ISV providing useful information in many topics: Product definition, cyber-infrastructure, market exposure, quality, support management, community relationships, law and payments.
   
   Provides a good number of interviews from diverse entrepeneurs, talking about their producs, business stories and advices for beginners.
   
   After reading it, i feel very motivated to follow the Micro-ISV road.



3. I only read half the book. Then why still rate it four stars?
   
   Having my own ISV for over six years now I have arrived at the point of having 10 people in my staff and having experienced most things any startup will bump upon. Sometimes that makes you think you've seen it all by now, but this is an illusion.
   
   No matter how many staff you have working for you, there will always be a Micro ISV within the company... you! Exept for any partners, no one will do your job of creating the company or product vision and has the same kind of commitment. Some would say that's sad to hear, but I think this is reality. You hire most people to complement you on your own skills, so most of the time don't expect the vision to come from them.
   
   Going through this book I sometimes skipped some of the pages. Some things I knew just to well to read about again, some applied on starting your own business and some parts applied to US / UK law only. Still, I managed to gain a lot of knowledge, ideas and feedback from this book.
   
   Thinking of starting your own ISV business? Then get this book first! Already a business owner with some experience under the belt? The pick your paragraphs and read what you have to. Great book, especially for ISV startups!



4. This book has a lot of good information on starting your own Micro-ISV. It does focus a lot on PC based software instead of Corporate Enterprise Software, but to be fair it's harder to build and sell Enterprise Level software with a few people.
   
   There are lots of good interviews with people that have succeeded in starting their own company and as expected it's not an easy route, but most seemed to be enjoying what they do.



5. Many "how-to" business books pretend they are going to show you how to take your business from nothing to hundreds of millions in sales overnight.
   
   "Micro-ISV" is refreshingly different.
   
   First, it is written specifically for those who want to bring personal computer software to the market through their own small, independent company. Second, it is about small companies. There is little here for the person who believes they are going to become a software billionaire. Rather, this is for the person with a good idea who wants to launch a software development and publishing enterprise that will remain small, except in the most exceptional circumstances.
   
   There are, in fact, thousands of small software publishers throughout the world who earn respectable incomes from their efforts. Some are truly small and the earnings of their publishing enterprise supplement the income from their day job. Others make quite significant sums from their products.
   
   Third, Bob Walsh does not peddle dreams or impossible schemes. He lays out a practical program for every step of creating your own "Micro-ISV" from having a vision, as he puts it, through developing and marketing your product. He even covers forms of business organization, which would be helpful for the complete neophyte.
   
   Walsh's orientation is toward Microsoft and the Universe it has created, which is about 90% of all the computers in the world. He offers a lot of extremely useful information about Microsoft and how even the smallest developer can benefit from their many support and assistance programs. Speaking from personal experience, Microsoft's support for developers is truly outstanding and Walsh presents the most detailed exposition of their developer support programs I've ever seen. (Note that some of Microsoft's programs have changed since "Micro-ISV" was published.)
   
   There are many sidebars featuring interviews with successful small developers or short case studies. Some of the interviews are fascinating such as those with David Allen, the author of "Getting Things Done", an approach to time management that has attracted an almost cult-like following (and that is a compliment) and Joel Spoelsky, founder of Fog Creek software, who is something of a legend in his own time.
   
   Overall, this is a remarkable how-to business book for anyone who believes they have an idea for a marketable software product.
   
   Jerry

2 comments about Microsoft Expression Web 2 On Demand.

1. I really like this book. I don't write reviews very often, but I was really impressed with this book. It is full color and very clearly written. I wish more technology books were this nice. It is asthetically enjoyable to work with.



2. I bought this book to try and get a handle on the new features in the product. I found some of the information to be inaccurate (not sure if it was based on a version prior to the version that Microsoft released or if the author was just careless) and some of the information that was included is confusing and hard to follow. I do like the quality of the graphics, but that hardly makes up for the other shortcomings.
   
   There are much better choices available. I also bought Jim Cheshire Using Expression Web 2 and I found it to be much better.
   
   One more thing. I'm not sure why the 5-star review that I see on this book appears here. It appears to be a review for the first Expression Web book from this author. It doesn't seem right for that to be used for this book. Strange.