5 comments about Pro InfoPath 2007 (Expert's Voice).

1. This book is just great. Good coverage in around 300 pages. I totally dislike huge development books that just harp around. This book covers all the necessary topics with examples... A++++++++++++++++ for Philo Janus



2. This tiny book, in comparison with other technical manuals, is a fantastic way to get up to speed with InfoPath in a very short time. I'd never had the opportunity to work with InfoPath before, until my company decided to implement MOSS 2007 with InfoPath Forms services. I bought this book and in a few short days we were churning out InfoPath business solutions.
   This book is an easy weekend read and then you are ready to go!



3. Microsoft writes a lot of sales hype about how terrific a product is but rarely explains what a product can and cant do. After days of asking I have yet to find out what Infopath exactly does and what it is capable of. We have documents in our office. It would be a blessing if people could go to our website fill out a form and then email the data to us so that we could then merge that data into a word document. Simply recieve an email in outlook after a client has input data on our website and then merge the data into word.
   
   It looks as if Infopath might do that function but most people have never even heard of the product although it has existed since 2003.
   
   After days on the internet I have yet to discover if this product can do that or exactly what product could do that. Infopath is not a popular product because of just that reason it is a mystery full of mis-information. Why is it we have to buy a book or buy a product to determine whether or not we need it??? I wish that the author (and Micro soft) would explain exactly what Infopath does and what we would be taught. I wont buy the product or read the book if you cant determine what I am about to learn, what it offers or why I need it.



4. There are all too many technical books that are heavy on theory and light on "how to", or start out in an introductory fashion and then suddenly venture into highly technical territory without including the necessary background information needed to understand the content.
   
   In "Pro InfoPath 2007", Philo Janus neatly avoids these pitfalls. Since he's writing about a product with whom most readers may not be familiar, he first answers the vital question, "What IS InfoPath?" with a comprehensive introduction to the product. Then Janus carefully outlines the capabilities of InfoPath and walks the reader through the steps necessary to create InfoPath forms in all kinds of environments; how to meet business needs in a myriad of situations; and most importantly, includes possible issues and limitations that one might encounter when using InfoPath and provides the necessary workarounds.
   
   My own company has InfoPath installed but despite an enterprise-wide need for exactly what InfoPath does, is resistant to its use because of a fundamental lack of understanding of the software and how to best deploy it. A read of this book would convince them that they have a good product sitting on the shelf that would meet their needs and interface neatly with Sharepoint and other applications already in use.
   
   Thumbs up to Philo Janus for a job well done.



5. I wanted to learn InfoPath, I am having to learn alot about computer languages and formats. I thought this would help, yeah, no so much.

5 comments about Pro JavaScript Techniques (Pro).

1. Book has lots of examples. Many involve using libraries such as Prototype and JQuery. But, if you are not already familiar with using those libraries, the examples will not make much sense. And considering the typos in the straight JavaScript examples, it left me wondering about the validity of the library demos. Written in the style of a blogger where the author expects you to follow a link to a library's web page and then come back before you can understand the example. If I'm paying for a book to cuddle up with to read on a winter's night, I want it to be self contained - and not expect me to reach for the laptop to read up on the syntax of another library. It also didn't even touch upon one of the more difficult to grasp "Pro" techniques - scoping of "this" when using object methods during AJAX callbacks in the author's own code examples or the various libraries he touts.



2. This was an excellent book two years ago, (and still is), but it's now outdated. I bought it based on its nearly five-star rating; I wish I'd done my homework, since I immediately needed to buy other books to supplement this one.



3. Pro JavaScript Techniques by John Resig is probably the best resource on the language I've encountered to date. I'm one of those web developers who has had something of a mental block when it comes to JavaScript. Despite its ubiquity, it always seemed like a toy language to me. It didn't help that JavaScript's syntax plays a bit fast and loose to my tastes, and that virtually all of the other resources on the language I've encountered barely scratched the surface on what the language can actually do. If you're like me - familiar with the basics, but knowing that you're not proficient enough to use it in a professional setting - then this book is for you.
   
   First, the bad news. Like all aPress books I've encountered, this one suffers from a few small, but glaring, editing errors. Small things - variable names that change between examples for no good reason, in-text refrences to things the author didn't mention (no doubt something missed between drafts), that sort of thing - crop up. It's not enough to break the book, but it is annoying.
   
   Also, the first section of the book moves at break-neck speed. While some of it is review, for those of us who have been toiling in web tutorials and older books, a few re-reads are necessary to truly understand what's going on. Thankfully, Resig addresses things in a logical manner, so each topic flows nicely into the next, making returning to those parts as painless as possible.
   
   Finally, in the chapter where he discusses public, private, and privledged object properties and methods, he completely glosses over how private properties and methods function. Instead, he merely tells the user to visit Douglas Crockford's site on the matter. It's a bit of a cop-out, and I figure that since I'm spending ~$30 on the book, the least he can do is briefly condence Crockford's ideas.
   
   All that said, though, the positives outweigh the negatives by far.
   
   Despite the quick pacing of the book, the information (ignoring editing inconsistencies) is delivered in a straightforward manner. Resig addresses most, if not all, of those little things which are important in the real world (testing/debugging, how to work with libraries, how to ensure your code doesn't interfere with someone else's code, etc), but are often ignored in other resources.
   
   In particular, the early chapters (chapters 2 and 3) on dealing with JavaScript objects are well done. While Resig doesn't go into all of the details (most notably with the link to Crockford's site I mentioned earlier), these chapters form the foundation of just about everything you'd want to do with the language. Indeed, these chapters address most of the pitfalls that create those pesky JavaScript errors we've all dealt with before: scope, closures, and context. Understanding how those three concepts work in unison is fundamental towards understanding modern, professional JavaScript as a whole.
   
   Being a JavaScript book, this particular volume visits topics we're most likely all familiar with: DOM scripting, event handling, and even a bit of AJAX. Thanfully, Resig stays true to his mission of creating inobtrusive JavaScript, and keeps his HTML separated from the scripting code. This is a far cry from other self-proclaimed professional tomes that embed their JavaScript function calls within their HTML tags.
   
   To conclude (and reiterate), Pro JavaScript Techniques is the perfect book for those developers caught in the middle. It's a resource aimed at those of us who have had experience with the language, but have never been pointed in the right direction to use it in a professional manner. Despite its annoying flaws, this book fills the rather large gap between beginner's JavaScripting and creating robust AJAX applications. It's worth owning if you ever want to do serious work with the language.



4. John Resig never fails to amaze and his latest book is no exception. I highly recommend it to everyone interested in javascript; it is a must have.



5. I agree with only one other reviewer who commented on the typos, etc. The demo code does not work until you debug it. The first couple of chapters on Javascript code are very good. The chapters on Forms (8) and Lightbox(9) are so poor I stopped reading. I am a jQuery user and admire Resig's contribution, but this book should be skipped.

5 comments about The Art of Agile Development.

1. After reaching 100 pages I felt really disappointed. I was looking something more similar to "Beautiful code" but about management. I have found a book without facts and measures but "tips". I think that we [developers, project managers and other animals] should try to move our profession towards a scientific discipline (i.e. hypothesis-measure pairs).
   
   I was looking for something either like "Mythical man-month"/"Peopleware" or the IEEE articles "voice of evidence". I didn't found any of those.
   
   I do not need any tips but real evidence about what development strategies are good/bad and in which conditions. Real data please.



2. This book is very well written and gives a great description of many different types of Agile practices. Although the book centers around XP, I think many of the techniques and practices could be brought over to any of the different Agile disciplines. The book also goes into the all important steps of selling agile practices to those with the money: managers, directors, stake holders, and the customers. This is a very important step! The book is also nice in that it doesn't necessarily have to be read in chapter order. If you need some help on something, it's easy to pick up the details by just going straight to that section - no need to read everything before it to get caught up. All the information in the book can be applied directly. Many of the concerns related to starting up Agile development in a shop are covered very well.



3. In my opinion, this is the best book for someone starting to implement XP. Before this book, other two books on XP practice were "XP applied" and "XP installed".
   Book by James Shore and Shane Warden provides more broad coverage, then previous books, and contains a lot of good advice, what to do, what not do, and how to do what should be done, while going to the path of Agility.
   
   Presentation is based on the XP, but book also shows a more wide perspective, and contains comparison with SCRUM
   
   What I really like in the book
   - Pragmatic approach to XP - In this book, you will not see approach XP as a holy grail - do it either this way, or you are wrong. Instead, authors expand the original definition of the XP from XP Explained by the practices, which they found to work well in real world
   - Its practical focus - It contains a lot of the practical tips (for example, how to implement continuous integration successfully, how to do test-driven development, what is the real meaning of the user stories etc..)
   - Balanced presentation - for each practice there is Q&A section, contraindications and alternative practices.
   - Live style - book is written in clear and engaging language
   
   Quality of book is very high, and I would recommend it to my friends as a best book to read on working in agile/XP style



4. I have about a dozen books on Agile and Lean development and this rapidly became my favorite.
   
   Why: It's advice at the level I can use. Clear solid explanation and methods to understand what to do, what not to do, and most important, why.
   
   It's just incredibly easy to read and use.
   
   I've already bought 2 more copies to share with friends!



5. This book has three parts in it - introduction to agility, guide to extreme programming and afterthoughts. You may want to read this book if you want to set up XP in your team or participate in it. It is mostly beneficial for the developers or project managers to read it.
   
   The first part (Getting Started) is about 40 pages long and just puts you on the right track by discussing what agility means and introducing you to extreme programming. Here is where the authors explain how to determine whether XP is right in your case, what prerequisites are needed and what steps need to be taken to start.
   
   The second part (Practicing XP) takes most of the book, some 300 pages and contains detailed guide to extreme programming. This is where all the XP practices are explained one by one. Each is given a big chapter - Thinking, Collaborating, Releasing, Planning and Developing. Inside each chapter, there is a detailed explanation of the relevant practices.
   
   The last part (Mastering Agility) is again on the smaller side, it takes 40 pages and contains assorted advices along the "rules are there to be broken" lines. Afterthoughts to help you improve XP once you think you have mastered it.
   
   It is therefore safe to say that the book is essentially a guide to XP, and a good one too. The writing style is excellent - information is organized in half a page long self-contained chunks, each chunk covers some concept or answers some question. Because of this, it is really easy to follow the material.
   
   Even better, each chapter is closed with mandatory sections Questions, Results, Contraindications, Alternatives. Questions are indeed short Q&A and the questions were real-life, more often than not I have found mine answered. Results explain what exactly comes out of the discussed practice. Contraindications explain what obstacles there could appear. Alternatives explain what to do whenever you cannot use the discussed practice. Very realistic and informative.
   
   There were a few imaginary tales from the field. You know, the ones that go like
   - "We use XP here", said Alice.
   - "Wow !", said Bob.
   I don't generally like such stories, they make me feel stupid and therefore in my opinion the book (just like any other) could have got without them better. But this is just me.
   
   An extremely practical guide to extreme programming.

5 comments about FileMaker Pro 9: The Missing Manual.

1. Pros:
   
   - The writing style is accessible and easy to understand
   - You can download the database examples used in the book.
   - It's the best FileMaker Pro 9 book I've seen.
   
   Cons:
   
   - Like a lot of computer books out there, this one is unnecessarily wordy. The publisher said, "I need a 750-page book," and the author complied.
   
   -And you gotta read ALL of it (especially beginners), because important information is distributed like buried treasure.
   
   - The wordiness and lack of consistent structure makes it easy to get lost. Let me give you an example:
   
   This is my first stab at FileMaker Pro. The first chapter shows you how to find records. It starts out nicely with bolded text showing the steps to perform a find. Then it gets wordy. And then it shows a few figures of what you will see. Huge paragraphs of smaller, italicized text accompany the figures.
   
   I skipped the figures and went on. Suddenly, I couldn't access most of my database entries. I went back to Browse mode, like the book told me to do, and still couldn't see them.
   
   Finally, after much digging, I found the crucial step I had missed, buried in the smaller, italicized text of the gargantuan paragraph accompanying Figure 1-17. Inconsistencies like this make the book a tough slog.
   
   I just brushed up on my Access 2003 (I haven't used it in 7 years) with one of those procedure-based illustrated books. It took me 3 hours to get through the 250-page book. It took me about an hour to get through chapter 1 (27 pages) of this book.
   
   
   I recommend downloading the examples from their website (I doubt you got a CD-ROM with your book). See the Missing CD-ROM link on this book's web page.



2. This is a thorough review of how to set up various database features of the Filemaker system. Like many such manuals I have had in the past, I found myself reading and re-reading instructions feeling there must be clearer, better ways to instruct someone on the various procedures of this fine database software. Nevertheless this reader got over some difficult spots in setting up his database and gives the book a positive review...



3. FileMaker Pro 9 is one of the most intuitive and user-friendly database programs available. But, as with all database programs, it is capable of so much that it is practically impossible for the typical user to deduce all of its functionality simply by searching the program's multiple menus.
   
   Enter FileMaker Pro 9: The Missing Manual - another edition of the Missing Manual series designed to enlighten non-technical persons on highly technical subjects.
   
   The main selling point of the series is that it is very simple to read. O'Reilly's writers are also extremely knowledgeable in the subject area. Geoff Coffey, has been a FileMaker Pro trainer and consultant for over 10 years. Susan Prosser is also a FileMaker consultant, as well as a database program creator. Along with the Missing Manual creative team, these authors impart their wealth of knowledge in a way that anyone could understand. And since they aren't part of FileMaker, Inc., they aren't afraid to point out any of the software's problems.
   
   When comparing FileMaker Pro 9: The Missing Manual to the user's guide supplied in the software's box, several differences are notable. The biggest is size: the Missing Manual is wider, taller, and much thicker. So if you just need a quick introduction to the program, this book might not be what you need. Learning a program as extensive as FileMaker Pro takes time, and delving through the Missing Manual is going to take a lot of it. But if you want to get the most out of FileMaker Pro, then the user's guide just isn't enough. The Missing Manual also notably uses less complicated language, has more example images, and presents a intuitive flow of information than the user's guide.
   
   One of the biggest benefits of FileMaker Pro 9: The Missing Manual is the online support. Armed with just the software and user's guide, you have to learn from scratch. The Missing Manual, on the other hand, offers several pre-built databases that it guides you through. This not only gives you an example to work with while learning, but also shows you various ways that your final databases could be built and organized.
   
   The indexing is also much more detailed in the Missing Manual. So if you ever forget how to work a specific function of the program, the answer is a quick look-up away, though there are several instances in which the index reference the wrong section of the book (but the right page number). This is probably due to a late chapter reorganization before publishing.
   
   While the current Missing Manual is well supported with examples, it does not, as yet, support any new software updates being offered by FileMaker, Inc.. In other words, the book is written for the FileMaker Pro 9 program right out of the box. If the company puts out any updates that alter the software, then you need to do your own research to figure out the changes. Also, when FileMaker Pro 10 becomes available, there is no smaller Missing Manual explaining just those changes - you'll need to pick up a new edition. So if you're not new to the FileMaker Pro software, these manuals might be more than you need.
   
   I found FileMaker Pro 9: The Missing Manual to be perfect for someone just starting to work with database programs. It's step-by-step process will have you building your first personal or professional database in no time!



4. This book does a good job of explaining the features of the product. It's clear and easy to use. Well recommended.



5. On my journey to create a relational database I realized the need for a teacher, a resource, and some inspiration. This book is awesome and provided all I needed. My Filemaker knowledge is growing every hour as a result of this book. In addition, my database is becoming more user-friendly, secure, and downright logical.
   
   Thank you, Filemaker Pro 9 Missing Manual, for being there for me in the summer of 2008.

5 comments about Microsoft® Office SharePoint® Server 2007 Administrator's Companion.

1. If this companion where a living entity, I would kick it off my team.
   
   Having an O'Reilly safari account I read through it and was very disappointed in that it doesn't cover some of the basic functionality that might be expected from a companion.
   
   As for the hype, don't buy it to it!



2. The sheer amount of information presented in this volume is impressive in and of itself. The depth and quality of coverage into the many topics varies, and there's no one topic covered in totality, but this is the "one" book. English et al. nailed coverage across topics i.e. in scope and breadth. This is certainly not the book for beginners; there is a degree of basic SharePoint knowledge assumed, and you'll need to go elsewhere for deeper developer discussion (e.g. Pattison and Larson) or specifics on administration (various blogs). But if you're to make a career out of SharePoint 2007, you'll need most if not all of the information that's contained in this book. It's nice to have it in one reference.



3. This book is geared toward readers such as Web Developers, Information Management / Compliance Specialist, Administrators to name but a few. If you are a beginner to Sharepoint Server 2007, this book will be a most difficult read. The concepts and topics that are presented will have to be re-enforced with online research or the purchase of another book.
   
   To give an example.
   The book is composed of six sections, with the first three ( 663 pages in length ) being targeted towards administration and configuration. However, within this mix we have presentations on performance monitoring and MOM 2005, high level discussions on information security policies such as password and storage policies, data classification. We are introduced to advanced Enterprise topics such as the Business Data Catalogue and records compliance ( that is the Sarbanes Oxley Act etc. ). These discussions all assume prior expertise and should you be new to Sharepoint Server 2007 this will no doubt frustrate you. The Authors, in their quest to appeal to a wide variety of readers, cannot delve into the in-depth explanations, followed up by well worked out examples that a beginner to Sharepoint Server 2007 would require.
   
   Web Developers will tend to focus on Sections 5 and 6. While these sections do introduce Workflow Services, Webparts and products like Sharepoint Designer I found the overriding theme is again one of high level discussion and overviews. Expertise is assumed.
   
   Overall I would say that if you are coming from a background with some expertise in Sharepoint Server 2003 or you require a high level picture of the abundance of features that Sharepoint 2007 can bring to your organisation in addition to how it integrates with other server platforms, such as ISA 2006 for example, you will enjoy this book and the nuggets of useful information it provides. The writing style is not engaging; this book is not a joy to read but it will tell you what can be done with Sharepoint Server 2007, outline best practices and point you in the correct direction. The how-to part is very much left to yourself.
   
   If however, your goal in purchasing this book is an in-depth knowledge of the installation, administration and configuration of Sharepoint 2007 and you have no prior expertise with Sharepoint Server 2003 or indeed 2001, then you will gain little benefit from this book. You will find it difficult to read, difficult to digest and your understanding of Sharepoint 2007 will not improve. If anything, you may be discouraged from using Sharepoint Server 2007 which would be a shame as the product is in my opinion really good. Regards.



4. This book covers most of what an administrator needs to know, very acurate information. I use this book all the time for reference because you can't retain everything that's in this book, it's a great tool for studying for MS Exams.



5. Useful reference and the eBook (pdf) has been invaluable. Unfortunately, the pdf is locked which restricts copy/paste (which would be great for documentation). This booke is not a sit down and read from cover to cover, but a go to book for research/reference.

5 comments about Managing Humans: Biting and Humorous Tales of a Software Engineering Manager.

1. This book was recommend to me by an engineer I trust. The idea was "read this, because this is what a software/systems engineer thinks managers should be more like".
   
   I found the book witty, intelligent and an easy read.
   
   Also, through most of the chapters I took some great notes and "gotcha's" about management and have been applying them as much as I can.
   
   Recommended reading for any manager who has a group of "individuals" and rock stars working for them in a fast-paced software environment -- OR -- for anyone who likes funny, management self-help books.



2. This book is supposed to be for aspiring managers, managers, and anyone who wants to know what a manager is. While it is definitely for the latter, it's not a book for managers or even aspiring managers. What I dislike most about the book is the self-important tone the author has. A lot of the content degrades in usefulness because the author assumes (or wants to believe) that the reader is really interested in him, not the lessons learned from his experiences. This is especially evident the third part, "Versions of You", where the author writes as if the reader will be impressed by the author's self-description (though this is thinly veiled by his constant reference to himself in the third-person, using his pseudonym "Rands").
   
   The use of this pseudonym, "Rands" was puzzling by itself until I learned about how he started writing about his work experiences by blogging. In this light, things make a little more sense, as I could see how the book is just a collection of blog posts pulled together. The execution leaves a lot to be desired however, as the content jumps a lot, and successive chapters have little relation to each other. I can understand why one would want to use a pseudonym while blogging about work life, but using a pseudonym in a book when your real name is on the cover is silly.
   
   Regardless, much of the book is written for people who want to understand software managers, which is much different than people who know anything about software or management, and want to hone their craft. There are a few interesting tidbits throughout the book, but they're scattered in between material I felt was irrelevant, or which I could barely continue reading because my eyes were rolling so much.



3. 
   While I learned a great deal from this book, as importantly, I enjoyed the read immensely. Michael knows very well that people learn through stories. This book is a collection of stories with analysis interspersed. I highly recommend this book for IT Managers looking to improve their leadership skills or IT engineers trying to figure out what makes their manager tick.



4. this is the first review i write, and yes it is because i was really upset at myself for getting this book. it is a random collection of paragraph. no "biting tale", no insight, only a failed attempt to "wow" people with boring stories. nothing to be learned, except that without ideas or writing skills one can still make money out of a book



5. While this book has some very good insights about management that are right on, the relentless use of angry and derogatory terms to describe everyone from managers to subordinates leaves me exasperated and cold. While humans, or should I say people, have their issues, I prefer to see the inherent value, humor, fun and value that each person has. These good qualities that human beings have are what make management an interesting and enjoyable job.
   
   I've yet to find a management book this is not either boring or whining. This book gave me hope when I started it because it was funny and lively, but descends into repetitive negativity that would make anyone want to run away screaming.

5 comments about Visualizing Data.

1. Based on the title and publisher's writeup I was expecting the book to provide in-depth coverage of various visual metaphors for understanding and manipulating data, such as "Designing Interfaces" by Tidwell, another O'Reilly book that I am very pleased with.
   
   Unfortunately it would be more appropriate if the title (Visualizing Dta) and sub-title (Exploring and Explaining Data with the Processing Environment) were switched. This book is primarily a tutorial on using the Processing Environment (http://processing.org), showing you how to create various interactive charts and composed primarily of code examples.
   
   In addition, the visualizations presented in the book are far from aesthetically pleasing. The Processing Environment has the capability to create visualizations that are not only functional, but beautiful as well. You can find a collection of visualizations at http://www.visualcomplexity.com, many of which were created with the Processing Environment.
   
   In summary I am granting a 2-star rating because the book does not deliver the expected coverage of data visualization design and even in its explanation of the Processing Environment does not provide exemplary visualizations.



2. Ben Fry hits the mark!
   
   The author jumps right into describing the process in Chapter 1, "The Seven Stages of Visualizing Data."
   He elaborates each of the stages with illustrations and examples.
   
   In chapter 2, "Getting Started with Processing," Ben introduces a software tool (named Processing) that's available for download: www.processing.org/download.
   
   From the site: "Processing is an open project initiated by Ben Fry and Casey Reas. It evolved from ideas explored in the Aesthetics and Computation Group at the MIT Media Lab."
   
   And the remainder of the title details the various stages of visualizing data with sample code you can use to develop your own visualizations!



3. 'Visualizing Data' is a book that is supposed to discuss how data is presented, sorted, stored and examined. Instead what we get is a 350+ page book that is jumbled with lots of code samples (why) and a small subset of data that is actually visualized. This is a really niche topic that I thought would be interesting to examine as I opened the book cover but thumbing through I saw few pictures (although there are a few in here that are good) and lots of java code. While it's interesting to see how data is outputted code-wise, from the book title I felt this would be more of a design discussion for the reader.
   
   I can't recommend this book. There is too much code, too much content, and the code that is contained within is all Java. I didn't get much out of it and I feel that if less code and more pictures were added the end result would have been much more solid.
   
   ** NOT RECOMMENDED



4. This book was exactly what I was looking for--chapter eight alone was worth the cost of the book. A word to the wise: rather than assuming its contents from the title alone, read chapter one thoroughly to ensure that this book is right for you.



5. I'm short of superlatives for this book or more generally for the work of Ben Fry.
   
   In my line of work, how people think of graphs is very much influenced by what is possible to do in Excel without changing the default settings too much.
   Enter Processing, a data visualization-oriented language, which makes it easy to create custom visualizations, tailored for the problem you want to address. There is a growing community around Processing and a number of truly incredible graphs that have been created with just a few lines of code. Ben Fry's own work, which ranges from simplistic to very sophisticated, is nothing short of mind-blowing. Yet this book demystifies this and make it all look accessible.
   
   It opens great perspectives for anyone interested in expressing their data graphically. Still, the title is misleading.
   
   This is not a book about, say, editorial rules by which one should construct a visualization. It is not an abstract book that offers generic advice that can be used in whatever environment. For that kind of book, pick Show Me the Numbers: Designing Tables and Graphs to Enlighten or The Visual Display of Quantitative Information, 2nd edition - books which are consistent with Fry's approach, by the way. "Visualizing Data" is really a practical cookbook that will introduce you to Processing. It offers methodological insights, but which are mostly relevant in the Processing environment.
   
   That being said, I highly recommend this book and keeping a close tab on [..]

No comments about Programming in Objective-C 2.0 (2nd Edition) (Developer's Library).

1 comments about Database Design, Application Development, and Administration.

1. Manning gives you a good exposition of the important ideas in putting together a database. The theory of relational databases is explained in enough detail that you should be able to apply this to your situation. Laying out whichever tables you need, in a judicious fashion, can take some skill. But by moving your data around, you should be able to find a suitable configuration of several tables, and the appropriate keys and foreign keys to connect these together.
   
   The other portions of the book, which discuss actually coding this, and on being a database administrator, are also important. But the conceptually hardest parts relate to the initial design. And it is here that you should focus your efforts.

3 comments about Wicked Cool PHP: Real-World Scripts That Solve Difficult Problems.

1. 'Wicked Cool PHP: Real-World Scripts That Solve Difficult Problems' is a fantastic PHP cookbook that is written exactly the way I like books to be written:
   
   - it's fun to read and learn from
   - content is broken up logically at the right points
   - layout and design is a joy on the eyes and brain
   - length is around 200 pages which is within the 2-3 (hundred) range that I like most books to be
   
   Content is broken up over 12 chapters:
   
   01. Basic script stuff
   02. Configuring PHP
   03. PHP Security
   04. Form Fun
   05. Text & HTML
   06. Dates
   07. Files
   08. User and Session Tracking
   09. Email Excitement
   10. Image Tasks
   11. Using cURL to talk to web services
   12. Other Stuff
   
   The audience for this book hits the rare area of ALL developers from the expert to the newbie to the weekend hacker. There are 76 scripts contained within that nearly anyone could find useful in any project.
   
   I love No Starch books because they don't feel like reference materials, rather they package it in a fun way from the glossy cover to smart design. No Starch gets 'it' when it comes to what geeks want and PHPites you will WANT this book!!
   
   ***** HIGHLY RECOMMENDED



2. I saw this book on a friends desk and shamelessly took it before he had a chance to read it. I have many php books on my bookshelf, too many. I can now remove quite a few and replace them with this book.
   
   When I first glanced through this book, I was intrigued by the way it was laid out. There are 12 chapters covering many topics that php programmers should know about their language and how browsers interact with a web server using php. Each chapter has many sections that cover a specific topic and most have very useful code examples. The extra feature is a part labeled: "What can go Wrong?". This is a great time saver on how to deal with common issues that might come up when you are working on your php script and implementing the example code. Most of the issues have really good explanations of how and why something could go wrong. What makes this book a real keeper is that they have the "why" explanations. I've always hated it when books tell you to do something a certain way, but never go into any depth on WHY you should do it one way or another. This book has the WHY covered very well for a great number of the examples.
   
   The style of the book makes it easy to read and learn from the examples. In my case, it makes it easy to pickup, read a few pages when I get the chance and then put it down again. I find it easy to pick up right where I left off and keep reading right on to the next example. I like the humor level too. Often authors can get a little too cutesy with their wit and humor. I find that to be a real turn off. William and Brian (The authors) do a great job of keeping the humor light and laughable.
   
   I just made some room on my busy book shelf for this book of 76 time-saving, problem-solving php scripts. I hope my friend doesn't ask for it back...



3. PHP is an easy scripting language for creating web features, but like any software it has its quirks. That's where WICKED COOL PHP: REAL-WORLD SCRIPTS THAT SOLVE DIFFICULT PROBLEMS comes into play. It's for those who have some experience with the scripting program but need more specifics to tweak applications. From scripts to process credit cards, template HTML and serve dynamic images to tracking visitors with cookies and editing images and text, WICKED COOL PHP is packed with tips and comes from two experienced PHP developers: perfect for any computer collection catering to PHP users.
   
   Diane C. Donovan
   California Bookwatch