5 comments about PHP 5 for Dummies.

1. Yes, the author reads the reviews here. That's me. The error in which a few quotes were replaced with underscores occurred during the publishing process, after I was finished with the book. I didn't know about the errors until I saw the earlier review here. However, there is no way to fix it. If the book is reprinted or a second edition is released, I can fix the errors, but not until then. I wish I could. I apologize to any who were confused by this problem.
   
   There are 8 quotes replaced with underscores on 4 lines in Chapter 3, 2 quotes replaced with underscores on 1 line in Chapter 4, and 20 quotes replaced with underscores on 8 lines in Chapter 5. I have a list of the errors and corrections on my web site at janet.valade.com/php5errors.html.



2. I only give this two stars because there are a few snippets of code that are worth absorbing. However this book has enough errors to make the subject matter confusing. I've used quite a few "Dummies" books as intros to a variety of subjects in my 20 years of programming. They have for the most part been quite helpful.
   
   I always expect some errors from books dealing with technical material, but the errors here are of a nature so as to cause confusion, especially to those new to PHP.
   
   My bottom line recommendation is not to use this book if you are new to programming or to PHP. You'll spend more time than warranted separating the wheat from the chaff. There are much better intros to be had. Try Sam's "PHP, MySQL and Apache" or Sitepoint's "Object Oriented PHP Solutions". Both are accurate, easy to understand, and have code samples that are easy to get to.



3. I have to repeat what others have said. This being a programming book, it is inexcusable to have _ when the programming language wants a "
   
   Terrible experience trying to learn a programming language when several symbols are just plain wrong in the text. What's the point? I'm paying money to waste my time figuring out typos in a programming language I do not know.
   
   So why did I give my money? Never again. The publisher should be recalling this book but they haven't done so.
   
   Other then this tremendously horrid mistake which is throughout the book there is some good information. There is also a lot of senseless rambling. The author goes on and on about PHP numerical functions. All she had to say was you can perform calculations and a few examples. Her rambling text is painfully dry. Maybe she should have spent more time proofreading rather then the obvious page filling.
   
   I'm angry that I had to translate code I'm trying to learn. Maybe the author and publisher should be paying me to teach them. Refund please.



4. I would've given this a 4. But, because of the amount of typos, give it a 3 instead. Good for beginners.
   
   Overall, very basic for beginners and explained in somewhat laymen term. Some may say that PHP is designed for non programmers, but for those who never used any programming languages before, trying to grasp the meaning of an array, multi dimensional array, different types of loops, functions, objects(their properties and methods), regular expression, blah blah blah, can be a brain twister still. However, if you have an editor/debugger (I use the Komodo IDE), it'll make learning MUCH easier. Don't let the brain twister part discourage you though, it's just a fact. But, once you start reading and writing codes, especially with the help of an editor/debugger, so that you can step in and watch line by line, to see what each line of statement and the variables are doing, things will fall into place. I used to program in VB, so I mainly read this book to learn the basics of how PHP syntax & structure work, the rest would be a lot easier(should've done this YEARS ago).
   
   An author should not be rating their own book a 5 star, especially with the amount of typos and definitely should not be justifying those typos. Before printing, those simple code snippets should've be tested, where they could have easily been caught and corrected.



5. This book is a very well prepared for its purpose and target readers... This is for the beginners and guides you through to intermadiete level in PHP. If you have some background in PHP, then I would suggest other works for intermediate and advanced coders.
   
   There are some printing errors that corrected by the author at her web site.. www.janet.valade.com/php5errors.html Please do not forget to go there to print the table out, so you can keep with the book.

4 comments about Data Structures and Abstractions with Java (2nd Edition) (GOAL Series).

1. Too complicated to use as a tutorial, and too simple to use as a reference. This book tries to be both and does a poor job of it. Buy this book if you absolutely have to (like I did, for a class at the U of MN); otherwise I'm sure there are other books out there that can do a better job.

   P.S. - I found at least one typo in chapter 1. Can you find it? :-)




2. We have been using this book at CSUCI as a textbook for a CS2 class with a heavy hands-on component. The book is very good in that role, and the lab manual - in spite of numerous errors in the first edition - is a very good companion.
   
   It is neither a tutorial nor a reference; it is a textbook for a university-level course. It teaches students how to embed numerous data structures and algorithms in Abstract Data Types (ADTs), how to use them from clients, and how to utilize the existing equivalents from the Java libraries (mainly Java Collection Framework).
   
   I highly recommend this book along with the lab manual to CS2 instructors.



3. This is one of the most useless Java books. I am a professor teaching JAVA in a state university. From my teaching experience and the feedbacks from students, I do not think this work is even worth reading. This book intends to introduce data structure through JAVA programming, but it does not achieve either goal. First, it is not a JAVA introductory book. If you are new to Java, the Just JAVA 2 (by van der Linden) is the best choice. If you want to know more about java, Core Java 2 is the good choice and can also be used as reference. If you want to learn data structure, there are many better books available on pure data structure or data structure with C++.
   
   This book is too expensive for students, and it does not deliver the content that is worth 1/10th of the book price. The only reason I use this for my class is that it is required by University and I cannot change that :(
   
   
   P.S. if you just want to learn more about Java, Think in JAVA is a great book and is free. The author (Bruce Eckel) did a great job in writing a great book and sharing it free on the internet [...].



4. Book was in new condition and shipped within a week. Would do business with again.

3 comments about MCSA/MCSE 70-270 Exam Prep 2: Windows XP Professional (Exam Prep 2).

1. Exam Prep 2: Windows XP Professional by the team of Melissa Craft and Don Poulton is the most comprehensive, accurate study guide for this popular MCSE exam. Updated with Service Pack 2 information, this in-depth approach to the exam objectives also explains the core concepts of the technology to help you pass the exam. Organized by exam objective, you will be able to quickly and easily assess your understanding of key exam topics. The real-world examples, extensive hands-on exercises and end-of-chapter exercises support exam objectives and reinforce learning.



2. The book was not bad, but I think it focused on a lot of material that was not on the test. I knew the material from the book's test and CD practice test, but it didn't help me when it wasn't on the actualy exam.



3. Over about 4 weeks I read this book and took the practice exam in the back. I also used the questions on the CD to drill. I did not read any other books. I passed the test with a 905. I will agree that this book covers more material than you need, but it goes quick and it is very informative.

5 comments about Java Management Extensions.

1. Java Management Extensions by Java expert J. Steven Perry is a superbly organized and written reference and instructional resource to managing Java applications with JMX. Individual chapters address standard, dynamic, model, and open MBeans, dynamic loading, the monitoring class and timer service, and much more. A practical study of JMX architecture as well as a thoroughly "user friendly" how-to guide for technical managers, Java Management Extensions is an exceptionally useful and straightforward manual.



2. This book covers the fundamentals of JMX but where I was disappointed was that it uses a pretty basic queue example and doesn't really get into J2EE applications and praticle uses. I was left wondering when to use it. If I had it to do over I'd choose another book with more praticle applications for JMX.



3. JMX is a Java framework for managing enterprise applications in a distributed environment. The book Java Management Extensions takes the reader from a high-level mountaintop description of what JMX is in the first chapter, aimed at architects and management, who might be investigating the new technology, to a trench-digging description of how to expose a class for management through instrumenting an MBean.

   Perry's initial description of the JMX architecture in the first chapter does a good job describing the parts of the JMX and how they interoperate. It is a very high-level view of JMX and many abstract ideas are presented. On a personal level, my experience with the JBoss application server gave me a concrete example to refer to during this JMX introduction, which helped. Here, the reader is presented with many UML diagrams to illustrate the architecture.

   The next four chapters cover the nuts and bolts of how to construct JMX services. To use the JMX framework, a developer must become familiar with an object called an MBean. In a nutshell, MBeans are Java classes that implement an MBean interface (A process known as instrumenting), allowing the MBeans to be loaded into an MBean server and managed. In these chapters, Perry talks about four types of Mbeans, Standard, Dynamic, Model, and Open MBeans. After introducing each type of MBean, Perry gives simple code examples of how to build each type of MBean.
   
   Chapter 6 deals primarily with introducing the reader to the MBean server. Perry uses the reference implementation from Sun for the examples in his book. Real world MBean servers include names such as JBoss and WebLogic. The most exciting part of the book, I felt were chapters 7 and 9, where Perry talks about the JMX notification model and Monitoring classes. Firing events, filtering notifications, and creating monitors appear to be the real advantages to the JMX framework and are covered thoroughly in these chapters.

   Perry's no-nonsense writing style provides a succinct description of the architecture. At 312 pages, the book is the thinnest technical book on my bookshelf, making the read easier to manage.

   In summary, Java Management Extensions is a good book for developers who want to gain an understanding of what JMX is. Programmers new to JMX will probably find the first part of the book a good introduction to JMX and its architecture, while the last chapters focus more on how to put the framework to good use. Although Perry does not have a style of writing that entertained me, it was clear and to the point. He does cover his information thoroughly and appears to know the content well. JMX is a technology that I feel will be used heavily in the future, and for anyone who is intending to write a J2EE application that needs management or monitoring, JMX appears to be the answer.




4. It has been 4 years since this book came out. Despite the many high hopes in the computer industry in 2002, JMX has run out of conceptual steam. You can't tell that from the text. But since then, Service Oriented Architecture and Web Services have garnered far more mindshare.
   
   The text also does not indicate that JMX simply proved too hard in practice, as a useful management tool or console. If you read the book and try its recommendations, you are walking into a dead end. There will be very little interest by others in what you program.



5. If you're looking for an introduction to JMX, this book gives good coverage of the concepts and techniques behind instrumenting your applications. However, if you're looking for information on the latest and greatest in JMX, especially anything related to JMX remoting, then you should look somewhere else. This book was written in 2002, before J2SE 5.0, and a lot has happened to JMX since then. Starting with J2SE 5.0, JMX is a core part of the Java standard library and the JDK ships with a highly usable remote management application called jconsole.

5 comments about A Programmer's Introduction to C# 2.0, Third Edition (Expert's Voice).

1. A print copy of this book is probably a bad idea, since its main value is its capability of describing differences between C# 1.x and 2.0. Not written to groove anyone into using C#; targeted more at people who know 1.x intimately or those coming from a java or c++ background, wanting to know about generics and other "new" features. It would sure be nice to have the pdf freebie that comes with a lot of apress books, but no -- it costs another $30. If you really want to know about C# from the ground up, this book can only be ancillary to something like Liberty's book or Troelsen's Professional C# and the .Net Platform. Hence the fact that you can buy it used for $10 or less.



2. I expected this book to just cover the enhanced 2.0 features. That's not the point at all. This is an all you can eat C# introduction book that goes really, really fast. Read in the title that this is for 'programmers'. That means that the author expects you to understand how to program an object oriented language. If you know that already then this book will get you into C# 2.0 quickly and easily. If you don't know how to program, then this book is not for you.



3. If you have not been programming for years or have a degree in Computer Science don't buy this book! However if you are a "real" programmer and want to learn the C# fast, it is a very easy to read, quick and pleasant why to get up to speed.
   
   Once you have learned C#, you will need to read some books that cover what ever part(s) of the .NET framework you wish to use. However knowing C# before you try to learn the .NET framework will give you an advantage.



4. Easy to read and understand.
   If you are new to C# look elsewhere (Troelsen, Liberty).



5. When I started at my current job, I was asked to program in C#, even though I had originally been hired as a Java programmer. Faced with this task I went to the bookstore and bought a book. The title of this one won me over, since I didn't want a book that explained object oriented programming from scratch - I had experience with Java and C++ already - I just wanted something that walked through the various features of C# at a fast pace.
   "A programmer's introduction to C# 2.0" does an excellent job at being such a book. The authors rapidly go through the various aspects of the C# language and the .net platform, introducing some peripheral topics, such as Windows Forms, on the way (just one chapter though, so don't buy the bok for this). Generally more attention is given to topics where C# differs, subtly or substantially, from similar languages like Java, and less attention is given to the basics that most C family languages have in common.
   As such I've found that the format of this book enabled me to learn C# very rapidly based on what I already knew about other languages. I would strongly recommend it to programmers in a similar situation. My only gripe right now is that the book would ideally be updated for C# 3.5, but this doesn't seem to have happened yet - however C# 3.5 programmers can read this book and get the additional topics from other sources.

3 comments about Constructing Usable Shopping Carts.

1. Once again glasshaus delivered a practical oriented and well-focused book. The authors don't waste time, straight to the meat; the book is actually full of well-explained code listings. The sample applications use ASP/SQL server and PHP/MySQL, but a lot of material is still relevant for other technologies, especially the coverage of database design, but also usability, interfaces and workflow
   BTW The book is actually 300+ pages long



2. The authors set forth an ambitious goal. In one book, they try to show you how to design and code a full e-commerce application. From laying out the user interface and connecting its interactions with a server running a relational database. For the latter, they spend some time with an extended example that involves constructing a set of interrelated tables, with primary and foreign keys. Those of you already familiar with RDB and the various normal forms will be very comfortable here.

   For the actual database, they illustrate with Microsoft SQL and the free MySQL. The code to connect is given in fair detail. Quite aside from anything else, the differences and similarities between these databases can be very useful. You can see the pros and cons of going with either. Heck, if you are searching for a book that compares these 2 common and important databases, this book is a good choice.

   The book is a little curious in one way. The authors are clearly skilled, but they don't seem to use the formal Model-View-Controller (MVC) approach. Though you might see that the various pieces and interconnections they give can amount to this. Nor do they explicitly use the idea of an n-tier architecture. Perhaps they chose to omit these ideas to simplify the narrative. Since if you successfully use their ideas to build your application, the MVC and n-tier ideas can then have far more substance to you, when you later encounter them.




3. The authors set forth an ambitious goal. In one book, they try to show you how to design and code a full e-commerce application. From laying out the user interface and connecting its interactions with a server running a relational database. For the latter, they spend some time with an extended example that involves constructing a set of interrelated tables, with primary and foreign keys.
   
   Those of you already familiar with RDB and the various normal forms will be very comfortable here. For the actual database, they illustrate with Microsoft SQL and the free MySQL. The code to connect is given in fair detail. Quite aside from anything else, the differences and similarities between these databases can be very useful. You can see the pros and cons of going with either. Heck, if you are searching for a book that compares these 2 common and important databases, this book is a good choice.
   
   The book is a little curious in one way. The authors are clearly skilled, but they don't seem to use the formal Model-View-Controller (MVC) approach. Though you might see that the various pieces and interconnections they give can amount to this. Nor do they explicitly use the idea of an n-tier architecture. Perhaps they chose to omit these ideas to simplify the narrative. Since if you successfully use their ideas to build your application, the MVC and n-tier ideas can then have far more substance to you, when you later encounter them.

5 comments about Fuzzy Logic for Beginners.

1. I found this text to be a satisfactory introduction to the principles of Fuzzy Logic. I don't think that the book presents the relevant information to developing a fuzzy system, but rather tries to excite the viewer with useless examples of fuzzy systems.

   It did answer and explain in detail fuzzy logic and the history behind the controversial mathematical concept. To predict the characteristic of something based on a table of measured values is something whose problem lies in the implementation of such a process. It would take a good amount of testing to find how much torque is needed to counteract the steering in commuter trains. The previous sentence was one of the examples used in the text.




2. I had hoped to get a concise introduction to fuzzy logic from this book. But the author only discusses fuzzy logic at the highest level, not much more deeply than most newspaper and magazine articles. The original text was clearly written in Japanese, and the translation is among the worst I've dealt with in the science and mathematical subjects.
   
   In short, apply the money you would spend for this book to one that is more expensive but actually useful. Just accept that getting to know fuzzy will not be cheap!



3. While I would agree that the text of the book is a poor translation from the original Japanese (my guess is they waved it in the general direction of an editor while he was distracted) and there is not much in the way of technical depth to the book, it seems to me to very nicely and concisely capture the spirit of the "Fuzzy" movement.
   
   All in all I think its a great introduction if you are wondering what all this fuzzy nonsense is about anyway, but don't plan on reading it twice.



4. I agree with Mr. Lentini. If you want to learn something about fuzzy logic - look for some other book. This is actually a booklet that only characterizes Fuzzy Logic in a very childish manner. The translator is an utter ignorant: Leibnitz is called "Ripunitz" and Aristole is "Alistoter" or something like that (probably following the Japanese transcription...). Even 1 cent is a waste for it.



5. I am an engineer and have read a lot of books on science, math and
   of course engineering. But I have never read a book this bad in
   English. Apparently, translator's mother tongue is not English.
   I am inclined to blame the publisher who publishes a book without
   checking the credential of the translator. My recommendation is:
   do not waist your money on this book.

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.

5 comments about Introducing Microsoft® LINQ.

1. I learned a few things from the book, but overall it left me wanting more. The price matches a much bigger book, so I would've expected it to be full of good stuff, but in fact it was almost cursory on most topics. I realize it's an "Introducing" book, but for the price I would've wanted a somewhat deeper introduction.



2. Considering that this book is based on a beta product, I was expecting it to have a section on installing LINQ. Sure I can go to the LINQ's website and find out but the author should have added that section and discuss the tricks, tips, caveats and particularly his experiences when he installed the beta version of LINQ. Without the LINQ installed in my machine, I was not able to try the code examples in the book.
   
   There is a relatively long section about C# 2.0 features. That is a nice-to-have section but that is the one he should have omitted.
   
   For a 240-page paper bound book, this is a bit pricey.
   
   I returned the book and promised myself to wait for the final release of LINQ before I buy any book about it.



3. this is a great into - not something you are going to start using right away, but good to keep in mind for up and coming projects. If you are using VS2005 you can start playing with this - its not a VISTA only tool.



4. I feel a little bad rating this a 4 since it's a Beta book. It's really hard writing on betas b/c material changes so frequently.
   
   I liked the book a lot and thought it covered the topics of LINQ and EF pretty well. I think though, it was a bit too heavy into language features of C# 3.0 and VB 9.0. Yes, it's necessary to cover many of these in the context of LINQ but I think proportion wise, it was a bit too much there and a little light in other areas (for instance, unless I totally missed it, i didn't see anything about parallell LINQ). The coverage of EF was good, but I would love to have seen about 50 more pages.
   
   Although it's small the content is right to the point however. They do a good job of discussing LINQ and EF and even showing some more advanced areas and I will say that if you read this book and understand it, you can get just about anywhere you want to be with LINQ. You can read it quickly and be up and running very quickly and that's the strength.
   
   In all honesty, I should probably have given it a 5. My personal opinion is that it's not quite a 5 but definitely higher than a 4. If it were 10.00 cheaper, I probably would have went for the 5 - but it's not a cheap book for the size of it.
   
   The authors did a great job in many areas and considering it's a beta release, they did a superb job.



5. I give this book two stars because it is not what I (a beginner) wanted to use. I cannot say how good a book it is for the audience it is written for.
   This book is designed for experienced programmers who know C# code. It surveys the use of advanced programming techniques using LINQ.
   The authors explain on page 51 "the ability to read C# code is also important for reading the rest of this book (because LINQ examples are written in C#) and for understanding differences between C# 3.0 and Visual Basic 9.0.
   This is not a how to book with introductory examples. It is not for beginners.

5 comments about Analog Circuit Design: Art, Science and Personalities (EDN Series for Design Engineers).

1. There is a lot of good information contained within this book from the many contributing authors. You can learn a lot of little "tricks" to help you in circuit design. However, many of the contributors get a little carried away with their own personal histories and design biases. I would like to have seen a few more of the design methods and ideas, that the authors have learned over the years, included in the book. Most of the authors are straigth forward in their design philosophies and explanations. However, some of the authors spend pages talking about how, "...they don't even own a computer, much less use it for design...," type of philosophies. This is just plain arrogance on the part of the author and does not help the reader. If the author had used the same page to talk more about how he optimizes a circuit's design, the book would have received a much higher mark from me. Overall, it's not a bad book despite these small shortcomings.



2. This is a great book to help you understand Analog engineers - I recruit them for an IC design company and am impressed how smart they are - this book gives you an idea of their depth...



3. Analysis is a science: there's a right answer out there, and we can all agree when it's found. Troubleshooting is the same way: when the broken bit is found and fixed, the circuit starts working properly.

   Design, on the other hand, is an art; there's always more than one way to do it, and the individuality of the designer has a strong influence on the way the design turns out: hence "Art, Science, and Personalities".

   This isn't to say that a good designer does unusual things without a good reason, or adds expensive bells and whistles because he happens to like them. What it means is that for designs that are not routine, the designer's personality has a lot to do with how it comes out.

   To become an expert designer, you need a well-developed technical taste. Once you have a design that works at some level, it's that sour feeling in the back of your mouth that will tell you that it isn't right yet, that it can be simpler, cheaper, or more reliable. There aren't a lot of other sources of that information.

   Arts are taught by apprenticeship. But where are you going to go to get taught this stuff nowadays? EE departments are going more and more to software, as shown by the vast number of graduate EEs who don't know which end of a soldering iron to hold. Jim Williams can't be everybody's mentor, but in this informal (and sometimes whimsical) book, he and his friends show us how the best analogue designers in the business go about things. You know what? One of the most important elements in the art of design is *play*.

   Maybe listening in on these guys playing at being analogue designers isn't quite the same as sitting elbow-to-elbow with them, but it's as close as most of us are going to get, and it's terrifically valuable. I recommend this book to anyone who wants to become a better analogue designer, and who is not easily put off by whimsy in technical writing. (I find it refreshing and fun, myself.) I've owned this book for 6 or 7 years, and it's about ready to fall apart from rereading.




4. I agree completely with the reviewer from SLC: there are some interesting insights, but too much ego invested in personal memoirs and irrelevant anecdotes of personal history.



5. you into Analog ? You got to have this book. Its a tribute to the LEGENDS. Legends that ever were, that ever will be. My boyhood favourite of almost 10 years. Dont miss it on the analog shelf. I would deem it blasphemy.