Programming Books

I bought this book for general project evaluation purposes, for a project that I was called in on that was in trouble.

Well worth the read - a lot of it is just good common sense, straightforward project management process, but it provided a great roadmap for validation of my plan to put the project back on track.

Definitely would recommend it - it's an easy read; I finished it in under 5 hours on the flight out, complete with note-taking. Kudos to E.M. Brennatan for writing this in a straightforward fashion.

It is a law of nature, grouped under the general name of entropy, that it is easy to mess things up and very hard to straighten them out. In fact, it is the natural state of nature to tend towards increasing disorder. This law also applies to software projects, since they are naturally very complicated entities; they easily reach a point where difficulties compound to the point of dysfunction. The author calls this state a catastrophe, although in my opinion that is an overstatement.
A catastrophe is a major disaster, far beyond what most software development projects actually are. Granted, there are problems, but most of the situations described in this book are ones that can be recovered from with more effective planning and focused execution. The author puts forward a ten-step plan for disentanglement:

1) Stop the project - not permanently, just long enough to examine the project in detail before things get worse.
2) Assign an evaluator - a disinterested party is assigned to perform an honest and unbiased appraisal of the project and what is going wrong.
3) Evaluate the project - the evaluator takes the lead in doing a complete dissection of all aspects of the project, what is being done right and what is going wrong.
4) Evaluate the team - examine the people working on the project and determine if all are suited to their jobs and if all are performing at the appropriate level.
5) Define minimum goals - determine what is considered to be the minimum level of achievement that will be considered a success.
6) Determine if the minimum goals can be achieved - if the minimal level of success is not possible, then the decision must be made to terminate the project.
7) Rebuild the team - this step has two basic components. Personnel changes if necessary and reinvigorating those who are going to remain part of the team. One of the greatest tasks is to overcome the defeatist mindset.
8) Risk analysis - attempt to identify all possible risks and assign a reasonable probability of occurrence to all of them.
9) Revise the plan - as circumstances change, modify the plan to reflect the different conditions.
10) Create an early warning system that will flag the appearance of problems when they are not yet serious.

These ten steps are each the topic of a chapter. Exercises for further practice are included at the end of each chapter, although no solutions are given.
I enjoyed the book; it contains a lot of sound advice on how to right a rudderless software project. Most of the advice will work only on a project that is not yet seriously out of control. Quite frankly I don't believe that a ten-step plan like this is powerful enough to get the most dysfunctional death marches back to a point of potential profit. Therefore, while I believe that the advice is sound, it is limited in scale, where the measurement is of the level of dysfunction in the project. On that basis, I can recommend the book.

Catastrophe Disentanglement : Getting Software Projects Back on Track teaches the kind of skills you hope you never have to use. It's something like taking a CPR class for project management. You hope you never have to administer CPR in real life, but when you do get put in that position, you're really glad you have that training to fall back on. That clear, logical list of steps can mean the difference between life and death. In the world of project management, the skills taught in this book can save projects and careers.

This book differs from traditional project management books in that it focuses on corrective rather than preventive measures. The author teaches two critical things. First, he presents a set of criteria used to recognize a project that is in need of rescue. This is an important step! Once a project is identified as seriously out of control, you can apply the steps presented in this book to bring it back on track and guide it to a successful completion. This book will give you the reasoning and courage necessary to make hard decisions.

Table of Contents
Chapter 1 An Introduction to Catastrophe Disentanglement
Chapter 2 When Is a Project a Catastrophe?
Chapter 3 Step 1--Stop
Chapter 4 Step 2--Assign an Evaluator
Chapter 5 Step 3--Evaluate the Project
Chapter 6 Step 4--Evaluate the Team
Chapter 7 Step 5--Define Minimum Goals
Chapter 8 Step 6--Can Minimum Goals Be Achieved?
Chapter 9 Step 7--Rebuild the Team
Chapter 10 Step 8--Risk Analysis
Chapter 11 Step 9--Revise the Plan
Chapter 12 Step 10--Create an Early Warning System
Chapter 13 Epilogue: Putting the Final Pieces in Place

I would recommend this book to anyone involved in software projects.

Good book, good subject, well covered. The book builds an organized process around the rescue of a failed (or failing) software project. The steps are easy to read and understand, and seem well thought out. Some good methods for identifying projects headed for serious trouble. Also, some useful guidance on how to handle political (not just technical) problems. Obviously, the result of significant experience. Well recommended.

There are plenty of books that try to help you keep your project on track. But what happens when you are sitting on a catastrophe and you don't know how to salvage it? E. M. Bennatan fills a necessary niche with the book Catastrophe Disentanglement : Getting Software Projects Back on Track.

Contents: An Introduction To Catastrophe Disentanglement; When Is A Project A Catastrophe?; Step 1 - Stop; Step 2 - Assign An Evaluator; Step 3 - Evaluate The Project; Step 4 - Evaluate The Team; Step 5 - Define Minimum Goals; Step 6 - Can Minimum Goals Be Achieved?; Step 7 - Rebuild The Team; Step 8 - Risk Analysis; Step 9 - Revise The Plan; Step 10 - Create An Early Warning System; Epilogue - Putting The Final Pieces In Place; References; Glossary; About The Author; Index

If you're in IT for any length of time, you'll be part of a project that is massively over budget or late. Rather than just continue the death by 1000 cuts or a quick mercy killing, Bennatan presents a ten step process that allows an organization to take a (hopefully) objective look at the project and decide what can possibly be saved from it. I was impressed that it wasn't a long drawn-out procedure either. The plan calls for an evaluator (or a small team for huge projects) to come in and quickly assess the environment... what's been done, the climate of the team, and what could be redefined as a "minimum system". At the end of this process, the organization should be able to either kill it off with the knowledge that it can't be saved, or continue on with a redefined set of deliverables that are achievable. It won't be everything that was originally wanted, but it will be more than you'd get by letting it die. I was also impressed with the "What Can Go Wrong (And What To Do About It)" section in each step. He doesn't present this as some cut and dried panacea that will flow smoothly every time. It may not be an easy task, but the book will give you the help you need to make it all work.

Definitely a book that is worthy to be on every IT project manager's bookshelf, as you *will* need it some day...

I really enjoyed this book, and I think it's definitely worth considering if you're interested in how stories can be told in video games. I've bought plenty of books about video game design and storytelling. (I'm a programmer who's been making video games professionally for about 10 years -- I wish more people would include their personalbackground in their book reviews...) Some books on game design are written by people who obviously have more "static media" backgrounds like books or movies, and don't understand the fundamental problem of making a story in a situation where the audience has freedom to do what they want. Another problem that a lot of people don't understand is that people playing a video game don't necessarily WANT a story, in the sense that they are playing a video game because of the interactivity, and not to watch a 10 minute cutscene to learn some back story. If they wanted to watch a movie they'd pop in a DVD.

I think the author really understands these difficulties. You want to make an emmersive worl, but you need to do it very quickly. So he talks about dialog, and how to convey as much information as possible in as few words as possible. He talks about how to get the player to sympathize with a chaacter, from the situation that characetr is in, to the design of the character art, to the words that the character says. All of the information is very practical, not like some books that leave you with a bunch of high-level nonsense that doesn't work in a real game. I really appreciated that he wasn't one of these "video games are mindless because they don't tell a story" type of guys. Or acting as if video games need to learn how to tell a story in order to "grow up" like movies or TV have. In a straight up action game or fighter, you don't need as much of a story as you do in a more adventure game. Playing a video game is a just a different experience, and the story has a different role, it's NOT the holy grail like some people think. Rather than trying to tell you how to convert video games into novels, he describe ways that you can inject story without taking away from the inetraction. I think he makes a good case that in almost any game, you can introduce just a bit of characetr depth and relationships, without stopping for a ten minute cutscene, and it adds value to the game.

This author's background was originally in TV, but he also has considerable experience in video games. I felt like he has a good background to be writing the book, and was speaking from experience.

The only negative comment about the book is that I found several of the chapters to be very similar. Like you'd be reading a chapter, and you'd think, "Hey, didn't I just read this exact same thing a few chapters ago?" Actually, you didn't, this chapter is covering a very slightly different topic. In other words, I think he could have consolidated a few chapters, which would have saved me some time. I suppose this makes it easier to jump around, since you don't rely on information from previous chapters. But I found it a little repetitive.

All in all, a really good book for anybody interested in video game design or storytelling in general.

I've known Lee Sheldon for several years. He is one of the most pleasant and knowledgeable people I've met in the game industry, so I was very much looking forward to this book. Suffice it to say that I wasn't disappointed.

Writing for games has a lot in common with writing for other media (e.g., character and theme) and a lot that is unique to itself. Lee does an excellent job of covering both aspects - so much so that I would recommend this book to writers with absolutely no interest in interactive media. (I've read my share of writing books over the years, and this one stands at the top of the heap.)

Of particular interest to me were chapters 3-6 on character and chapter 14 on modular storytelling, the most elegant way I've seen of organizing a linear experience into a non-linear structure. The book also does an excellent job of discussing storytelling in massively multiplayer games and provides extensive background material, much of which is intended to set up and justify Lee's modular storytelling model - rather more background than necessary, actually, since you should be sold on the need for something like modular storytelling long before he gets around to explaining it.

The book's does have a few faults. For example, a couple of the later chapters feel out of place, and the text is dusted with a handful of puzzling and sometimes repeated typos (Eowen? Kalishnakov?) But these are of little consequence and should not detract from your enjoyment.

Highly recommended.

Cons: The book seemed slightly long for what it was, kept reusing the same semi-obscure examples from the writer's experience, and didn't always go in the directions I wanted it to go (for example more detail on world building, settings, or individual story scenes would have been appreciated).

Pros: It didn't matter that it didn't go where I wanted it because it was still very entertaining and unexpectedly beneficial to follow the writer on his path. The book is solid from start to finish and doesn't have a false air of superiority about it; everything is very practical and friendly. Definitely a good read that rewards the effort.

This book is excellent. Sheldon is witty and insightful and his book is a joy to read. I can't really think of anything negative to say, although I should perhaps mention that this book is pretty focused on RPGs and adventure games, since these are the genres which have traditionally relied most on story. Anyone interested in developing their understanding of storytelling in games should definitely pick this book up.

I am working on forming a game development studio, and our team is in the middle of producing our flagship title, an RPG entitled "Revolution's Dawn." I am the main writer of the script, and I just recently finished reading this book. Where I thought my duties as a writer were finished, I now see new openings to provide dialogue and sidequests to fill in the backstory, plot gaps, and other means of enrichment that I didn't see before. Because of having read this book, my team and I can now take this game and bring it into the realm of what we intended it to be-a vehicle for telling a story.

While the title of the book is "Character Development and Storytelling for Games," the book really focuses more heavily on the latter. I was expecting the former, but by no means am I complaining! I have been able to break through blocks in my own role as a writer for this project.

If you are looking for the "right" way to write your story, you won't find it here. What this book does instead is to open doors, and then let you decide whether to walk through them or not. And even then, you still have to choose for yourself what to do once you've walked through them. If you are looking for new openings in crafting your game _and_ writing your story(and synthesizing them both together), this is the book for you.

This is a GREAT book for people who know COBOL and need to know the differences among the COBOL versions. This book is LOADED with programming tips.

Covers how to improve coding techniques along with the differences in COBOL versions. Great for seasoned programmers too.

This book is for programmers who learned OS/VS COBOL or COBOL II and are now upgrading to COBOL/390. This is IBM's latest version of COBOL, with an emphasis on open systems and object orientation. There are a lot of new features in COBOL/390 and David Shelby Kirk describes them clearly and thoroughly.

The book was written for experienced professionals, not for novices or entry level programmers. The book does not explain basic syntax of statements or other organizational aspects of a COBOL program. I wrote the book for the professional programmer who already knows COBOL and wants to move that skill to a higher level. This includes incorporating the COBOL language with the enterprise server environment for effectiveness and efficiency, and creating extended software architectures.

To my knowledge, there are no other books that focus on the advanced techniques of COBOL in the IBM enterprise environment. This book introduces new techniques for program structure and memory management and explains the major components of optimizing programs within the IBM enterprise environment. If you are developing enterprise applications, this is the book for you. IBM has made major expansions in COBOL in recent years and this book will help you unlock those new features.

For the basics, this is an excellent writeup and you SHOULD have it. What is NOT covered is LE and object programming. Intrinsic functions are slighted but you can figure them out.

The author is very upfront about not covering the object extensions - I can almost forgive him. But these are the future - our top management is very object/web oriented.

I think there is a slide on the LE coverage. After we went through the Y2K conversion, our programs are loaded with language environment calls. Section 3.13 is a listing only of what should have been a great amount of detail on using LE calls and intrinsic functions.

In defense of the author I did find an example of the function used with a date (on page 384) MOVE FUNCTION CURRENT-DATE (1:8) to WS-GREGORIAN which is close to our shop standard MOVE FUNCTION CURRENT-DATE (1:14) TO WS-DATE-TIME.

An authority in the field of artificial intelligence and computer science in general, Joseph Weizenbaum provides insight in proceedings in that area but mainly warns about what these developments may lead to. It is very entertaining to read this book some 20 years after original publication and see how many of what we believe are recent developments were actually implemented back then already (on one or two priceless "super" computers).
Very dogmatic and patronizing at times, it still is a good read if only for the thought provoking ideas like: if electronic computers would have been used in the manhattan project, today we would assume that development of the atomic bomb would have been impossible without it.

The computer and natural language is a sub-domain of computer science in which one of the major aims is to imitation of man, focusing on two topics: psychology and linguistics. If we wish the machine to do something, we must tell it what to do and it must be able to understand us. The easiest way to tell a computer what to do is to give it a program to run. "Humans, if they are machines at all, are vastly general-purpose machines and what, is most important, they understand communications couched in natural language." Work must be done for a machine to understand natural language. "Man's capacity to manipulate symbols, his very ability to think, is inextricably interwoven with his linguistic abilities." A machine must be able to extract semantic content from the messages impinged upon it, adopt a syntactic structure of a visual scene and adopt a certain conceptual framework. The question of what comprises a visual symbol is in question. The developer defines the elements of the machines primitive vocabulary. Robert Lindsay said, "high quality translations could be produced by machines supplied with sufficiently detailed syntactic rules, a large dictionary, and sufficient speed to examine the context of ambiguous words for a few word in each direction."

Eliza was a program consisting mainly of general methods for analyzing sentences and sentence fragments, locating so-called keywords in texts, assembling sentences from fragments and so on. Eliza created the remarkable illusion of having understood in the minds of the many people who conversed with it.

In ordinary two person communication, each has a working hypothesis, a conceptual framework, concerning who the person is and what the conversation is about. The hypothesis serves an indicator of what the other person is going to say and what he is going to mean by what he is about to say. Often, the erroneous prediction is falsified before the sentence is completed and the listener makes corrections on the fly and virtually unconsciously. Each brings into mind an image of the other person, the image consists in part of the other's identity, attributes based on evidence derived from independent life experiences of the participant. "Our recognition of another person is thus an act of induction on evidence presented to us partly by him and partly by our reconstruction of the rest of the world; it is a kind of generalization". Eliza starts with the hypothesis that the system does understand.

Rogar C. Shank, based his theory on the central idea that every natural-language utterances is a manifestation, an encoding, of an underlying conceptual structure. Understanding an utterance means encoding it. The theory proposes a formal structure for the conceptual bases for making predictions. The theory creates formal rules for converting utterances into a conceptual base. One difficulty is that every individual's belief is constantly changing mean that an individuals entire base of conceptions is changing. "When a person enters a conversation he bring his belief structure with him as a kind of agenda."

Terry Winograd, of M.I.T, was working with a group were building a computer-controlled "hand-eye" machine; the computer could see its environment and manipulate objects in its environment by means of a computer-controlled mechanical arm. Winograd design and coded the software to enable humans by natural language, too instruct the computer, how to manipulate and explain events with respect to the toy world of blocks, in a natural language. "The robot can manipulate toy blocks on a table containing simple objects like a box." The robot could be ask to manipulate the objects, doing such things as building stacks and putting things in a box. It could be questions about the configuration of blocks on the table, about events that were going during the discussion, and it could be told simple facts about the objects which could be stored and used for reasoning later. The conversation goes on within a dynamic framework - "one in which the computer is an active participant, doing things to change his toy world, and discussing them."

This book is a basic philosophical treatment of computing. I think that it should be included as a basic part of any Computer Science / Computer Engineer curriculum in respectable universities, along with Roger Penrose book, The Emperor's new mind, it creats a better understanding of what is human and what is mechanic for all those who need to know it.

Should Computer Science / Engineering freshmen/women in universities know? My answer is YES, in their first year !

I read parts of this book, thinking highly of it. I thought one particular passage from it, as quoted in Gates by Stepehen Manes and Paul Andrews, particulary stood amid the limelight: [t]he computer programmer . . . is a creator of universes for which alone is the lawgiver. . . .No playwright, no stage director, no emperor, however powerful, has ever exercised such absolute authority to arrange a stage of field a battle and to command such unswervingly dutiful actors or troops.

This is perhaps the best book ever written on issues of computer technology and modern life, in the sense that it says a lot of really important things and is also very readable by both lay persons and technical persons. People like Jacques Ellul, Arnold Gehlen et al. have written very important texts in this area, but are much less "accessible". If the truth only counts when it is absorbed by persons, Weizenbaum's book stands out as being engrossing and a pleasure to read, as well as saying what needs to be said. It is very sad that the second edition which was supposed to be out a year or so ago has not appeared. But in no way has 20 years "dated" the present text. _Computer Power and Human Understanding_ explains why we have such problems as Y2K, etc.

The book contains a common-sense approach to software process improvement strategies for most organizations to follow. Wiegers takes the mystique out of the Software Engineering Institute's CMM and offers the CMM as one way of many to accomplish process improvement. He balances technology and process-focus against real-world people issues. Must reading for anyone involved in a Software Engineering Process Group or for senior managers trying to figure out what all this stuff is about. Text is well illustrated by case studies and examples from the author's experience at Kodak

This is a great overview of all the elements of a successful software project - from project planning to system design on up to testing and project postmortem. Many of the topics are covered too lightly to allow a practitioner to use all of Wieger's advice right out of the gate. But that's fine - the book is meant to be a handbook of great ideas from which practitioners should choose, study and implement. Pay particular attention to the discussion on determing project drivers and constraints during the project planning phase - an area usually breezed over, with devastating consequences.

This is a good book for software leaders who need ideas on how to improve the engineering culture in their organization. I thought the Culture Builders and Killers in each chapter were particularly useful.

A practical guideline for building strong and successful software development methodologies.

Wiegers' experience in a relatively small group at Kodak and his practical approach embodied in this book provide sound and strong encouragement for anybody to improve their software processes. There may be no silver bullet, but this book comes awfully close.

The books came to me in like new condition. Thanks for your prompt service. I would order from this company again. Great service.

I liked reading it. Was simple to understand. I got a lot of info. on starting a web page. The only thing is it shows you how to use a program to get a web page going but its only 2 programs so if you don't have the programs that it helps you with than don't buy this book.
The programs are Macromedia Dreamweaver MX 2004 and Microsoft FrontPage. It also helps you learn about some basics about photo editing and some graphics. I got some good use out of it. I just wish that it had the info. on my program I have. Other than that its a great book very informative about the basics of running your own web page.

i generally have found the for dummies series to be helpful, and this book is no exception -- you can sit down, thumb through it, and create a photo album online quickly without having to wade through any technical jargon or fluff. i'm no slouch in the web development department and even i found lots to like about this book -- it has helped me explain certain concepts and steps to my less technical family members. i'm including it with my standard baby shower package from now on (which also includes an aromatherapy relaxation candle, lip moisturizer, charmin-to-go, dove facial cleansing wipes, hand sanitizer, and other small items that new moms appreciate).

If you've ever been bugged for photos from the family reunion, or wanted to show off your new kid/cat/car, this book actually makes it seem easy. I know, I know, putting up your own website has a reputation like dragging all your neighbors in and making them sit through your vacation slides used to. But this book shows you how you can still show off a little, without boring everyone to tears. Actually, you can do some pretty neat stuff, which can be really fun when your family is scattered all over, and you don't feel like running up the long-distance bills just so you can keep up on current events.

Very highly recommended.

As with the other For Dummies books, this book is intended for beginners and absolutely minimizes the jargon. At the most basic level the book provides a series of templates that can be used with a fill in the blank approach to get a site up and running quickly. Then it branches out to increasing the creativity by designing your own pages. At this level there is almost no mention of dynamic database driven sites. This is building a static web site with pictures and text. This is a book to get you started.

Most of the book is on showing you how to do things using Microsoft's Front Page. But on the CD is a trial version (30 Day limit) of Dreamweaver MX 2004. In addition, the CD includes:

Family Tree Maker
Contribute
Fetch, and
WS_FTP.

If you're a complete beginner to web design and programming, here's a good way to get started.

As book titles go, CyberRegs: A Business Guide to Web Property, Privacy, and Patents sounds uninteresting. Fortunately, what the book lacks in flashy titles, it makes up in interesting content. CyberRegs is an engrossing and sometimes angry look at the perverse nature of patent law.

When many people think of the Internet and e-commerce, they think of a series of open and non-proprietary standards that enable computers to speak networking Esperanto. As the book shows, that does not necessarily jive with reality. Many companies have tried to homestead on pioneering technologies and use them to gain a lock on the market. Author Bill Zoellick cites numerous cases -- many still in litigation -- to illustrate this point.

The book starts with a brief background of the nature of copyright and patent law and doesnýt assume any type of legal background or expertise. Zoellickýs writing style is easy going but to the point, and he accomplishes his goal of examining the disruption and instability that the Web has introduced into the world of intellectual property.

Zoellick looks at the Web from many different perspectives, from business and legal to technological and political. While some may think they don't need a book about Internet law and regulations, the reality is that, for any organization doing business on the Internet, there exists the strong possibility that they may be infringing on someone elseýs intellectual property rights.

One of the most controversial issues that the book looks at is one-click patents issued to Amazon.com. The one-click patents preclude any Internet business that has not licensed the technology from Amazon.com from enabling their customerýs to complete their purchasing experience with a single mouse click. The question of whether one-click is even patentable is a controversial one. Those who say it is, feel that Amazon.com is protecting a vital business asset. Those who donýt support it say that it only serves to stifle productivity. Zoellick gives numerous other examples.

CyberRegs also goes into such issues as digital signature and privacy. Zoellick does not take sides, but provides a fair-minded look at the debate between greater and lesser control of privacy and the Internet. The book also tackles such controversial topics as the Digital Millennium Copyright Act, Napster and DeCSS.

In part 3, Zoellick provides an excellent overview of digital certificates. He goes into detail on the parameters around the groundbreaking E-SIGN (Electronic Signatures in Global and National Commerce) act. Many have complained that E-SIGN is extremely light on details and specifics, which it is.However, Zoellick says that with E-SIGN, Congress took the approach that we donýt really understand how to do business on the Internet so issues surrounding authentication of electronic signatures are not necessarily easy problems to solve.With that, Congress restricted government action to the parts of the problem where they are directly involved and required.Congress recognized that for any effective solution, markets need time to develop and patience is required. Although this approach is hard when dealing with Internet time, it is nonetheless necessary.

You donýt have to be a lawyer to appreciate CyberRegs. Anyone who wants to have a business presence on the Net should read this book so as not to get involved in a legal tussle. While John Grisham may own the legal fiction market, CyberRegs is as close to a non-fiction legal thriller as you can get.

I am a senior engineer for network security operations who frequently reviews technical books. I was hesitant to read "CyberRegs," given its "Business Guide" subtitle. Noticing the book mentioned controversial topics like the Digital Millenium Copyright Act (DMCA), Napster, and the DeCSS case, I decided I'd give "CyberRegs" a try. That proved to be a wise decision, and I strongly recommend this book to anyone worried about the future of the Internet.

The book is exceptionally well-written, with a clear style and a welcome lack of typos (gasp). In a former life I read plenty of boring, repetitive policy books, but I had no trouble digesting "CyberRegs."

The book is arranged around the themes of copyright, patents, electronic signatures, and privacy. "CyberRegs" gives both sides of each argument, but wisely includes the authors own helpful opinion. (I was pleased to see the author share many of the security community's views on the DMCA, Napster, and so on.) Because Zoellick presents balanced arguments, readers will understand the opposition's complaints and can more effectively counter them.

"CyberRegs" was written to help business people engage in the debates and legislation shaping the Internet. Along the way the reader gains a solid historical understanding of how we arrived at the current state of affairs. Would you believe that software or business methods weren't patentable until recently? Would you believe the United States was the world's most egregious intellectual property pirate until 1891? Given this background, readers gain a sense of why policies developed, and how one can help influence the present and future of the Internet.

I found no major weaknesses in this book or its arguments, but I have two technical/security comments. First, "Web bugs" can be used to transfer more information than an IP address; some use "Web bugs" to validate email addresses. Second, giving customers access to data collected by businesses opens bigger doors for malicious hackers to manipulate that data. Readers may share these concerns, which the author doesn't address.

"CyberRegs" seems marketed as a "business guide," and speaks in part to "business people." As a technical person, I gained the knowledge needed to better defend my opinions on copyright, patents, electronic signatures, and privacy. Technical staff looking for the "why" of state of the Internet will probably love this book -- I certainly did!

(Disclaimer: I received a free review copy from the publisher.)

This is a complete primer on intellectual property and its value to the enterprise. Key issues that are addressed include:

Digital Millennium Copyright Act (DMCA)- this is probably the most important discussion in the book because it continues to be controversial.

Complete discussions of all aspects of intellectual property law as it pertains to cyberspace. The clarification of the protections afforded to patent holders that are not given to trademark holders is invaluable. In addition, I learned much about the value of patents and how a business model can be developed around patents alone. I particularly liked the discussion of patent ownership (employee inventor vs. company to which the patent was assigned). This alone makes the book worth reading.

Case studies - many of the case studies which are used throughout the book focused on pending court cases when the book was published. Many have now been resolved, the resolution of which open more questions and further cloud issues. I'd like to see an update or second edition that provides closure.

Excellent introduction to technical issues. The author has a knack for reducing the key elements into easy-to-understand chunks of information that teach non-technical readers quite a lot about technology.

If you buy one book on intellectual property law from a cyber-business perspective, this is the one to get.

Laws relating to patents and copyrights are always moving targets, but at this time they are running on jets. The speed with which technology is changing how we use things has left the legal system struggling to understand, much less keep up. However, it is a critical part of our society at large, as well as how we do business now and in the future. Therefore, all citizens need to understand the basics of the law and it is unconscionable that anyone in business would not understand the rules of copyrights and patents to a high degree. Yes, it is possible to hire lawyers, but they are expensive and cannot be with you every moment of the business day.
This backdrop serves to demonstrate how critical this book is to the management of the modern business. Since an Internet presence that allows for interaction is nearly mandatory, this could be the most important book you read this year. It already has a place on my best books of the year list for 2002. What makes the book so impressive is that the author pounds home the point that copyrights and patents are not fundamental rights, but are in fact derived under the basic notion of the common good. They are designed to encourage the creators of new things to make them available for the general society, while reserving certain key aspects for the inventors. The case involving the music swapping company Napster is examined in detail without a step up on a virtual soapbox. Zoelick also recapitulates the famous legal case over the video cassette recorder, which went all the way to the Supreme Court, where the decision turned out to be a sensible one.
The end result of that case should provide all of us with an object lesson concerning new technologies. It is clear that fighting the new technologies is at best a holding action rather than an effective long-term strategy. The best solution is simply to ferret out the best ways in which your business can open new markets and profit from the changes. Yes, changes in copyright law take many years to resolve, but in the end, the market and society will get the greatest good, which is the way it must be.
This is a book that should be required reading of anyone in business who makes decisions concerning intellectual property. In fact, some of the chapters are recommended for any citizen concerned about how our society is changing, as the effective resolution of these issues may have a dramatic affect on our economy.

Although CyberRegs has a much wider audience, my perspective of this book is that of a competitive intelligence specialist. The four topic areas covered, from a CI specialist's point of view are illuminating.

The first two topics, copyrights and patents, are the foundation of intellectual property and by extension, corporate and shareholder value. The author's discussion of both copyrights and patents expose loopholes that can work for or against you, depending on which side you are on. One theme the author repeatedly addresses is the fact that copyright and patent law is lagging behind the technology. He cites numerous case studies, all of which you will either applaud or condemn depending on which side of the issue you happen to be. As a CI specialist who engages in "white ops" (collection of competitive intelligence using legal methods), I was somewhat dismayed by aspects of the Digital Millennium Copyright Act (DMCA) because it draws legal boundaries that didn't previously exist. The CI community needs to be aware of this particular law because what was heretofore "white ops" may fall under black ops (illegal intelligence gathering) under the provisions of the DMCA.

The more technical topics, electronic signatures and privacy, are presented in the same balanced and thought-provoking way as copyrights and patents. Having recently read Bruce Schneier's SECRETS & LIES I had some insights into the technical aspects, but the nuances that Mr. Zoellick brings to these topics makes for compelling reading. He manages to raise thorny issues and provide answers from both sides of the issue.

Overall this is an invaluable book that should be read by anyone who seeks to understand the current state of intellectual property laws, the challenges imposed by the connected world, or how the laws and challenges combine to change the playing field. As stated above, the DMCA alone will have wide implications in my profession, and is certain to affect business operations and corporate policy in far ranging ways.

Very good book, explains real-worlds issues one faces when developing COM components.
A few first chapters are extremely useful (something I had to learn hard-way. Have I had this book, I would have saved myself many hours restructuring my projects). Basic ATL types are also explained and recommendations given are very good.
Concise but very useful is explanation of BSTR, OLESTR, CComBSTR, _bstr_t types.

This is an excellent book; a little pricey, but worth the money if you are serious about COM+. And I mean serious! This is not a beginners book, for that I would recommend "Inside COM+ Base Services" by the same publisher. This book is a little too biased towards MS development environments. For example they compare VC++, VB, and VJ++ and casually mention there are "other capable environments". Hmm. Then again, this is a Microsoft press book, and COM+ is a Microsoft technology, so its to be expected.

This book picks up where introductory COM books left off. The first chapter is about error handling in your COM+ objects - not a good place to start learning COM :)

Particularly useful to me was the last third of the book, the design patterns. Here, the authors give us a meaty example of a "real world" COM+ enterprise solution. What other book gives you this? Answer: none. Get this book!

This book, is without a dought, the best COM book ever done. In my seven years as a working COM engineer and some say expert, I have read and bought every single book on COM. And when you come right down to it, even Don Box's book, they are all the same: explaining IUnknown over and over again, rehashes of available documentation and books with esoteric and useless ICat and IDog interfaces. None of them deal with the real COM world and the problems we really face every day. This book does. This book assumes you are a working COM developer and focuses on the hard problems: Smart Pointers, Strings, Enumeration Interfaces, Streaming and trying to deal with the world of STL. It offers real solutions and real code that can be used today to bridge to the STL world and to deal with things like enumerations. It offers code to deal with COM enumerations and collections, a topic scarcely covered. This book has become my number one resource.

An excellent book. The early chapters reveal solid solutions to oft-encountered COM problems - error handling, string manipulation, smart pointers, multiple-reader single-writer locks, streaming and marshal-by-value etc. The later chapters concentrate mainly on design techniques for building scalable applications. In my (humble) opinion, chapter 13: The MTS Revolution is worth the price of the book alone. This chapter describes the evolution of technologies for building scalable systems, introduces the single-concurrent-client model and explains how to write scalable systems keeping code maintainable and in the general case, lock-free. All would-be COM+/MTS developers should read this chapter! I've read both this and Tim Ewald's Transactional COM+ - both excellent books and compliment each other very well. In my opinion, Brown's chapter 13 is far superior to Ewald's chapter 1. Both attempt to acheive the same thing, coaxing the regular developer into the COM+ mindset, but Brown's offers logical facts and reasoning as opposed to Ewald's non-real-world convoluted IPerson examples.

This book covers the software design aspect of COM+ with very good detail explanation of the why and what are your options in COM+ system design. The book also covers in depth discussion in using STL, architecture pattern, MBV and concurrency which are very valuable to software designer. If you are going to work on a software development that uses COM+, this book definitely will save you a lot of research and experiment time and resources.

EXCELLENT book.... I cannot rate this one high enough.... at firstI thought it might have been expensive but it is NOT... the price is well WORTH it for what you get, Knuth is a master!

This book won't teach you TeX or Metafont. It might not even teach you all that much about particular algorithms (although Chapter 3 is one of the most detailed explanations of TeX's linebreaking algorithms published anywhere). Instead, this book offers a look behind the scenes.

Instead of beholding TeX and Metafont in their almost final versions, as published in _TeX: The Program_ and _Metafont: The Program_, respectively, you see them grow from the first design studies (when Knuth thought of TeX as a program for two grad students to write over a summer) to where they are today. You see how the collaboration between Knuth and Zapf on the Euler fonts worked, and you get another glance at many facets of Knuth's mind (And a beautiful mind it is indeed, even though it is entirely sane).

If you have any deeper interest in TeX and Metafont, this book is well worth the money.

This book collects numerous writings on TeX and typography from one of the greatest coumputer scientists of all time, Donald Knuth. Here you get to read fascinating inside information on Knuth's earliest development of TeX, how doggone hard he worked to get the letter "S" just right in his computer modern fonts, how to typeset his wife's recipes, and other bits of amazing minutiae. Knuth's style is breezy and funny in a wry-dry kind of way. (He's the kind of down-to-earth genius you'd love to take out to dinner.), and I was amused to find out that he seems to be a film buff. (His journal from his early work on TeX shows that he went to see "Earthquake," for goshsakes, "to relax"!)

This is a brilliant book, a book to treasure, and with its relatively short essays, a book to keep handy for bathroom reading. But then again, you may get addicted and just keep reading one chapter after another! If you love TeX (or LaTeX or AMS-TeX) as much as I do, you'll have to have this book. It's that good, and you will not only be astounded by his genius, entertained by the presentation, but you'll learn things too. Trust me on this one.

I got this book primarily to understand the word-wrapping algorithm in TeX,
and just that chapter alone was worth the price of the book.

Having said that... when explaining algorithms, I find Knuth concentrates so
much on the minutiae that the bigger picture is often lost; but that's just
his style and the exposition is always very clear. I've gone through parts
of TAOCP, so his style of teaching wasn't a complete surprise to me.
The word-wrapping chapter itself has a very leisurely style with a lot
of history and background, and it was a very enlightening and pleasant read.

The book itself is a selection of papers, articles, transcripts
of talks and working documents by Knuth on TeX and Metafont
(for the most part.)

Some chapters were not particularly interesting to me, they dealt with
specifics of tricky typesetting with TeX, which I feel has a clumsy
programming syntax.

Other chapters were great reading as they dealt with the historical
development of TeX and Metafont. For example, he writes about his collaboration
with Hermann Zapf on the AMS Euler typeface, which gives great insights
on how fonts were developed with Metafont. There are a couple of chapters talking
about his fascination with digital typography and his gradual descent (or is that
ascent!) into developing TeX and Metafont, and they were fun to read.

If you're a Knuth fan, you'll definitely want to get this book. The historical
material makes for nice, light reading, and if you get the urge, you can plunge
into the technical chapters and see some interesting gears within TeX
and Metafont.

This is a highly stimulating collection of essays about TeX, typography, the delectable art of programming, the joy of a beautifully constructed letter A, the world, the universe and everything. Knuth's style is, as always, eminently readable and possessed of a fluidity unmatched in technical writing this century. Definitely recommended.

All in all just a fascinating book on a fascinating topic. In general, the introductory parts of each chapter are accessible to anyone with a standard 12 year education. The mathematics are best understood by people with a background in algebra and statistics at the American High School level, but not much more. If you buy this book, expect John Ashcroft to put your name on a list of people buying dangerous published works (and with the Patriot Act in place, I am neither paranoid nor joking). The best chapter is the one about encoding information in ordered lists. This book taught me how to include a one line hidden message in a 50 item list of my favorite Country and Western Songs of all time (and THAT is a cool thing to do).

This book is a great introduction to learning how to hide data in places most people wouldn't think about looking. Sample code and various URL's are provided for places to start, this not the easiest subject to grasp, but the book helps put it at a manageable level.

A great place to start!...

This is a deep, serious book about making information transmogrify, even if there are a few silly parts. I liked the funny parts and they reminded me of Goedel Escher and Bach

This is a very easy read that does not really assume much about the reader other than mathematical maturity at the precalculus level, knowledge of programming in a higher level language, and a curiosity about hiding information in such things as images. In fact, I bought this book to get a grasp on how to hide a watermark in an image. The early chapters are devoted to material that forms the basic toolkit for steganography - private key encryption, secret sharing, and error correcting codes. The later chapters describe how to apply these techniques in various ways to hide information.

Chapter 5 discusses common data compression algorithms, not to the point that you could write an encoder/decoder system, but so that you know which allow perfect reconstruction and which do not. Compression leads to the topic of mimicry, which is the subject of chapter 6. Basic mimicry produces text that looks statistically similar to the original text but is far from perfect. Chapter 7 shows methods of improving mimicry techniques so that the mimicked text not only passes statistical tests for similarity to the original, but passes rules for grammar. This leads to the concept of context free grammars and their role in mimicry. Thus, you can hide data in realistic sounding text.

Chapter 8 concentrates on a robust and complete model known as the Turing machine. Such a machine hides data as it "runs forward", while running the machine in reverse allows the hidden data to be recovered. Certain proofs show that this is a stronger data hiding model than those previously discussed.

Chapter nine discusses a more image-processing related data hiding topic - hiding in the noise. What appears as noise to the untrained eye can actually be a message. Of course, the flip side of this is "real" noise has the power to obscure the hidden message.

Chapter 10 discusses anonymous remailers, which is the deletion of the name of the originator of a message by an intermediate node. Such systems can range from very secure to very insecure depending on strategies involved. Chapter 11,"Secret Broadcasts", is a companion chapter on how to broadcast a message so that everyone can read it but nobody knows the source. The solution lies in the "Dining Cryptographers" algorithm, and this solution is discussed at length.

Chapter 12, "Keys", discusses message keys as extensions to the concept of keys in basic cryptography, which was discussed earlier in the book. Adding keys to any algorithm discussed up to this point makes that algorithm stronger. Chapter 13, "Ordering and Reordering", discusses how steganography strategies might be disrupted by reordering parts of a message, and discusses methods that might prevent this from being a problem.

Chapter 14, "Spreading", is a more mathematical chapter than the preceding ones and takes a different approach to the problem of information hiding. It takes ideas from spread spectrum radio and applies them to steganography. This is the one chapter where a knowledge of calculus, Fourier transforms, and even wavelets will be helpful.

The last three chapters, "Synthetic Worlds", "Watermarks", and "Steganalysis" are short and more subjective than previous ones, mainly giving the reader a broad overview of these topics.

The book has a wealth of algorithms, equations, and simple examples. There is even a very basic Java mimicry program in the appendix. However, this is not a programming book full of ready to implement solutions - you will have to do that yourself. There are numerous references to web addresses where you can find both executable and source code for implementing some of the algorithms mentioned in this book. I would say if you are interested in hiding information in data of any kind - text, sound, imagery, etc. - then this book is essential reading. I highly recommend it.

I read the entire book from first to last page and enjoyed the content absolutely. The book has theory and practice, clear examples and many references to free and open source software to make tests. The math part has razonable level (not too much, not to little). I have no found anything better in the area.
Good for Peter Wayner!

P.D. ...