Software Books

I know several programming languages and wanted to use Perl on my website. Within days I was able to take existing scripts and modify them to use on my site. I was able to generate several program to help maintain the site within weeks. Great book!

This is the first and from what I found "ONLY" book for a novice. I have read numerous titles on Perl and was always left with basic questions. If you want to understand Perl, read this book.

I read Beginning Perl, 2nd Ed (BP2E) to gain some familiarity with Perl 5. I do not plan to really write anything in Perl, but I find myself using other people's code quite a bit! In those situations I would like to know how the code works. I also enjoy being able to make small changes if the code does not work as expected. Perl is basically everywhere, so it pays to understand it to some degree.

James Lee's book is excellent from start to finish. I found his explanations very clear and his writing style lively. He covered just about everything I hoped to read in a book of roughly 400 pages. The book is ideal for the self-educated since it contains exercises with answers in the back. I personally enjoyed learning more about regular expressions in Ch 7, since PCRE is an important part of several network security tools.

It is easy to take a good programming book for granted. I have started and stopped reading several other books written to teach programming because their style is terrible and the assumptions they make confuse the beginner. BP2E is always conscious of what the reader has already seen. The author makes it clear when a briefly mentioned topic will be more thoroughly explained later in the book. Plenty of technical authors could learn from this example.

Even if you plan to read the author's new book -- Beginning Perl 6 (or BP3E) -- you may want to read BP2E. Perl 5 will be with us for many more years, so it pays to understand the material in BP2E. (It's possible that BP3E could demonstrate Perl 5 and 6 syntax, but I doubt it.)

Beginning Perl is a great introduction and resource. It does assume the reader has some basic prior programming experience, but either way it is very logical and easy to follow. The book is well-organized so that you can easily find what you need. There are tips and shortcuts strategically placed throughout the book to help you along the way.

I bought this book very recently, having no prior experience with Perl. I had seen a couple of scripts that other people had written, but since I have minimal programming experience I could only somewhat figure out what they were intended for.

I read the first chapter of Beginning Perl (11 pages), and read bits and pieces of the second chapter (37 pages). Then I began writing my first Perl scripts, using the book primarily for reference. It makes a great reference tool because the index is very thorough and the examples are easy to understand without necessarily reading the entire book in order. About 3 hours ago I couldn't have told you what a subroutine was or how to create a hash, but now I have completed my first interactive program using subroutines, hashes, various types of loops, error-checking, etc. That would have taken me weeks to learn if I had not discovered this book.

I highly recommend this book to anyone interested in learning Perl.

Beginning Perl really is an excellent resource for anyone looking to learn the language - novice to expert. Even if you have absolutely no programming experience, the book starts out from the beginning by covering not only things you will need to know to learn Perl, but also good general programming practices. If you are an expert programmer, the book is written in a way that makes it easy to scan through and pick up on some things that you may not know or refresh your memory on some things that may not be completely clear. The index in the back is also great for use as a reference. Nothing can compare to the usefulness of a good Internet search engine (see Google) for use as a reference, but the book does quite a good job. It is nice to have something tangible in front of you to walk you through some tutorials and build up your knowledge of the language in a methodical way.

Personally, the book has helped me to become comfortable using Perl to do "everyday tasks" (everyday in the context of an obsessive computer user), perform my necessary job functions (manipulating massive text files), and become a better programmer. I used to know next to nothing about Perl, although I did have a solid background in other languages. With this book, and some help from the Internet, I was able to become a sufficient Perl programmer within a week.

Perl is a great language that every person in the computing field should know. There's literally hundreds of great tutorials and books on the subject that will suffice, but I would stress the value of having a well-written book sitting in front of you while you learn. I would certainly recommend this book to anyone looking to learn Perl.

I have used this book and it has proven to be a highly resourceful Visual Basic and SQL Server book, that I am anxiously waiting for the release of Beginning VB.NET Databases by the same author!!!.

It's very good Books with good Price and (Wrox Press)

OK for beginners who want to know some of the innards of SQL server, but there are two major faults. One is that newbies to networkable machines will find themselves crushed under the weight of networking and communications jargon that the author never explains, and Win98 machines can't handle half of the book. Second, the last third of the book for some 200 pages has nothing to do with VB: the samples are written entirely in XML, DHTML, and a mere snippet of VBScript. There are better VB tools for creating Web apps that can handle big datasets and ActiveX, whereas XML has enfuriatingly slow performance and an unattractive and inflexible interface that looks like something pounded out on a typewriter (remember those?). 5 stars for the first two-thirds, zilch for the remainder.

I had to learn SQL programming with Visual Basic 6 in about a month's time for a project. This book taught me everything I needed to know to deliver the application. Everytime I came across a stumbling block in my code or in SQL Server 2000 I found the answer in this book.

This book will make you feel that you not only know how to make Visual Basic talk to SQL Server, it will make you feel you know more than the basics of SQL Server itself. Previous to reading this book I had no idea what a stored procedure was, or how a query works in SQL Server (I had worked extensively with Microsoft Access, and these skills were not necessarily transferable to SQL Server, though many of the concepts are similar). Now I know my way around SQL Server 2000. This book fulfilled a dual purpose.

There are chapters on Database design, SQL Server installation, SQL Server security, Querying, Stored Procedures, the SQL language, IIS, and XML. Most of the book is taken up with what developers do everyday: the storage and manipulation of data. Over 300 pages of the book is dedicated to data in general, and how to get the most out of it using VB and SQL Server.

If you need to create a VB6 (there is no discussion of VB.NET since the book predates it) database application using SQL Server, this is the book to start with. Its bulk pays off.

This is an excellent introduction to SQL Server 2000 for Visual Basic 6.0 developers. I used this book and Robert Vieira's Professional SQL Server 2000 Programming (Also by Wrox) to study for the Designing and Implementing Databases using Microsoft SQL Server 2000 exam (70-229). The 2 chapters on XML were especially good. Thearon does his best work when he works solo and this book is one of his best. I have his SQL Server 7 book and both books are well-written. I really like the "Hardware Tracking" tutorial that he follows for most of the book. This tutorial will also help with your Visual Basic skills. I have learned several new VB tricks just by following along. I hope that Thearon writes a Beginning SQL Server 2000 for Visual Basic.Net Developers.

This book makes a complicated machine like computer very easy to understand

The best thing I love about this book is the writing style of Prof. Freedman and how easily and clearly it can crystallize, the otherwise complex computer terminology, components and concepts. The explanations used here are vivid. I have owned a copy since 1997 and I have never been disappointed with anything that I needed to look up, for instance 'kludge' is described here as - "Also spelled 'kluge' and pronounced 'klooj'. A crude, inelegant system, component or program. It may refer to a makeshift, temporary solution to a problem as well as to any product that is poorly designed or that becomes unwieldy over time."

It will be hard to obtain better explanations than they are written in here.

There are several other similar Encyclopedias around which I have never looked at, because I had no need to look for another Encyclopedia.

Unlike most other computer dictionaries/encyclopaedias in its class, the inclusion of a companion CD-ROM gave this "Computer Desktop Encyclopedia" a comfortable jump-start in the superiority contest.
The book (and its attached CD-ROM) covered, in the most definitive way, all the important terms and acronyms that apply to today's computer and networking technologies. Hardware, software, and allied peripherals were adequately represented.
It is descriptive and well-illustrated, and included all the commonly used file extensions. With over ten-thousand terms and definitions, its scope is rich: in comparison to what exist now.
This computer encyclopedia ranks among the best currently on sale. However, potential buyers may be frustrated (at the moment) by its limited availability.

And too bad it's out of print. While this book will not teach you how to use a PC, it will define every computer related (and often electronics) term you can imagine. I was surprised on some of the really obsecure terms this book contained that I didn't expect it to mention. I got this book used and after reading over some of it, I'd say this is a must have on any nerd's desk as the it compares up there with as good as an internet search for explanations of PC related terms.

I work people whose computer knowledge varies from very little to a serious computer user. This reference manual is one book that all levels can benefit from. This book is the perfect manual to answer the questions in an easy to understand format without all that technical jargon.

The book is over 1100 pages and is loaded with pictures and figures to give a visual representation of the definition which makes is easier to understand some of the concepts covered. There is computer definitions, vendor breakdowns, and certification analysis and application definitions.

Some of the topics covered are networking, computers, MACs and applications. Some of the technologies included are CISCO, CompTIA, ATM, FDDI, Ethernet and token ring. Also included is a cd-rom which has over 5000 more definitions not included in the book. Overall a great addition to my technical library.

The GlassHaus "Constructing Accessible Web Sites" book has been a great find. I began working to build sites and applications for use in Web browsers that had to be used by individuals with disabilities in 1997. Over these years I picked up a lot of hard won knowledge and experience, but have never run across a resource that fully backed what I had gathered. The GlasHaus Accessibility book not only echoes what I have learned, but has provided new insights to improve upon what I already have. The best part of this book is that I can point others to it and I am assured they will be able to build an accessible site or Web applications that can meet high standards.

Many folks think accessibility is a great inconvenience, but it takes a little thinking and planning to do it right from the beginning. Having a great resource at hand makes the process a cake walk. Not only are the processes and guides helpful for creating sites that are accessible for those that are disabled these steps outlined also make the information in the site future ready. Sites that are accessible are much easier to use with a handheld PDA device or from even a cell phone browser. Accessibility for everybody in more situations improves with structuring the information properly, which is all making Web enabled information really requires to get it ready to be consumed. Is your information ready to be consumed by everybody?

I don't usually come it the "lyrical type", but to find such a worthwhile book on such a worthwhile topic is a breath of fresh air!

Above all else, it offers practical advice on how to actually do the right thing. Unlike certain titles with animals on their covers, there's more here than just reams and reams of tables containing cut-and-pastes from the man pages on the subject.

It's also of a nice size. (I know that would be no recommendation, if the book didn't actually teach you anything, but it does - and you don't feel intimidated, like you can when you pick up some dirty great Red tome from a Certain OtherPublisher.) You feel as if the subject is managable. Knowable. It may be just me, but if a book is smaller than my own head, I generally feel that there's an outside chance I may be able to fit the contents inside my own skull!

I'll have to keep an eye open for these blue things... they're quite good.

Of the books and resources that I've read on accessible web sites, this is by far the best - especially from a UK perspective.

The main UK legislation that specifically mentions web sites and accessibility comes into force in October 2004 which, at the time of writing this, is still over two years away. This means that there isn't a great deal of information and certainly no legal cases that we can draw on from our country, so we have to look elsewhere to see what is happening.

This book benefits in that, although it does cover Section 508 and other already in place legislation, it also gives a great all round understanding of the topic, and is very easy to read. Having chapters written by different authors means that you get a far greater depth of experience and information, which can only benefit the reader.

If you're going to buy one book on accessible web sites, this should be at the top of your shopping list.

Two new words have joined the vocabulary of web designers in recent years - usability and accessibility. You will often come across them used in tandem.

Usability really became an issue when Jacob Nielsen infamously denounced Flash as 99% bad. Accessibility became a priority for web developers working on government projects after Section 508 was brought into law in the United States.

Accessibility became an issue in Australia during Maguire vs SOCOG in 1999, when a blind man filed a complaint with the Human Rights and Equal Opportunity Commission (HREOC) that neither Olympic Games tickets purchasing information nor the souvenir programme were available in Braille. Most importantly he alleged that the SOCOG website was not accessible, and to make it so would have been well within budget. SOCOG was found to have discriminated against the complainant and damages were awarded against the organization.

Accessibility is now a civil rights issue. It is also not that difficult to implement on a website, once you learn how it can be done. This excellent book, Constructing Accessible Web Sites, teaches you all that and more. It is the first on its subject, and will not be the last, but it is damned a good beginning.

All eight co-authors have been pioneers in the field of accessibility, and Glasshaus deserves praise for having assembled such a team. They cover more than website accessibility - their expertise extends to the accessibility of web design tools themselves. An apt reminder that the web is as much about reading as writing, for writers as much as readers, a real medium of two-way communication.

All websites can now be made accessible to varying degrees, even Flash websites since Flash MX, as Macromedia Senior Product Manager for Accessibility Bob Regan demonstrates in Chapter 10. So there are no excuses for failing to add increased accessibility, and usability for that matter, to that new project you are just about to commence.

Ensure you have a copy of Constructing Accessible Web Sites at hand when you begin. And also take a look at another equally essential reference on the subject due out any day now, Joe Clark's Building Accessible Websites. Accessibility is the newest and most necessary website building skill. There are no excuses now.

The GlassHaus "Constructing Accessible Web Sites" book has been a great find. I began working to build sites and applications for use in Web browsers that had to be used by individuals with disabilities in 1997. Over these years I picked up a lot of hard won knowledge and experience, but have never run across a resource that fully backed what I had gathered. The GlasHaus Accessibility book not only echoes what I have learned, but has provided new insights to improve upon what I already have. The best part of this book is that I can point others to it and I am assured they will be able to build an accessible site or Web applications that can meet high standards.

Many folks think accessibility is a great inconvenience, but it takes a little thinking and planning to do it right from the beginning. Having a great resource at hand makes the process a cake walk. Not only are the processes and guides helpful for creating sites that are accessible for those that are disabled these steps outlined also make the information in the site future ready. Sites that are accessible are much easier to use with a handheld PDA device or from even a cell phone browser. Accessibility for everybody in more situations improves with structuring the information properly, which is all making Web enabled information really requires to get it ready to be consumed. Is your information ready to be consumed by everybody?

I will be brief.
I only have 4.5 years experience as a programmer, of those only 1.5 were spent on C++ and I have no experience whatsoever in game programming;
the new stuff I learned from this book could be printed on a letter page or less.

This is just generic, and rather primitive, data structures and algorithms book, that applies them to making a small game instead of usual example search/whatever programs. Sometimes it feels like a data structure was used merely as an example that fit in that place in grand example-place matching, and not as the most useful or efficient one...

One could probably turn it into "Data Structures for Database Server Programmers", "Data Structures For Embedded Device Programmers", or "Data Structures For Solving World Hunger" with copy/paste and minor grammatic corrections ;)

Ron Penton, Data Structures for Game Programmers (Premier, 2003)

I don't normally get all googly-moogly over programming books. In fact, I just took a quick look back at my reading log since 1999, and a select few have gotten four stars, but nothing above that. But I picked up Penton's nine-hundred-page tome on Thursday and I finished it on Sunday. Nine hundred pages in four days. I've only been keeping track of page counts over the past year, but the books I've read that have come closest, page-wise, have been Robin Hobb's lovely novels, three of which I read earlier this year hovered around eight hundred pages. I read the shortest of them in eight days. And I love Robin Hobb.

Data Structures for Game Programmers is a wonderful book in no small part because Ron Penton was still an undergrad while writing it. Which is, of course, also the book's main problem, because someone like me who last saw ivy-covered halls well over a decade ago is likely to be sick with envy that some little greenhorn has already found his way into the world of professional computer-book publishing (and by "professional" here I don't mean "published by recognizable press," I mean "the kid's already published three books in three years, and they're ALL monstrous tomes, when does he have time to program?"). But let's face it, you expect something different when you read a book by a young writer, be it the hot new novelist or the new kid on the programming block. And Penton delivers it; Data Structures for Game Programmers is, if you're a programmer, the most readable computer book you've ever come across. Penton seems to have a healthy disrespect for textbooks, which he alludes to a few times in the course of the book, and it shows in his writing; he wants to write something that will teach you more than a textbook by being more accessible. And in this goal, he succeeds. Brilliantly. I learned more about C templates from reading this book than I have in any other three books devoted to nothing but templates, and here they're just referred to a few times in passing. How is this possible? Because Penton explains things in language far easier to understand than that of most programming books; simply put, he hasn't yet been so overwhelmed by jargon that he can't see when he's written something the layperson might not be able to understand, which is a common ailment among programming authors.

Also, there's been some minor grumbling from some critics about the book's insistence on reinventing the wheel. Of course it does. That's how you learn to program-- you bang away at it, doing something that's already been done, until you figure out why it's done that way. There may be five or six people on the planet who can read it in a textbook and immediately figure out why it's the case (and, one assumes, they are the same people as those critics), but the rest of us are much happier seeing it this way.

If any computer book publishers happen to be reading this, you, especially, should be reading Data Structures for Game Programmers. See what it's like. Try to get the rest of your authors to emulate it. You'll have much happier customers that way.

This is one of the handful of books I've read since getting a library card again (a total, in fact, of four since 2003) that, after returning it to the library, went back on my Amazon wish list, because I want a copy for myself.

This book actually teaches Data Structures!! Data Structures are the essence of programming. Ron manages to present all the basic Data Structures and the most famous algorithms in a clean and gentle way.

Many many thanks to Ron Penton for his help! Ron Penton really knows how to write a book! His way of writing shows that he knows the subject perfectly and presents it in a way that anyone understands what he is talking about. No matter how hard the topic is! By the way, Ron Penton has a great sense of humour!

If I could I would give one more star for the GREAT job he did with the CD. Although I intended initially to learn Data Structures, I also learned SDL. Perfect combination for someone who wants to start writing games!

A pre-requisite for any book on Data Stuctures is that the person should be comfortable with the syntax and semantics of programming in a high level language such as C++ or Java. Hence this book assumes that you are comfortable with C++ and OOP. There is no such thing as Data Structures for Absolute Beginners. So discard the review with 2 stars. Overall this is an excellent and interesting book on Data Structures.

Bottom line is this, you can find the information presented in DS4GP in any other good book on data structures but what sets this book apart is the presentation, organization, practical content and the writing style of the author.

It's definetly not for beginners or for a person looking for a very detailed book on data structures that covers AVL trees and red-black trees. But for the other 99% its a must buy.

i wanted a book to brush up on some data structures since i've been out of programming for a few months. plus, most of my learning of these has been self taught and from the internet where there is limited (good) writings on more complex subjects such as programming. so i wanted to have a fresh perspective. not only does the book contain very useful details in many areas and to the point information (gets to the first data structure by page 14!) but the author somehow makes this stuff fun to read.
the author doesn't go hugely in to depth in some areas but that's pretty much what i wanted since i am already familiar with how to use most of the stuff. very good book and i'd highly recommend it. hope this author continues with more books!

Not soemthing I would read cover to cover, but the individual "Hacks" that I have read are pretty good. I have lots of books along this line and this is one of the bet. I put it up there with Stu's "DV Rebels Guide" which is also incredible. If you like the Rebel guide, you will probably like this as well. Lots of good stuff. Enjoy!

Great book with great content I recommend it to anyone who want to take there film making a step forward and is to busy or lazy to download the information from the internet becaue it is all there. Spread around of course but you will find every piece of information even most of the pictures used in this book so. If you have time and dedication you can save yourself the money by looking it up on the internet.

This book covers many aspects of video. Labeling tapes, making excel spreadsheets for saving information, time code on tapes, how to achieve certain effects, lighting, and green screen effects just name a few. The book is general to most all video software and is a very usefull tool I'm glad I purchased. Don't let the term "HACKS' fool you it 's only refering to tips or tricks.

I found the book to be very practical and have the
kind of "nuts-and-bolts" pointers that I like. You
don't have to read it cover to cover (I didn't) but
can pick it up and go to the points that interest you
or where you are currently in need of help. It refers
to various "commerical products" that the author has
used to get the job done. I found this helpful. With so
many competing products to chose from it's nice to
hear, "If you get product X you'll be able to do Z,"
rather than buying and hoping (or not buying and
wondering). Kuddos to the author.

I learned so much from this book. In fact, I've already implemented several of the ideas and have had great results. If you're semi-professional (video has been added to your responsibilities but you have no experience with this medium) BUY THIS BOOK.

Who would have thought of parchment paper and clothes pins to diffuse light and create a softer, more natural light over the subject? That's just one of the great tips I've already started using.

I've bought several digital video books while trying to learn this medium, and this has been by far the most useful.

This book will definitely help you get your projects into Project 2000. Great ideas on both Project Management and Project 2000.

Eric,
Thanks for a superb job on your Dynamic Scheduling book and the accompanying CD, which I make use of as well. I have been managing projects at fortune 500 companies for nearly a decade. I have read many books, I have taught and I've done some writing of my own and with out question, your book is the best I have ever read. It is obviously written from the perspective of someone who knows project management as well as Microsoft Project. Often there a slight disconnect between instructors and authors and those of us in the real-world of project management, Dynamic Scheduling shows that you have your foot firmly planted in both worlds. Some people consider me a Microsoft Project expert, but I have stolen so much useful information from your book that I probably should be paying you royalties. Thanks again and I will be on the lookout for your next book.

I've been using MS-Project for a few years now, starting with Project 98, and now 2000. I've always looked at it as a quirky tool that I use to create task lists, rough schedules, and charts to use in project plans. I've never considered it a serious tool for planning, let alone controlling a project. "Too many inconsistencies," I thought, considering myself an intermediate user. I've taken CBT's, and read MS-Project for Dummies - what more should I need?

This book has changed how I look at the tool, and how I schedule projects. MS-Project really does work - you just need to know what is going on behind the scenes to make it work for you! The author clearly walks you through how to perform tasks from a project manager' perspective (I' not a PM, but happen to do some of it, so don't think you need to know all about PM to benefit from this book), and examines common pitfalls and best practices gathered from obvious extensive practical experience using the tool. The title is accurate - the book revolves around creating a "dynamic schedule," i.e. one that easily updates as variables in your project update. The chapter on optimizing the schedule was especially helpful, and immediately applicable.

MS-Project is not a quirky tool for high-level plans and pretty pictures - it is a powerful project planning and controlling tool that will cut hours and frustration out of your project. Impressive text - do yourself a favor and read it cover to cover. You'll be happy that you did.

Finally, a book that promotes the use of MS Project to do real project planning and tracking, rather than just using it to draw pretty charts. The author brings the reader up to speed on the essentials of MS Project, and then takes the reader through the process of optimizing the plan and ongoing project tracking. It provides a clear rationale for using MS Project to build a model of the project that can be used to do what-if analysis and to help the project manager to see the effects of change on the plan when reality differs from the plan (always does). The book clearly draws on real-world experience in trying to balance and optimize resources, as shown in the section that describes a resource critical-path method. The book is clear, concise and practical. The techniques show how MS Project can actually be useful, rather than as something a project manager is forced to do just to keep management happy.

I was searching through bookstores and Amazon.com for a good book on how to best use Microsoft Project. There are a ton of books out there that teach you Microsoft Project, and I own two of them (Mastering Project 2000 and Project 2000 Step-by-Step). These books are great at describing features, but you can also get that information with the Help files.

For anyone who has used Microsoft Project can tell you, there are several ways to set up the application, some of which is helpful, and some of which can have you very frustrated.

What I wanted was not a description of all the features, but how to best set up Microsoft Project. I stumbled on this book on Amazon.com, and it proclaimed to be the book I needed.

I was not disappointed. The author draws upon his years of experience in developing and managing with Microsoft Project and leading the Microsoft Project department at the International Institue for Learning (IIL), upon the lessons from the many other instructors, and from his students. Being able to learn from others mistakes and tips is worth the price of the book alone.

The author's stated objectives in setting up Microsoft Project are to:
- allow the schedule to be dynamic, so that when reality comes, as it will do several times during a project, then the schedule will dynamically adjust to reflect the future
- need as little care and feeding throughout the life of the project as possible, so you can spend your time managing the project, not in front of a computer trying to update the status and plan the future (when you don't have the time).

The author walks you through step-by-step on how to set up Microsoft Project to achieve those two goals. He discusses:
- the best settings for the project's properties
- how to properly establish a work breakdown structure (WBS) and describe its elements in the project tasks
- what variables need to be visible on the Gantt data entry chart to watch how Microsoft Project will alter variables
- a complete discussion of the Scheduling Formula
- descriptions of Fixed Work, Fixed Duration, and Fixed Resources, and the concept that a task does not remain as one of these, but should be changed to control how Microsoft Project will react to replanning
- when to use constraints, deadlines, and milestones, and how to add constraints so you aren't held responsible for the impact of other organizations not fulfilling their commitments
- assigning responsibilities
- how to title resources
- when resources can be "pooled"
- how to optimize the schedule (whether for time only, time and cost, or for time, cost and resources through the use of a Resource-Critical Path - aka Critical Chain)
- the use of Monte Carlo simulations
- how to handle (and possibly hide) project buffers in a schedule
- the use of one-page reports (always!)
- establishing baselines
- tracking progress (the six basic situations and how to indicate them) and updating projections and assignments (through workgroup features or manually).

The author also describes three "hazards" with Microsoft Project, namely facility and machinery costs, gross work time vs. dedicated work time, and the use of the Effort Driven tag.

Facility and machinery costs are poorly handled by Microsoft Project, and the author describes some workarounds.

The author does describe the difference between gross work time and dedicated work time, and that planning usually is done with dedicated work time, but the difference between the two are often not correctly accounted for. Recent findings suggest that worker efficiency is not better than 65%, so this difference can be enormous. The author describes two ways of handling it when he describes the subject, and then describes a third method much later in the book (and says that method is popular). Unfortunately he does not describe the advantages and disadvantages with the approaches, to include cost implications. I would highly suggest that you only plan in gross work time, knowing the inefficiencies. By the way, Microsoft doesn't make this very easy either as the efficiencies of individual resources against a task is not an included field for the assignments.

The author describes that there are problems with using the Effort Driven tag, and gives great advice on how to deal with it (always turn it off if the task is not Constant Work - but watch it as Microsoft Project can and will change it on you). His description of how Microsoft Project treats the Effort Driven tag, however, was not complete. The Effort Driven tag attempts to hold Work constant in addition to the variable that you declare as fixed. Since the Scheduling Formula only has three variables, trying to hold two of them constant while changing the third obviously causes some confusion. I don't have room to describe how Microsoft Project will react when you set this tag, but it's not always "Effort Driven". Just keep it turned off!

There is some room for improvements in this book:
- Earned Value Management was not mentioned (except in the glossary). The author should either explain that he doesn't find it useful, or explain how he's used it productively
- The Index is weak for the volume of information included in the book
- The advantages and disadvantages of each of the approaches to hide management reserve in the schedule should be described
- There should be graphics showing how to set up constraints, milestones and deadlines, to include un-hidden management reserve
- There should be example one-page reports included
- Update for Microsoft Project 2002

Despite these shortcomings, you will not find another book that comes close to this on how to use Microsoft Project. If you manage projects with Microsoft Project (even if you use Project 2002), you should have this book on your desk (not your shelf).

Rob have wrote a book that should have been use during the crazy internet start- up era. Maybe all those companies would be thriving if they have gone through Rob's boot camp. Ok maybe not all of them but I feel that 80% of the dot com companies may be still existence.

I am still working on my hi-tech company but I have not been able to because they are not up to my standards. I got good ideas but I am just not feeling ready to go solict for funding just yet.

But anyway this is a great book! Rob gives a lot of good information that you would normally pay big money for a consultant to tell you the same thing!!

The book is 6 years old, yet the topics covered here is still useful for any entrepreneur to get $$ from venture capitals (VC):

1.Borrow $$ from friends/relatives to build a prototype
2.Beta test this on large and small firms, to build up clients
3.Build a better product/service based upon their feedbacks
4.Write a concise business plan with killer PowerPoint slides
5.Get the insider VC to arrange meetings
6.Answer intelligently on any VC concerns
7.Get the $$$, start the firm
8.Grow the firm for 3-5 years with track records
9.IPO and make Billion$$$

Sounds like a great formula! But this is 2007, VC is not the only game in town. They are Private Equity, Hedge Funds, Debt Financing, many other avenues to get $$$. Rob Ryan, are you contacting them?

If you are an entrepreneur. Do not do anything before reaqding this book. It is easy to read and understand... No business jargons or anything...

...is that it's not out in paperback so that I can buy 50 copies and give them out to people to show them why I babble on about it. Rob Ryan's "Entrepreneur America" is the *single most practical* book about entrepreneurship you will find on the market today.

Rob founded Ascend, and he tells you exactly how he did it. And even though Ascend was a pure technology play, his lessons are broad enough that they can be applied to non-technical inspirations as well.

Kudos also go here to Phaedra Hise. She has captured the voice, verve and essence of Rob Ryan and got him down cold on paper. Quite an achievement.

This books is a must read for anyone involved in a hi tech startup. I am with my second private technology company, and it provided some great insight into where we are, and what we need to do. For someone planning to start their own company or join someone elses, you should actively answer all of the questions put forth in the book. It will help you understand what the real chances for success are in a world full of great ideas without markets!

Working with Exchange everyday this is a book I recommend to any IT person wanting to know more about Exchange. This is the best Exchange book I have purchased so far. Don't pass this book up.

I purchased this book as a sys admin working with Exchange Server for the first time, and this book took an already complex product and made it more frustrating. I was looking for a book that would explain the capabilities of Exchange Server and how to configure it to exploit these capabilities. This book seems much more concerned with migration of existing enterprise messaging systems to Exchange and upgrading existing Exchange installations than actually setting up Exchange from scratch.

While I am sure that there is good info in this book that I will eventually use, I would definitely not recommend this book to someone who didn't know quite a bit about Exchange Server to begin with.

This book is giving you hundreds of useful and practical advises about Exchange administration & configuration. Jim Mc Bee knows what he is talking about. Remember there is NO reference book about Exchange but don't miss what is in this one.

I don't usually write reviews, but I had to for this book. The author not only knows his stuff, but is capable of putting his indepth knowledge in a very step 1,2,3 approach, something I have found to be an exception in alot of what I read. One think I have to note, I am the main systems person for a trading firm, and we are required to do message journaling (keeping all communications for three years). I have tried to find information on this topic and how to implement it on many message boards and other forums, as well as in documentation. Being that I did not know the actual term was "journaling" I found this impossible, and therefore, have been backing up every single mailbox, and that does not even "legally" do the trick. This one 2 page section on how to implement this makes this book worth more than money, because we are now legal. To the author, thank you for your help, and I look forward to anymore lit. that you produce!

I picked up this book by accident thinking it would be a good "starter" book. AKA - Having never used exchange server before, I wanted a basic book for setting up accounts, addresses, basic administration, etc. This is not that book at all. If you want a really low level book, look elsewhere. However, I quickly found out Exchange Server is intuative enough that it's easy to figure out the basics all on your own just from playing with it. Aside from that, I am greatly impressed with this book. It's solved every problem I've ran across, and more. The best thirty bucks you'll spend this year.

This is a benchmark book for interactive design. It separates the design process into information design, interactive design and presentation design. Those who head the process and focus on information design tasks at the beginning of an interactive project will find that costs are lower.

Information design changes are easiest at the beginning of a project and create large cost problems at the end.

If you have proceeded with good information design then interactive design and costs are much less difficult and less expensive.

Finally if you have made good information design and interactive design decisions, then you have a vast arrays of how to present the final product. It is at this stage the costs the highest with graphic designers, video producers, web developers, programmers and so on.

Read the book and memorize the process.

The book promised a lot based on previous readers' reviews and the publishing house's reputation but I was disappointed with its contents. The information is well presented but too simplistic. Lacking any further elaboration this book is of little use if you have some experience in the field of interactive design. A good brain-storming session at home would come up with the same findings of this book.

I have had this book for 4+ years. I loaned it to a friend once who didn't return it, so I bough another one.

Among the dozens of books I own and read on usability or project management, etc. this one is fantastic - a real stand-out.

The one drawback is that it's not as contemporary/up-to-the-minute as newer books. [shrug]

This is nicely organized, introduces important concepts and explains them in plain english. I used it as a textbook for a multimedia class and it was well received.

You will not find fancy tricks and designs, but you will get a good overview of multimedia, interface design and project management. It is 'outdated' so it is not suitable for experts but its information is excellent for an intro class, especially for people with little graphics experience.

For once, someone makes the distinction between information design, interaction design and presentation design. This book was invaluable in helping our division more clearly define our process for product development.