Software Books

Best off shore book out there... great info...lays it out pretty straight. Easy to understand and follow.

This volume is well-written, lucid and easy to follow. The authors have done an excellent job in providing an explanatory framework for offshoring, as well as giving a realistic look at potential costs and benefits. Their list of suggestions and guidelines is comprehensive. The book avoids the trap of becoming overly technical and steers clear of being specific to any particular country or industry. I was pleasantly surprised to find chapters on such important topics as country-specific legal pitfalls, privacy rights issues, and how to sell the idea of offshoring inside a company resistant to the idea. The authors livened up their material with numerous case studies to illustrate key points. The level of detail they provided on how to write a solid Service Level Agreement (SLA) was also impressive.

Overall this was an excellent volume, and the only two objections that I have are both minor. First, the book could benefit from a small amount of updating; some of the data, especially in Part I of book, dates from 2001-2003. In any other discipline, that would still be considered fairly recent. However in technology, that verges on being stale. In addition, that was the period of the global downturn in IT. The authors' data would be obviously impacted by that global economic event. To be clear: I do not believe that any of the authors' points would be reversed by updating the data. On the contrary, I expect that current data would only strengthen their points, as the trends they identified have only accelerated since the book's first publication. Second, as noted earlier the authors provided several cases of companies who tried offshoring and either failed, or suffered setbacks. Given the fact that offshoring is not the cure-all for every company, it would have also been useful to see a couple of case studies of companies who investigated the offshoring option but decided against it. It is just as important to understand why a company declines to offshore, as it is to understand why they would undertake to do so.

This is a book that I wish I had read before working on several offshoring/outsourcing projects for former employers. It is highly recommended for anyone who is contemplating the offshore option, or who has recently been put in charge of making such an option successful.

This is a rather comprehensive look of why software
development gets offshored and of how to do it right
should you decide to try it yourself. The authors are
an academic and a consultant, making the book an
appealing blend of evidence-based theory and practical
advice. The focus is primarily on software
development, with some attention paid to such
IT-enabled services as call centers.

The two most appealing things about the book are its
maintenance of a practical tone and its
comprehensiveness in identifying the many things you
need to get right to get offshoring to work right. For
example, international projects tend to get into
serious difficulty if the customer is unwilling or
unable to provide sufficiently detailed specifications
to bring task ambiguity down to the level that can
survive the communications problems caused by distance
and cultural differences.

The authors put a lot of effort into explaining why
some countries have been successful at growing an
offshoring business and others not. This insight is
valuable for companies into offshoring for the long
haul, as you need to understand how wage rates and
technology depth wax and wane over time.

The book also has a number of chapters written by
specialists in such important ancillary areas as
international contacts and managing cultural
differences. All in all, a very useful book.

This book does an excellent job of linking offshoring to a company's business strategy. Many companies are pursuing offshoring to take advantage of lower wages in other countries. Chapter 5 shows how cost reduction can be strategic, and the other potential non-cost-based advantages of offshoring. Its treatment is also balanced, showing the downsides, costs, and risks of offshoring as well as the benefits. And it talks about choices companies have in implementing an offshore strategy.

I am Executive Director of a research center on process management, and we have done research in this area. I know and respect Erran Carmel, the author, and Peter Schumacher, who co-authored Chapter 5. Peter's work is grounded in consulting that he has done at the Value Leadership Group, which advises companies on how to think beyond cost cutting and view offshore as an opportunity to build unique competitive advantage.

"All things being equal, any manager would prefer to manage a co-located team rather than a distributed team," how true. Authors Erran Carmel and Paul Tija believe that IT managers need to feel as comfortable with managing distributed teams as they are with co-located teams. They intend their book, Offshoring Information Technology, to act as a primer for IT professionals, students and teachers in business and technology programs as well as policy makers and analysts in and around governments. That is a lot of end parties to satisfy, so does this book hit the mark.

Erran Carmel had previously authored, "Global Software Development Teams", in 1999, and has deeply focused on the topic of developing software with global teams for years. It is obvious that a researcher was one of the co-authors, as very accurate listing of references are made, more than you usually see in many of these books on offshoring. These references provide another list of papers and publications that the reader can use for further research. The book makes excellent use of cross-referencing between topics, which also adds to its usage as a good reference tool.

Right off I like the preface in which the authors define the terms offshoring and outsourcing. Since I agree there are many strange definitions leading everyone to think outsourcing means offshoring, this needed to be included. The offshore stage model, previously defined by one of the authors in a research paper, puts the offshoring numbers in to perspective by dividing it in to stages and the number of Fortune 1000 companies currently using the offshoring model. These numbers may be surprising to some, as the actual usage is much smaller than is played up in the media.

The book is full of case studies, most of them fairly interesting. The case study in chapter 9 is meant to show the difference between working in a low-content country versus a high-context country like India. I, along with I believe many practitioners, will look on this case study and say that Christina (not her real name) was not a good manager, no matter where she was working, if they thought dumping a bunch of new work on a team was not going to impact the schedule. Low-content or high-content country aside, the project manager made too many assumptions and may not be the experienced project manager that she thought she was. I think others will see the same when they read it. Another real life case study gives an example of one company trying to do a comparison between countries; what do we learn from it, price wins out over quality in the end, which in reality is often the case.

The emphasis on knowledge transfer is exceptional. This area is often glossed over in many offshoring books. Chapter 7 which is dedicated to managing the offshore transition defines different ways of undertaking knowledge transfer. One of the ways that they describe is to have the developers work in different positions, i.e. put them in to the user's position, so they understand why the user works the way they do. They state that this is new. I started out in banking twenty years ago and this is how I started out, working the user positions of the applications which I was then to develop and maintain, so I do not think this concept is new. But perhaps the authors mean this is new for offshore outsourcing. In all though this section on knowledge transfer is valuable and looks at all of the different types of transfer: skills, process, domain and work and cultural norms. Good emphasis on the fact that the easiest one to achieve is skills transfer, but the other ones are more difficult to achieve. For example it is more difficult to have someone work on dispute resolutions app for credit card processing, when they do not understand how credit card processing works.

Chapter 8 on overcoming distance and time emphasizes and outlines virtual team management. Much of the information presented is included in many books on virtual team management, but as this book is a primer for IT managers, it has a place in this book. Readers will find the suggestions on iteration development; formalizing the iterations and frequency of iterations particularly helpful in a real situation. I whole heartedly agree that this is what builds trust. If you have frequent deliverables, and the remote team meets those frequent deliverables, i.e. they do what they say they are going to do, trust is built. The authors also define the range of deliverables and that it can be anything: plans, outlines, prototypes, simulations, design reviews, test results, software code reviews, module integration and documents. Again I wholeheartedly agree. This will be an area that many IT managers may have to get used to because at first to some it seems like "make work", when in fact all of what is delivered from the offshore is and should be useful for fulfilling the project.

There are a few situations where puzzling statements are used such as the quote on pg. 28, just before a section on IT-enabled services. The quote refers to E-loan and its well-documented offering to its clients of a couple of years ago. At the time E-loan offered the users of their loan service to Press 1 if they wanted their loan processed in 1 day in an Indian center, or to press 2 if they wanted their loan processed in the US which included the statement that the processing may then take longer. In March of 2004, this was written up by many Indian firms as admittance by a US company that Indians are faster. It seems strange that the authors use this statement with no no explanation; for example was it really an admittance that Indians are faster or did it really mean E-loan had 4 times as many processors in India versus the number in the US, thus accounting for how loans could be processed faster there. Or were they working round the clock in India versus only one shift in the US, another reason for the difference. In other areas the authors go to great lengths to explain issues which are reported in the press, such as how offshore labor rates are reported in detail and what they really mean versus the actual total cost of ownership.

The book contains an excellent discussion on the different types of risk, very detailed, to a level not usually defined. Only one area, contractual risk, seemed to be lacking. The authors state that a buyer can mitigate contractual risk by signing a contract with a US company, if you are a US buyer, or with a UK company if you are a UK buyer, i.e. with a company which is also domiciled in your location versus in the offshore location only. The authors also refer to the chapter on Legal issues of offshoring where contractual risk will be further defined. In that chapter, however, only mention to reduce contractual risk is to work with providers who can provide a combination of onshore/offshore resources, thus enabling a buyer to access the provider's onshore resources if necessary. They seem to fail to mention one of the bigger issues; if the contract does go awry, even if you are dealing with the big Indian players, most of the assets that of that vendor are located in the offshore location. If any case, you will have to bring suit against that vendor in their home country. Large buyers already seem to be aware of this based on both outsourcing and vertical conferences I have attended over the last couple of years.

There were two areas where I thought more emphasis could have been made, if this is a book is really meant to assist IT professionals. One of these areas is helping the IT manager assess their own offshore readiness; how do they feel about the process, are they ready to change how they work, are they ready to manage by not walking around? The second area of missed opportunity is assisting IT professionals in defining what could be a new role for them in the global environment, for example by working in and/or managing the offshore office which is responsible for managing the onshore and offshore outsourcing for a client.

Offshoring Information Technology is an informative and educational book for IT managers looking to define their place in the offshoring world. The details provided on the offshoring process and through the case studies will make it easy for an IT professional to determine where they may need to gain additional knowledge to move their career forward. The book will be most useful and most familiar to those IT professionals currently working in or with large scale enterprises as most case studies and examples such as in total cost of ownership and the governance areas, use examples from large enterprises. This book is highly recommended for IT professionals who are looking at career development as well as those persons who are in a position to help their countries promote their outsourcing capabilities.

This book is a true student service for online learning and is a great step toward online student retention! It covers everything the online student would need to know in order to succeed in a self-paced, self-motivated, and technology dependant environment!!

I compared Online Student Skills and Strategies Handbook (Pearson Longman 2006) to E-Learning Companion A Student's Guide to Online Success (Houghton Mifflin 2005) in order to select a resourse to support distance learning. I found Online Student Skills and Strateiges Handbook much more useful, learner oriented and readily accessible. It includes large, clear screen captures to accompany step by step directions. It handles practical topics like using Rich Text Format (RTF), practicing netiquette, storing lessons in a binder, and submitting assignments. It also includes cross references to other relevant chapters in the handbook, and it includes other Internet resources for each chapter. In comparison, E-Learning seems too textbookish. While E-Learning has a useful glossary and index, Online Student Skills and Strategies has a glossary, index and Webliography.

This is a valuable resource for students interested in a successful on-line learning experience. The straightforward and practical examples should help guide everyone from novice to experienced.

I was very impressed with the format, content, attention to detail, step-by-step approach to help users work through technology, and the success-oriented focus of the text. The first chapter utilized an innovative and unique assessment to help users identify what they already know and what they will need to focus on to learn. The text is a well-designed and non-threatening resource for any online user.

I think this text is a practical and useful guide for both novice and experienced online students. The information is very well organized throughout with a couple great appendices containing websites and computer skill tips. The helpful screenshots and lay flat binding are a plus for use as you are working on the computer.

RMAN is the present and the future of Oracle solution for backup.
It has a simple concept, but a great variety of commands, by this way, as a solution for all the complexity inside the RMAN solution, Oracle Database 10g RMAN Backup & Recovery come as a special "friend" to help us discovering all posibilities inside Oracle RMAN software.

I had no idea about backup and recovery but after reading this book and trying out the examples, I can say with confidence I can recover a RMAN backed database. Written extremly well!!! One of the good technical boooks I have read....

We had to install and configure Oracle10g 4 node RAC with ASM+FLASHBACK and implement backup/recovery procedures using RMAN and Veritas Netbackup. This book covers everything I need to know in depth.

I had bought his book on Oracle 9i RMAN Backup and Recovery...
And very much impressed with the technical details and examples given in the book... Same way, the book on 10g also excels in technical depth and details...

Backup and Recovery is one of the most critical tasks that a DBA has to perform. Sadly, it is also one of the most misunderstood. RMAN should be the tool of choice for backup and recovery for Oracle databases. There is so much that can be done with RMAN.

What Robert and Matthew do is break it down piece by piece. There is a great intro and they build on that in subsequent chapters. If you want to link RMAN directly with your backup software (i.e. Veritas, EMC, Legato, etc..) then the authors show you how. I used the Veritas piece to link RMAN in and it worked flawlessly. They go over the latest features including block changing files (for faster incremental backups), merging level 1 and level 0 backups (for faster recoveries without the overhead of backing up the whole database), and even cover what the flash recovery area is and how to use it. There is so much great material packed in this book. Yeah, you can try and read Oracle's docs, but rather than just show you how to do it, the authors also teach you why to do it.

You can read this book chronologically or use it as a reference. The authors writing style make this book a great joy to read. They also include a lot of great examples in case you like to learn by seeing.

I would highly recommend this book if you are an Oracle DBA, whether you use RMAN or not. Afterall, RMAN is what you should be using :).

The strength of this book is its combination of breadth and completeness: there is working code (well beyond the toy stage) of a large number of different AI systems that cover a large subset of what is commonly considered AI.

The programming itself is rather basic, and very straightforward. In many places an advanced programmer would have avoided a global variable, unified code through the use of higher-order functions, had functions communicate through a shared local environment, created a lazy list, you name it.

The author avoids most of these more advanced approaches in order to present the ideas behind the approaches without being sidetracked into programming technique issues, and that is the correct choice for this book. Even as it is, there is already the duplicity of teaching Common Lisp and teaching AI programming.

That being said, the code in general is not bad at all, even though I wouldn't want my students to learn CL programming from it. The author has simply bent down to the level of, a good C programmer, and worked from there. His main intention being to teach AI programming approaches, he has spent much less time to raise the programming level of his audience.

Knowing the author's level of Lisp programming, I can't wait to see a book by his hand on how to use abstraction as an organising principle in programming.

I have no background in computer science or AI, but found myself needing to use Lisp for various creative and artistic purposes. I've spent a lot of money on books relating to Common Lisp, but I wish I had just gotten this one and Touretzky's "Gentle Introduction to Symbolic Computation." The particular strengths of this book are its detailed discussion of advanced topics, especially optimization, and the practical overview of current and historical AI topics through programming examples. Very clearly written.

This book is equally excellent regardless of whether you wish to regard it as:

a) A historical study of Artificial Intelligence, with USABLE examples of code, or

b) A book presenting techniques for programming in Common Lisp.

As a reference about Common Lisp, it is certainly lacking, but this is no great problem when both the Common Lisp HyperSpec and Steele's book are readily available in electronic form. It provides something more important: SIGNIFICANT examples, and significant discussions on WHY you would use various Lisp idioms, and, fairly often, discussions on HOW pieces of Common Lisp are likely to be implemented. Its discussion of an implementation of the LOOP macro, for instance, provides a very different point of view than the "references" to LOOP. (Contrast too with Graham's books, which largely deprecate the use of LOOP.)

From an AI perspective, it is also very good, providing WORKING SAMPLES for a whole lot of the historically significant AI problems, including Search, PLANNER, symbolic computation, and the likes.

It would be interesting to see parallel works from the following sorts of perspectives:

- The same sorts of AI problems solved using functional languages (e.g. - ML, Haskell), to allow contrasting the use of those more modern languages. Being more "purely functional" has merits; such languages commonly lack macros, which is something of a disadvantage.

- The use of CL to grapple with some other sorts of applications, notably random access to data [e.g. - databases] and rendition of output in HTML/SGML/XML [e.g. - web server].

This book has been called "The best book on programming ever written". I'd have to agree--it is certainly the best that I've ever read.

William Zinsser said, "The essence of writing is rewriting" and the same can be said for writing computer programs. Norvig's book presents this process--how the limitations of a program are overcome by revision and rewriting. What sets Norvig apart as a writer is that, amazingly enough, he can write about debugging (the most dreaded part of computer programming) and make it a fascinating read!

Lisp has been getting a higher profile lately because of essayists like Paul Graham and Philip Greenspun; in particular, Greenspun's Tenth Rule of Programming which states: "Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp." So, should this book be read as an exhortation to return to Lisp as the preferred programming language?

Paradoxically, I think not. One third of the way through the book, Norvig shows us how to implement Prolog in Lisp. From then on out, most of the AI techniques he presents either directly use Prolog instead of Lisp (such as his excellent discussion of natural language processing using Prolog) or use Prolog as a base to build on (such as his discussions on knowledge representation).

From this we can abstract what I'd like to call Norvig's Corollary to Greenspun's Tenth Law of Programming: "Any sufficiently complicated LISP program is going to contain a slow implementation of half of Prolog". I'm leaving out the "ad hoc", "bug-ridden" part of Greenspuns's law, because Norvig's programs are neither. But it is quite remarkable the degree to which, once having absorbed Prolog, Norvig uses Prolog as the basis for further development, rather than Lisp.

Is this a book about Prolog then? Again, no. What is the take-away message? It is this: as our world becomes more and more complex, and as the problems which programmers are facing become more and more complex, we have to program at a higher and higher level.

Norvig does not stop at just embedding Prolog in Lisp. He also shows us how to embed scheme as well. Excellent discussion on the mysterious call/cc function and on continuations.

In a capsule review, it is impossible to really give an overview of a 1,000 page book like this one. But the scope and heft of the volume really needs to be commented on: the programs presented in this book are like basis vectors, the totality of which nearly span the space of programming itself. In no way should this be considered "just an AI book" or "just a LISP book". This book transcends language, time, and subject matter. It is a programmer's book for the ages.

"Paradigms of Artificial Intelligence Programming" is one of the best books of computer science that I have ever read. I put it up there in the pantheon with "Structure and Interpretation of Computer Programs". I have found more useful and mind expanding material in these case studies than I have in many other books on computer science. I highly recommend this book to anyone, even if they have never used Lisp.

When I bought this book I never realized how handy it would be. Reading it from cover to cover is a pleasure but it's also very easy to use as a reference -- I've never spent more than a minute trying to find whatever I need. This book has saved me uncountable hours both while debugging software and while porting to various platforms.

After 10 years of developing real-time software for DOS and embedded systems, I needed to develop software for the real-time O/S, QNX, a POSIX compliant O/S. Unlike DOS, QNX is a real operating system which demands a different programming paradigm. Without Lewine's book, I'm not certain I could have made the shift.

This book may be too complicated for somebody unfamiliar with C programming. But, if you know the language, it provides all the basics to successfully create software on a POSIX system. The first half of the book elaborates on how to do things in POSIX. Lewine does not assume that the reader knows anything about UNIX. Plenty of example code clarifies the the theory. All the examples are heavily annotated. One cannot *not* learn the POSIX programming paradigm from this book.

For real-time programming, information about POSIX.4 was needed, and I gleaned this from Gallmeister's PROGRAMMING FOR THE REAL WORLD: POSIX.4, also an O'Reilly book. Once through these books, code began to flow from my keyboard. The QNX library manuals made far more sense.

As an "expert" (I've been doing this for about 5 years), I still refer to the back of Lewine's book. The last half is a reference to the POSIX library functions. Although I haven't done much programming under LINUX, I presume this would be a useful reference for that O/S. The latter half of the book documents the function calls at least as well as any manual for a C programming library that I've ever seen. I've gotten to the point where this book mostly sits on my shelf--but it's comforting to know that when I can't remember the arguments for sigprocmask(), I can take it down and find the answer quickly.

For many programmers, interoperability is the name of the game.
Write once, compile everywhere. Yes, compile, because a compiled
program runs 80 times as fast as an interpreted program. Now comes
the gotcha: different compilers come with different libraries.
C source written for HP-UX might look different from C source written
for Solaris, which might look different from C source written for AIX
or Linux. What features of the language should we use? What library
calls should we use? Answer: Use ANSI C with IEEE 1003.1 POSIX
standard library calls. This gives you the most bang for your buck,
because nearly all C compilers support these standards. Write your
code on one platform, compile it on the other platforms. If you
conform to the POSIX standard, you will minimize your porting
headaches. Follow this book and you'll conform to the standard.

When I bought this book I never realized how handy it would be. Reading it from cover to cover is a pleasure but it's also very easy to use as a reference -- I've never spent more than a minute trying to find whatever I need. This book has saved me uncountable hours both while debugging software and while porting to various platforms.

After 10 years of developing real-time software for DOS and embedded systems, I needed to develop software for the real-time O/S, QNX, a POSIX compliant O/S. Unlike DOS, QNX is a real operating system which demands a different programming paradigm. Without Lewine's book, I'm not certain I could have made the shift.

This book may be too complicated for somebody unfamiliar with C programming. But, if you know the language, it provides all the basics to successfully create software on a POSIX system. The first half of the book elaborates on how to do things in POSIX. Lewine does not assume that the reader knows anything about UNIX. Plenty of example code clarifies the the theory. All the examples are heavily annotated. One cannot *not* learn the POSIX programming paradigm from this book.

For real-time programming, information about POSIX.4 was needed, and I gleaned this from Gallmeister's PROGRAMMING FOR THE REAL WORLD POSIX.4, also an O'Reilly book. Once through these books, code began to flow from my keyboard. The QNX library manuals made far more sense.

As an "expert" (I've been doing this for about 5 years), I still refer to the back of Lewine's book. The last half is a reference to the POSIX library functions. Although I haven't done much programming under LINUX, I presume this would be a useful reference for that O/S. The latter half of the book documents the function calls at least as well as any manual for a C programming library that I've ever seen. I've gotten to the point where this book mostly sits on my shelf--but it's comforting to know that when I can't remember the arguments for sigprocmask(), I can take it down and find the answer quickly.

POSIX is only one operating system standard in IEEE/IEC.
But now ISO have another oerating sysm standard, OSEK OS.
OSEK OS is more slight, simple and real time oriented.
Why Posix is not so portable and not so Open.
NIST made a POSIX Test Suite based on old POSIX standard.
But where is POSIX Test Suite based on new POSIX standard.
This book was based on old POSIX.
So, you can understand this with NIST posix test suite.

Gallmeister splits this book into two main sections, an introduction to the material and a reference section, which provides detailed documentation for the various function calls and header files. Somebody new to the material will find the first section indispensable, while the pro will flip to the reference section to answer questions.

Chapter one provides an overview of the problems this book addresses. The second chapter examines POSIX, POSIX options, and POSIX namespaces. Chapters 3 - 6 define real-time problems and POSIX.4 solutions. Chapter 7 considers the issues of real-time performance.

Gallmeister provides many example code fragments to illustrate his points. He would have done better to have annotated his examples, instead of writing a number of descriptive paragraphs after each fragment. A particularly useful feature is his discussion of "current UNIX practice."

Overall, this book provides a reasonable introduction to the concepts of real-time programming, and a number of "recipe" examples for the POSIX environment. Recommended if you'd like to develop real-time skills or need a reference work on the subject. I found it useful learning to develop QNX software, even though QNX implements a number of "optional" features differently.

This is the best book on the subject. One can tell that the author is an expert and knows very well what he is talking about.
Unlike one reviwer mentioned below - I dont think he has read any part of the book - this is not an "reasonable introduction" at all. This is an in depth handling of the topic.

If you know C and know UNIX, this book is for you. Simply put, he knows what he's writing about and he presents the material in a logical, methodical manner.
This book was written just before the POSIX4a standard was completed, so no PThreads are covered.
As long as you're not expecting PThreads coverage, you won't be disappointed. Most of the topics you need to know about mutli-threaded programming (besides PThreads) are here.

The book consists of 2 parts. The 1st part is a detailed guide to the real-time POSIX programming. The 2nd part presents a reference to all POSIX real-time functions. The book also has an appendix with various sample and exercise code.

All explanations in the first part are very clear and complete. Writing style resembles the best programming books (like those from K&R or R.Stevens). At the same time everything is given in a distilled manner without unnecessary water, so that you might handle the stuff surprisingly fast.

The second part is less valuable since all this material can be found in UNIX man. But if to see it as just a free bonus for the 1st part it is not bad at all. In any case having printed manuals is quite useful.

Sample code in the appendix is also interesting to look at.

Actually I didn't notice any considerable drawbacks in the book and recommend it to everyone interested in the subject.

The prerequisites are minimal. You should know C and be familiar with the basic UNIX/POSIX API (like working with files, etc.). The next reading is obvious - some book on POSIX threads (I'd recommend one by Mr. Butenhof).

I've managed to get about halfway through this book so far. It's NOT an easy read. Coverage and detail are excellent, however, and if you're interested in plumbing the depths of how MySql works, I would recommend this book as a solid reference for improving your overall knowledge.

No, I am not associated with the authors in any way. I was looking for a book for MySQL that was beyond "this is a database, here is how you select".

I wanted something more challenging that covered topics like clustering, backups, etc.

This book dives deep into MySQL database use and design, including detailed information on indexes, optimizations, etc.

Very good read. I totally recommend this book.

cbmeeks

This book is a great expert overview of all that is current in MySQL 5. This covers both the SQL interaction with the database and the management. There are aspects that users often don't use in any SQL platform, and it is a shame. The effort expended to learn stored procedures and custom functions is greatly rewarded in code creation and support. This is another book I rate as ROI super positive.

Highly indicated reading for any database designer involved in developing a major application or in optimizing database operations using MySQL, this intermediate/advanced level book assumes the reader has a general knowledge of database operations and some familiarity with MySQL database system. However, should such awareness be lacking, the book is sprinkled generously with additional source of information to remedy the deficiency. From conceptualizing and elaborating a database to fit business needs to implementing it in an efficient manner, the author takes the reader deep into the inner workings of MySQL in order to optimize database operations. Tools for benchmarking and profiling, which are essentials to indicate where coding performance could be improved, are explored in an insightful manner.
As much as it is possible to make a book on data processing, much less database innards interesting and captivating reading, the author has done an excellent job in this regard.
Overall, a must reading for any MySQL developer looking into enhancing his/her skills.

For people like me who have a good understanding of MYSQL, the next logical step would be this book. I already know about stored procedures, transactions and the basics of triggers, but I want to learn more about these topics in more "real-world" scenarios in how to develop larger, enterprise-wide applications. Also I want to know more about other advanced topics that I may not even know to think about. If this sounds like you as well, then read on...

The author starts in with reviewing how business requirements and the software development cycle can be part of database development. This a great chapter for people like me who would like to learn how different approaches are taken from different IT perspectives in a team environment (business analysts, application developers, and project managers) This chapter gives you a good understanding of how the other side thinks.

The next chapter focuses on the importance of proper indexing and strategies as pertaining to data storage. Because once your databases reach to the multiple gigabits of storage space, you need to very focused on how long each request takes. A few seconds here and there begin to add up and can cause serious issues if not taken into consideration early in your database design. Like me who only deals with small to an occasional medium-size database I never really had to think about this before.

The next chapter focuses on transaction processing in MYSQL which is one of the more difficult concepts for many and I am in the process now of reading it. I really like the author's explanations and examples. Each point is explained thoroughly and in an easy to read manner.

The rest of the book goes into more advanced topics (system architecture, benchmarking and profiling, security, replication and clustering) as well as giving more detail and explanation to topics that may only be briefly covered in other MYSQL books (stored procedures, functions, and views).

If you already know the basics of MYSQL and want to really advance your knowledge with "real-world" scenarios, this is the book for you.

Judging by the number of reviews, MacDonald's fan base is similar to that of Alison Balter-Mastering Access 97 Development (one of SAMS best). The learning and example experience is fairly similar. I got Pro WPF before the VB version came out. Migrating from VB to WPF is difficult enough without dealing with C#. The downloaded code of the VB version is only for examples but they are generally relevant to me. I still break out Visual Basic 2005 (.NET or Bust) for a succinct reorientation.

This review is a comparison between
Windows Presentation Foundation Unleashed (WPF) (Unleashed) by Adam Nathan

and

Pro WPF: Windows Presentation Foundation in .NET 3.0 by Matthew MacDonald

I have been using both of these books for learning WPF. What I like about "WPF Unleashed" is the quality of the pages with the color printing. I believe this higher quality is a great step in the right direction and I know a lot of developers appreciate good quality printing such as this. But as good as the printing is I still find myself spending more time in the "Pro WPF" book.

I think it has to do with the flow of the book and how the information is presented to the reader. I'll do my best to explain my experience. In the "Unleashed" book I found myself reading a bit of knowledge, looking at the example, try to work with it in Visual Studio and struggling. Then going back over the knowledge, going to the internet, find out some more, work with it in Visual Studio, back to the book and in some cases giving up because I couldn't achieve some result.

In the "Pro WPF" book though I didn't have this happen nearly as much. In the Pro book it had a really nice flow to it where he would present some basic information, give and example, present some information, give an example. So here I found myself reading some knowledge, do it in Visual Studio like his example, read some knowledge, do it in Visual Studio. I didn't have to reread nearly as much and the knowledge seemed to build upon itself nicely; taking you from simple to more complex. He was really good at NOT introducing newer topics (WPF class/methods) that he hadn't already covered.

The books work well together though and that's how I used them. I use the "Pro WPF" as my main and the "Unleashed" book for more examples.

The "Pro WPF" book has also been updated since publishing and split into two books for C# and VB.NET in .NET 3.5:
Pro WPF in C# 2008: Windows Presentation Foundation with .NET 3.5, Second Edition (Books for Professionals by Professionals)
Pro WPF with VB 2008: Windows Presentation Foundation with .NET 3.5 (Pro)
I haven't read these books yet so I cannot comment on them. I just wanted to include them as a note to the reader.

I really didn't need another book on WPF, at least that is what my girlfriend would say. I already own "Applications = Code + Markup" by Charles Petzold, "Essential Windows Presentation Foundation" by Chris Anderson, "Foundations of WPF: An Introduction to Windows Presentation Foundation" by Laurence Moroney, "Windows Presentation Foundation Unleashed" by Adam Nathan, and "Professional WPF Programming: .NET Development with the Windows Presentation Foundation" by an assortment of Wrox authors.

But I saw Pro WPF: Windows Presentation Foundation in .NET 3.0 on Amazon and decided to investigate the possibility that I need to have it. After reviewing the TOC I still wasn't sure. But after downloading the code from Apress I was sold. I have been a fan of Matthew MacDonald for some time. He has definitely worked his magic on this title.

Some of the highlights I like:
His in-depth coverage of printing.
His Custom Elements chapter.
His approach with 3-D drawings makes extensive use of the 3DTools from CodePlex.
The chapter on using ClickOnce with WPF.
Everything is gone into in depth. This is not a brush over the topic book.
The usability of the code makes the book all that much more valuable.

He also has a great site named ProseTech that has a companion site for the book. It contains all the links found in the book

For extreme coverage of Expression Blend you will have to by a book specifically on Blend. Too bad no good ones exist yet. One I have seen that is out has bad reviews. None of the books I have listed above cover Blend in-depth at all. The Wrox book has 2 high level chapters on it, but I have been playing with Blend 2 a lot and find myself in the XAML most of the time because I don't know how to get to what I want to do in Blend. On that note, this book is excellent for showing you how to work XAML to the maximum.

This book also does not cover Silverlight. It is a book about Windows Applications, not Browser Applications.

I highly recommend this book as addition to any developer's or designer's (those who need to know XAML) library. It was definitely worth buying.

Books stated purpose: This book is an in-depth exploration of WPF for professional developers who know the .NET platform, the C# language, and the Visual Studio development environment.

This book introduces the developer to the WPF (Windows Presentation Foundation), which is a new graphical display system for Windows. This book is well written from beginning to end, and takes the developer through the process of learning how to utilize the capabilities of WPF. The author provides references to outside sources throughout the book. These either provide a more in depth look at the current topic, or point to a tool that would be useful. The author introduces WPF in a manner that lets developers of any level understand what WPF is and the benefits of using WPF. Then chapter by chapter he provides instructions and examples that take the developer through the learning process about WPF.

System Requirements;
* To run WPF applications, you must be running Windows Vista or Windows XP with Service Pack 2.
* To create WPF application, you must have either Visual Studio 2005 with .NET 3.0 and the WPF extension, or Visual Studio 2008.

The early part of the book is about the basics in and about WPF. The author gives basic, but understandable examples that lead the developer in a growing understanding of WPF. Once the developer has the basics of WPF down, the author begins to build on this base.

One of the basics covered is the creation of the Application object. This is the foundation for all the code throughout the book. Another basic operation covered is the layout of the forms. WPF provides the ability for Windows forms to dynamically grow and resize based on data and language, similar to Web Forms. It takes more work to set up a form, but it will give the user a much better experience in using it.

Now that the developer has the basics, the author moves along the path for using them. The developer is introduced to the WPF controls and how to develop with them. There are a number of features added to familiar controls. Some examples include: Tooltips can now contain both images and text. Multi-line text boxes can grow dynamically and text does not have to always break where it fits the textbox edge. You can add a dynamic spell check to textboxes.

There is a chapter on building control templates or modifying existing controls. This feature appears to be more powerful, and quicker than the old method of building a new specialized control from scratch.

The following topics are part of what is covered as the book continues. Data Binding to a database, Printing, Animation, Sound and Video and 3-D drawing.

The author wraps the book up with a short tutorial on using the ClickOnce Deployment. If the developer has already learned to use the ClickOnce Deployment, this chapter can be skipped. However, it is a useful conclusion to the book if the developer has not yet used the ClickOnce Deployement.

The book is pretty detailed. This review only touches on a few of the highlights from the book that specifically caught the reviewer's eye. It is worth adding to any developers library if they are looking to do new development for Windows Vista or Windows XP SP2.

I already have several WPF books now, each of them has something to offer and it's a rare day when you can find all the information you need on a complex, wide ranging topic like WPF in one book.

Without detracting from the other books that I admire, I think if one book does come closest to being a one-stop source then possibly it is this one. Coverage of topics is comprehensive, detailed and accurate. At just under 1000 pages it's definitely a heavyweight, although you're unlikely to want to be parted from it long enough to use it as a doorstop.

The author's writing style is clear and friendly without being patronising. If I have a gripe about the book, it's the same complaint I've been making since the middle of 2007 - this is yet another WPF book that only has code behind samples in C#. However I understand that there will be a VB2008 version out early in 2008.

Of the books I have on WPF, I turn to this one early in most researches. I consider this book to be a good investment. I have several of Matthew MacDonald's earlier books, which I have always found relevant, well-written and useful; this book is in the same mould.

Mr. Bassiri definitely has an excellent grasp of the Netscape Server architecture. After reading this book, I have gained a better understanding of the Netscape server inner workings. I found the chapters on WAI very helpful! I would definitely recommend this to anyone developing applications for the Netscape platform.

My only complaint is that some of the sections are too wordy and redundant.

I thought I knew a lot before I read this book. I was just fooling my self..... Must own book if you work with NES.

Just got my copy of this book and it is great. Wish Netscape provided such accurate and detailed information in their books. Mr. Bassiri seems to know what he is writing about. He seems to write from experience instead of reading Netscape manuals and rehashing the old story. Appendix A and B are really helpful. They included a complete list of server configuration settings. The NSAPI tutorial is the best around and the WAI section provides a true programmer's review of this API. This book is packed full of information. If you want to know how the Netscape server works and program applications for it, you should definitely buy this book.

If you administer or develop for Netscape servers, you will benefit from this book. Administrators: the knowledge you gain from this book will allow you to modify the config files to do correctly what the Server Manager sometimes doesn't do properly, and configure features that simply cannot be administered from the Server Manager. Developers and Architects: Having read this book, you will know what options you have, and be more easily able to decide which architecture is best for your application -- and you'll be able to code it. In addition, your understanding of the key concepts will allow you to grasp quickly how external but related technologies (like Forte's Web Enterprise) work. Well-written, detailed and comprehensive; highly recommended.

Easy to read, I delved in and finished it in 2 workdays without falling asleep. The info is clear and the examples great. Two suggestions: more examples, and greater focus on what the non-threadsafe functions are. He lists NSAPI funcs and says to use 'em (util_sprintf() for instance) but doesn't mention if strlen or other functions are threadsafe. Also, the time function - I can't get a compile using time funcs that don't have a local time_t or timeb structure (instead of pointers to system structures). That should be noted. Otherwise, totally required book and excellent for beginners to get into it.

This book is very good for all types of projects. It covers setting up a project, organizing the work, managing a project, handling several projects at once, dealing with project issues and crises, using modern technology such as groupware and the Internet. The approach of establishing an issues data base and relating issues to specific tasks in a project is unique. It is very useful.

This is one of the best project management books for introducing employees to modern project management in an interesting way. Most project management books are ver dry and lack realistic examples. Thus, it is difficult to motivate people to read and use such materials. This is a very practical, down to earth book that has many guidelines that you can use immediately as you read the book. Some of the strengths of the book are: 1) best description of matrix management; 2) use of collaborative tools in managing projects; 3) how to deal with multiple projects; 4) how to share resources across several projects; 5) how to deal with risk in projects. The authors have developed a very creative and useful approach in dealing with project risk that associates project risk with unresolved issues. I highly recommend this book.

Project management for the 21st century is one of the most usable, easy to read, and complete project management books. There are good examples. Techniques are modern--better than that available in other books. This books stresses working together, sharing information, and dealing with resources that are spread among various projects. Very good reference.

This book provides the basics of project management in an easy to use casual style. It proceeds step by step through building a plan and then managing a project. The chapter on project costing is good, but could use some more detail. The modern and historical examples are usefully examined. These could be expanded more later.

This book not only gives you all of the basics, but also highlights how to use the Internet for project management. Very useful material.