Software Books

I've been designing games for more than 20 years and I've read a ton of books on the subject.
This one is unique.

Most game design books focus on teaching you how to make a good game, detailing what techniques and processes one must master to understand an audience, to design a product that will satisfy their needs and aspirations, and to work with a team to produce it. "The Art of Game Design" goes beyond that: It teaches you how to become a better designer.

Here's an excerpt from the Deck of Lenses' instructions (it's the deck of cards sold separately that illustrates the 100 design "lenses"):

How to Design a Game
Step 1: Think of an idea for a game (it's easy, it can be anything!)
Step 2: Try it out (no really - try it out - you have to play games to see if they work)
Step 3: Figure out what's wrong with it, and change it so it is better. Then go back to Step 2!

That's what game designers do, over and over again, until they're satisfied with the game or they run out of time or money. However, if there are lots of books out there that explain how to increase the quality of whichever aspect of the game you want to change, it's the first one that so directly and so thoroughly addresses the problem of "figuring out what's wrong" with a game at each iteration.
In the book, Jesse Schell presents one hundred ways of looking at your game in order to figure this out, one hundred lenses. Even if this number seems big, it really isn't, because the book covers every domain touched by design: from the nature of the playing experience itself, to understanding the player, the game mechanisms, interface, story, technology, theme, etc.
For instance, here's the sum-up of a lens taken at random:

Lens #82: The Lens of Inner Contradiction
A good game cannot contain properties that defeat the game's very purpose. To remove those contradictory qualities, ask yourself these questions:
- What is the purpose of my game?
- What is the purpose of each subsystem of my game?
- Is there anything at all in my game that contradicts these purposes?
- If so, how can I change that?

The book doesn't give answers but helps you ask the right questions. I think of this book as the Tao of Game Design, a path toward understanding, each step its own path that can be explored and perfected. The one hundred lenses are one hundred design domains in which a designer can become more proficient. Jesse Schell's knowledge, experience and talent are obvious when he clearly explains how to consider all these questions, why they are important and how they are linked together.
This book makes and helps me think. To me, that's the best things a book about design can do.

It's rare to find an instructional book on any topic that takes such a broad, holistic view of it's subject matter. Not only is it loaded with useful info on game design, but many of it's methods can easily be applied to the creative process in general. It's depth and breadth of thought set it easily above any other game design book I've come across.

The Art of Game Design is a book which provides an easy read, it has a simplistic elegance to it, yet the depth of the book is quite deep which will keep you thinking for hours upon end. For me one of the most impressive things about the book is that it pretty much covers everything that a game designer should be aware of and how their decisions will effect the real world (it even talks about the moral obligations which I have never seen covered in a book about game design!). If you really want to learn the depth of being a game designer this book is a must read.

The Art of Game Design is simple in its language yet intriguing in its concepts. Jesse's well written book is equivalent to a four year undergrad degree in the same subject. The bulkiness of the book might seem overwhelming, but once you start reading, you delve right into it without you even knowing it.

The book draws inspiration from a myriad of topics and fields and definitely provides life lessons on a deeper level. The philosophy and its understanding helps in knowing yourself better, first as a person and then as a designer.

The Art of Game Design will inculcate a positive design perspective to the way you observe everyday things and events. Even if you are not a designer, it certainly is an excellent addition to collectibles that broaden your horizon. A must-buy for those aspiring to be a designer.

good things come to those who wait - and i have been waiting for this book for years. jesse schell has managed to compose not only a game design guide through an idealized design process, but also a handy catalogue of "lenses" that will help designers to inquire whether their game is enjoyable, or not, and how to improve the design. most importantly, 'the art of game design' provides intellectual as well as practical inspiration throughout - what more can you ask from a book in this field?

Prolog remains academic but still of great educational value. But to get to that value, you need to get past using prolog like a smart procedural language. This book and especially its last few chapters achieve this goal. For this reason I recommend it as a must read for any decent computer scientist.

I am currently working as a computer hardware design engineer. I have always been looking for new software methodology to improve my hardware design flow. Prolog, and especially its presentation in this book, shows me an interesting and powerful view of how computer programming should be.

Overall, I am a true believer in Prolog and logic programming after reading this book.

This, to me, is one of the 4 best books on computer programming. Unfortunately, it is hard. Not because the book is poorly written - it is like a wonderful story, but because understanding how to think declaratively after being taught something like C or Java is like someone giving you a pair of wings when you're a mudfish.

Thinking declaratively changes how you think about problems and how you write code. It's a career changing experience. This book leads the way.

Top 4:
* Structure and Interpretation of Computer Programs (Sussman, Abelson)
* The Art of Prolog by Sterling/Shapiro
* Introduction to Algorithms by Cormen, etc.
* Concepts, Techniques, and Models of Computer Programming by Van Roy and Haridi

Admittedly, this one tends to be a bit pricey. But, the content is pure gold for any programmer. Nowhere is the Prolog paradigm better conveyed than here. And, it is of little value to you if you attempt to learn prolog with a mindset of some other language. Prolog is unique and demands a unique way of looking at computer programming in general. It is dated a bit in that it does not cover all the latest developments in Prolog/AI research but no other Prolog books provide the foundational understanding that it does. Get this one for a solid foundation and then build on it with others. See my listmania list of AI Language books for suggestions of followup titles.

This book is a must for anyone starting to program in Prolog or interested in logic programming.

A downsize of the book (if any) can be that it could have detailed more in the respect of Prolog's applications. The pleasant style of the authors would have made a wonderful introduction into these fields.

A real pleasure to read.

This is a well-organized and comprehensive introduction to Grails. The reader will come away with a lot of exposure to the Grails way of doing things, which was kind of a shock for a hack like me who is used to mixing sql queries with html and changing entire schemas at a whim. The authors do not assume you know MVC or even Groovy, so I think it would be a good book for anyone with a bit of Java coding under their belt.

The source code presents some difficulties, although some of these might be attributed to Grails and Jetty. One problem is that all the collab-todo examples are called "collab-todo", which seems innocuous enough but it causes several problems as you proceed through the book. Often Grails leaves all sorts of artifacts in GRAILS_HOME that corrupts different versions of collab-todo. I found myself having to run rm -rf ~/.grails/1.0.3/projects/* before things would work properly for the next chapter. Secondly, I found it impossible to deploy multiple demo chapters at the same time, which would have been useful to see how the author edited various files to achieve increasing customization. Even when the application.properties file was altered to give the deployments different names, the lightweight jetty app server would display a "port already in use error". If I chose a new port for new deployments, there were still deployments files that were still using the directory name "collab-todo" instead of "collab-todo4", my renamed app.name, which caused all sorts of weird runtime errors. The authors and testers really should have foreseen this problem.

Another albeit smaller problem is that the .project files used for Eclipse or IntelliJ are missing for chapters 6 and 8 and I don't think those are really finished demo freezes - I'm not sure if this was intentional or not. I suspect they were not meant to be deployed. If that is the case they should put that in the README. The unfortunate things about chap 6 is that it would have been good for a working MySQL example. There is no formal introduction into using a different backend database until chapter 12, an example so complex it threw all sorts of Hibernate errors in prod mode.

I think the collab-todo project is a decent model for the average web application. However, in some sense a lot of the quick webapps that would have previously been done in Visual Basic or FileMaker Pro can now be handled by Rails/Grails, so a migration example starting from a poorly maintained Excel spreadsheet with no normalization and no keys might have been useful.

After banging my head against JSF for a few months I was happy to see a framework that has proper respect for GET and for a developer's need to have control over any element of a web application without question. I just didn't want to bang my head to get some of these Grails demos to work. Still, this is a decent read and well worth the money.

This book is an excellent way to get started with grails development. This book provides a solid foundation and excellent coverage of the grails framework.
The book starts out with a 3 chapter overview of the groovy language. After that starts the Grails Sections, Which are very fluid working though one application (Collab-todo) from start to finish. Showing you how to use features such as plugins, ajax frameworks, security and web services. This book will really get you going with grails fast.

As a Java developer who is a true beginner with Groovy and Grails, I found Beginning Groovy and Grails an excellent starting point. The book's strength is providing a core structure for the Groovy language and the Grails framework, then building on them.

I had read other Groovy books, and still use them as a reference. But BGG kept Groovy at the right level for me to start -- showing the core features without getting bogged down in the details. I was able to work through the examples and get an excellent feel for the power and elegant simplicity of the language.

The Grails overview is an excellent start to understanding the framework. I appreciated the step by step introduction to setting up and evolving a simple web application.

In terms of writing, I found this book very readable. I wish that the copy editors had helped out a bit more in spots, and the errata pick up some glitches in code, but overall I truly appreciated the authors' efforts and have learned a great deal.

I concur with the previous reviews. I've been looking to dive deeper into Groovy and Grails for a while now. I'm hoping this is the first of many new titles to come on this subject. I would really like to see the language and the framework take off as it should. There are many people out there doing cool things with both like Graeme Rocher, Guillaume LaForge, and one of the above reviewers (Scott Davis....you gotta see this guy talk about Groovy if you can!). People who work in the Java space really should give these technologies a look. This book should really get you going. I would also suggest looking at some of the book offerings by the contributors mentioned above. Good stuff. Buy this book!

Let me start by saying "Beginning Groovy and Grails" is the book that the Grails community has been clamoring for. Two very good books kicked off the Grails revolution ("Definitive Guide to Grails" and "Getting Started with Grails"), but both predate the 1.x version of Grails by many dot-versions and many years (as of the time of this review, August 2008). BGG will certainly have worthy competition on the bookshelf before long, but right now it is the book that we all have been waiting for. Luckily, it easily lives up to the heightened expectations.

After reading BGG cover to cover, it seems to break naturally into three sections: Core Groovy, Core Grails, and Ancillary Grails. This division is mine, not the authors; the table of contents lists 13 chapters with no explicit section breaks. (Whether the three sections correspond to the three authors is an interesting question -- the tone of voice and writing style is consistent across the entire book.)

The first three chapters do an admirable job of covering the Groovy language from the basics to advanced topics. Groovy offers lots of syntactic sugar that might initially catch a Java programmer off-guard. These features, once you've seen them, dramatically reduce the lines of code you have to write. But more than that, there are some fundamentally new features in Groovy that don't have an easy match in Java. Builders, Expandos, metaprogramming, and DSLs are all discussed in these early chapters. While you don't have to use these features yourself to be successful in Grails, it certainly helps the reader understand how much of the Grails "magic" occurs under the covers.

The next three chapters (Introduction to Grails, Building the User Interface, and Building Domains and Services) hit the Core Grails features hard. These 150 pages do a great job of walking you through the basics of getting a Grails application up and running with a minimum of effort. They also make testing feel like a natural part of the development process (which it should be!). Rather than having a single chapter dedicated to testing, each new topic organically includes testing as a way to validate that the new code does what it promises to do.

The remaining chapters (Security, Ajax, REST, Reporting, Batch Processing, Deploying, and Alternative Clients) make up close to half the book. Each chapter covers the subject material as advertised, including working sample code. Not every Grails application will use every feature discussed here, but I still found a clever snippet of code here or a nice explanation of a general concept that rewarded me for reading every chapter.

Overall, "Beginning Groovy and Grails" delivers on its title -- if you are new to either (or both) technologies, you will be up and running before you know it. But don't be fooled by the title; even though it has "Beginning" in it, this book doesn't shy away from the advanced topics, either. This isn't a completist volume. Rather, it is a broad survey of the Groovy and Grails ecosystem. Christopher, Joseph, and Jim covered a lot of ground in an easy, readable way. I highly recommend it.

I would say this book is particularly good if you don't come from a Mac development background. The Sadun book I think assumes a lot of Mac programming background. This book is much easier to just pick up and start using, especially if you are familiar with other gui development environments like c sharp or some other gui development tools.

A word of advice for people who want to use the the apple iphone dev sample code. When you download it seems to put all the files in a temporary place that you can't save to. You can use it in xcode once but you can't save it or changes for later use. I'm sure the mac guru's have a better way to do this but I found you can see the temporary space the sample code goes to after you download it in Finder. When you are in that temporary directory Apple Key a, the Apple Key c, then Apple Key v into another permanent directory. Then you can use xcode project open to have permanent access to the code.

Before any iPhone development books were released, learning the frameworks was next to impossible for me. There was just no easy way to learn iPhone development until now. It's extremely well written, and feels carefully crafted to maximize understanding - not just quickly thrown together to get the first iPhone dev book on the market. I would reccomend this book to anyone interested in iPhone development.

I've been learning Obj-C for iPhone for about 3 months and this is by far the best book I've come across. It explains things like nothing else I've read and I have been doing exercises from the book involving things I thought I already understood, just because things become a lot clearer after reading it. Highly recommended reading.

When this book arrived, and I saw the book cover, I knew I got something different. Not a cookie-cutter book but an original piece of work where somebody really intended to teach something.

I just got this book a few days ago and with this 4-day Thanksgiving weekend and living alone I have been having a blast focusing just on this book. I haven't read through it all yet, still just a quarter of the way through, but I'm not trying to cram. This book does exactly what I want a book to do (as opposed to an online reference resource): stop and talk about every little thing that is really useful to know in the workflow of applications programming on an iPhone.

These guys know how to write. They don't leave the reader with presumptuous word choice and leave the reader hanging; every time they say something it's like they read the mind of the reader, "Now you might be wondering, what about... or why not do ... Well, let's talk about that." Nearly every corner is covered, and where I still have questions it's usually not directly related to the topic, i.e. I have an Obj-C question. Even then, after I return from surfing the web for answers, I return to the book and turn the page and the book says, "You should read up on this stuff at [URL]"... I kid you not, this book had me floored.

Looking towards the latter pages of the book, I can't help but be astounded, thinking, wow, I get to learn about THAT? And in the same style of learning that I've been enjoying so far? This is great!

There are very few errors, mostly just little things that the reader can spot just by paying attention. There are plenty of enough illustrations and tips to keep the reader engaged and constantly learning not just the basics but how to get comfortable in the workflow of iPhone development.

My only disappointment is that the book assumes knowledge of Obj-C, but fortunately it comes with plenty of URLs and references to complete those prerequisites as well, and really, to discuss Obj-C in detail, beyond the rather brief coverage-as-we-go that is indeed in this book, would have been beyond the scope of the book so that's fine.

There's just nothing I can say bad about this book, and everything good. It is by far the funnest technical book I've owned and cracked open in months, if not years.

By the way, coming from a C# background (and Java and VB5/6 before that), lightweight programming of the iPhone is EASY!! It's different, but it's easy, particularly compared to C++ programming which I've had a number of false starts. For me, if I can go from VBScript to VB6 to Java to C#, I can go from C# to Obj-C. Also, the workflow of Xcode + Interface Builder is somewhat analogous to the workflow of Visual Studio + Expression Blend 2 for WPF programming, if indeed event handlers would have been set up in the Blend designer in a drag-and-drop way. I must also add, learning how to develop software in Xcode forces the developer to learn MVC. I don't know why people who are used to Visual Studio programming dislike the MVC-ness of Xcode programming, but I love the change of workflow, and I think there is much to take back with me when I return to C# development.

In keeping with Dave Mark's excellent track record for introductory Mac development books (referring to his Learn C on the Mac classic) and Jeff LaMarche's obvious talents, this book is THE book for those new (and really, who isn't?) to iPhone Development.

I'll start by saying that relative to the Apple samples, the authors are heavily into Interface Builder usage, which is good to force separation of your Views from your Controller logic, but a challenge when you fumble hooking up an outlet and things don't work as you expect. Understanding how IB outlets & actions interact with source code is different than other programming most of us not from a NextStep heritage are used to. That is to say, for most programmers, debugging and changing behavior in source code is a much more familiar method to follow than trying to fix a NIB file. Not necessarily a better one mind you, but a significantly different one that'll take some getting used to.

That said, from my own brief experience, it seems starting off with a strong fundamental understanding of Apple-flavored MVC from this book, enforced via Interface Builder views and managed via controller source code, is preferable to trying to structure it correctly just in source code (as Apple usually shows it).

With respect to IB, the authors do a great job covering the common mistakes we all make and what you should do to resolve them (i.e. in Chap 6 they mention that if you don't see the proper action popup, you probably control-dragged from the wrong IB component. Nice touch.)

A minor nit, when I read the chapter on autorotation, I didn't find mention of the very handy "autoresizingMask" property of a view (UIViewAutoresizingFlexibleHeight | UIViewAutoresizingFlexibleWidth), which handles the changing sizes of a view for you. They mention it in passing, but it's such a nicely done feature that more people should use, it might deserve a project sample. Bonus: they explain why Apple discourages use of the "upside-down portrait" mode, which is good to know.

The authors wisely emphasize the importance of TableViews, which are so central to so many iPhone app interfaces for a reason. I've skimmed those chapters (8 & 9) and they're the best available anywhere on explaining tables and how they interact with Navigation Controllers and subviews. I'm really looking forward to digging into them. My initial concerns that like a compelling preview to a bad movie (I'm looking at you Zohan) I was worried that Chapter 3 [which Apress has available on their website, google for it if you're looking for a representative sample] would be the best in the book. Chapters 6-9 put those fears to rest.

The remaining chapter coverage is conducive to arming you with the basics to create a solid, stable, fully-featured iPhone/iPod Touch application that combined with your own creativity and hard-work, you'd be proud to display in the App Store.

So, in sum, this is the book to get right now if you're just starting out on developing Cocoa Touch apps. Even after I've learned the basics, I can see myself referring back to this book for refreshers. Thanks Dave & Jeff!

This is a great commentary. In an expository manner, he explains each book of the Bible in detail. Wiersbe gives background information on topics that help make each passage more clear. It is always beside my Bible when I study! I highly recommend it.

I have found Wiersbe's commentaries very helpful in my study of the New Testament and in particular our recent study of Revelation - the Commentary on Revelation had many very helpful thoughts which I found very useful as I prepared Bible studies for my group.

I have not completed reading these books but so far they are exceeding my expectations. Great books for anyone wanting a greater appreciation of the word of GOd and seeking to know him(God) better.

As a Bible college graduate and youth pastor, I could not do without this commentary set. Wiersbe uses everday illustrations and gives a good explanation of the text. However as with many commentators, some difficult passages are skipped.

I use these all the time in my studies. Wiersbe writes at a level anyone can understand and provides many insights that his years of study and devotion have provided.
I would recommend both volumes to anyone wanting to gain a deeper insight into the New Testament.

This book is great for the self taught person with significant insignificant questions. In completing this book, all those questions answer themselves. None of that "cutsie" just great tutorial. Instruction is easily to understand and follow. I've gone through the book a couple of times and discovered something new each time. When I finished with this book, I knew what I was doing and why.

Money well spent on this book.

Straigh-forward writing with no pretension. Some knowledge of 3D graphics vocabulary is helpful but not necessary.

Book is one example from beginning to end; presumably the author. Starts with some pictures and, step-by-detailed-step, ends with an avatar.

The only fault I found is that he doesn't mention Poser in the list of 3D modeling programs for human figures.

If you want to learn how to model a detailed digital human,this is THE book for you! You start out with totally empty viewports,and if you follow the book you'll end up having created a model with an incredible amount of detail.

The author explains in great detail the process of modelling every body part (head,neck,arms,hands,legs,feet and torso) with anatomical references where they're most important.

I wanted a book which I could use as a definitive guide to model a detailed and anatomically correct human body or body part,and I'll look no further when I have to do so. It's also got a clever chapter about modifying the same model to create very different ones, and a good chapter about texturing and UVW unwrapping. Finally, it refers to cloth and hair (somewhat briefly) and,no,it DOESN'T cover rigging. But it does cover, extremely well, human modelling, which is what mr.Brilliant had set out to do,I assume. Very very good!

I used this as a class textbook and it worked fairly well. This is not a single program book so this will work well with whatever program you model with. Although, depending on what you model with, depends on if you need to go out and find plug-ins that will do what he does. The book is really good going through step by step. Although there are some occasions where he leaps forwards ahead with really telling you what to do. Also, sometimes when he gives instructions, there aren't any images to go along with them, so you have to end up guessing what to do.
This is modeling for realism/cinematics and if you want to use this book to model in-game characters, you are out of luck. The was he teaches you to model is extremely high poly (especially in the head). The CD doesn't do much for you, it mainly just has naked pictures of the guy he models on it so you can copy exactly what he does. The book does give good information on the differences between modeling men and women, although it is fairly brief. He does go into UV mapping pretty good as well as modeling hair. The book doesn't, however, go into modeling clothing fairly well, just a short chapter. The book also doesn't even mention rigging, which I think is a crucial part in character modeling.

Given that you are already familiar with some type of modeling software, this book is the best resource you could have! The non-software specific approach of the book keeps it focused on the concepts of creating a good model rather than the user interface. Every detail of the body is covered with step-by-step diagrams, and a lot of it focuses on creating a topology that is animatable and will subdivide correctly (ie the mesh is mostly in quads). It also covers texturing, rigging, facial animation, both modeled and simulated hair, and simple clothing. The book discusses anatomy to the extent that it is needed to create a realistic model, and uses those concepts to demonstrate how the male model you create can be changed into a female, or into a fantasy character that looks completely different.

One thing that did make it a little difficult to use was that in the screenshots, the mesh was transparent and therefore you couldn't tell whether vertices were at the front or the back of the model. More screenshots with an opaque mesh would have made it easier to see the topology.

Overall, the explanations are concise and makes the task seem efficient, easy, and fun.

- The authors of the early chapters talk to you as if you're in highschool.
- Since most chapters are written by different authors, most material is redundant.
- Instead of getting to the point, they try to soften the material with anecdotes and jokes that are mostly immaterial and detract from the information I seek.
- Lists a whole bunch of contracts that are apparently required for a startup, then suggest talking to a lawyer, such as Buy/Sell char Contact. Then why did I buy this book?

+ Great reference for taxing, IP, and some contracts.

Skip all the other chapters and just look at taxing, Intellectual Property stuff, and contracts. That's where the value of the book is.

For anyone interested in understanding the business of video game development this book should be on the top of your list of things to read first. Written for the person trying to get into game development or the person in game development looking to start out on their own. It combines both the business and the legal fundamentals that you need to know to get started in video game development. Includes analysis of publishing agreements and EULA's that are extremely helpful to any game developer. Also includes things you need to know to protect your intellectual property rights and what kinds of things in video games can be protected. The book is not overly complicated and in fact it is written to be easy and fun to read. The authors are all experts in the fields of business and law of video games and you can tell they had a good time writing this book. One of the most interesting chapters includes helpful suggestions from leaders in the video game industry on things that they wish they would have known starting out as game developers. Overall this book is a must for game developers and fun reading for anyone that is interested in understanding the business of games.

This book was invaluable to me in learning about doing business in the video game industry and the concerns that a game development team will face.

While many books which discuss the video game industry will waver in their accuracy on any given subtopic due to the limited expertise of the speaker, this volume avoids that problem by having each chapter written by a different author, each with particular knowledge and experience with their chapter's subject. The Primer is written by more than a dozen experts, including game developers, business persons and law professors, each talking in plain English about the problems and solutions to difficulties and issues that will arise over the course of developing a game and starting a development company.

As a student, I have read a lot of textbooks in the last few years and being interested in the game industry I regularly read magazines and articles on game development. This book is neither of those. It is informative and helpful without being long-winded or wordy, serious in its expertise and insight but fun in its approach and writing. In short, it is the type of reading you will enjoy doing while learning the things you want and need to know about business and legal issues which arise in game development.

This is an enormously helpful book. It is one of the best intellectual property law and game development book on the market that I've read. It is an enjoyable as well as practical text.

Superb book. Enormously Practical text. The best intellectual property law and game development book on the market. A very healthy read. may change your whole perspective on business, games and life.

Phoebe Mentel (computer handle "Pathphinder") is very good in virtual reality computer simulations. She has gotten so good that finally she is going to do something she has longed for a long time to do. She is going after the very powerful Peter Harding with a little help from Phagan, her anonymous boss and a few other fellow runaway outcasts. But, almost from the beginning and thanks to a very small mistake on her part, things begin to go haywire.

At the same time, Deputy United States Marshall Jake Kirby is chasing the same group for other cyber rimes. He has been called to the scene of the death of one of his fugitives. Ollie Smith is dead and was wanted for a variety of computer crimes and high tech burglaries. Jake soon realizes that Dewey Hyatt, another man he is looking for has been to this same apartment where Ollie died.

Bryn Bailey of the FBI soon joins Jake in his inspection of the scene. She works electronic crimes and gotten a hot tip from the mysterious Phagan. She has been hunting him and he still sends her leads to other problems as well as attempting through cyberspace to romance her. While on level she is flattered and interested, on another level she is annoyed with how he toys with her. He toys with her again by leaving her a computer message in Smith's apartment.

While the computer isn't helpful, they find a couple of clues that lead them to JR's Bar in Estes Park, Colorado. Phoebe's one little mistake has lead them to her doorstep and she begins a cat and mouse game with Jake while at the same time, going forward in her plans for revenge. She has very personal reasons for going after Peter Harding and her hatred will not allow her to back down and change her plans now. Once committed, she can't let go. Phagan also plays his own game with in games and continues to seduce Bryn. Soon, both agents of law enforcement face the choice between their hearts and their jobs as the plan works towards a violent conclusion.

While I have simplified the story considerably, there is no simplifying the results of this book. This is a very good novel with plenty of action and complicated characters. The computer stuff was more of a background level and did not overshadow the plot or storyline. The characters are real and complex and the story has plenty of twists and turns. At 242 pages, it was well worth the read and I look forward to reading more work by this very enjoyable author.

This is the second in a series of 3 and I loved every one. This is the first review I have ever written so it had to be really good for me to make this effort! I have read all of Pauline B. Jones' books except Do Wah Diddy Die, which I am about to start. Every one of these books really pulls you in and makes you want to read more. You can't put them down. I want to say I especially liked this Lonesome Lawman Series, but then I loved them all! So I can't really play favorites. It is very suspenseful & romantic with a little humor thrown in! I especially appreciated the author's humor. Read all of this author's books. You will be glad you did.

Also the third part of Pauline Baird Jones's "Lonesome Lawman" series is definitely worth reading. We are reunited with old friends, hence fans of Matt, Dani, Jake and Phoebe shouldn't miss reading this novel on any account. Even Phagan is part of the gang again. All in all, a successful end to the saga of the good looking Kirby brothers. Action and fun guaranteed!

Once again Pauline Baird Jones gives her readers a great story of mystery, thrills, and romance. It's little wonder that she's becoming one of the fastest growing stars in the genre!

If you're facing a dull evening and want to liven it up with something warm and fun, pick up Pauline Jones's book. A fast paced interesting read.

At first glance you may easily dismiss this book; featuring a rather dull cover; size that is dwarfed by the more "popular" C books - do not be fooled! This is an excellent text for learning about the C language.

Admittedly, if you're new to programming in general, then this book may seem a little difficult. For instance the first chapter launches straight into a discussion of C idioms: keywords, variables, operators etc. If these are foreign to you I would recommend you also buy an introductory programming text, then return to this book when you understand these concepts.

These assumptions aside, Kalicharan clearly and concisely discusses control structures and arrays, functions, character handling, data types, input/output and more. The concepts of each chapter are thoroughly explained and incorporated into numerous programming examples.

Indeed this is one of the strongest points of the book. In particular I liked the way Kalicharan introduces the three programming constructs; conditional execution, looping and iteration first, BEFORE discussing for example, the printf statement like most other C books do - which can be highly confusing to the novice C programmer. (Kalicharan leaves it until chapter 9). Thus a strong grounding in the fundamentals of programming is emphasised from the very start and is a consistent theme revisted throughout the book.

Unlike other C books, Kalicharan gives a brilliant discussion of pointers. What is dismissed as "too hard" in other texts is covered with ease and again, numerous examples to illustrate. For this chapter alone, one should buy this book.

Following the chapter on pointers is a good introduction to "advanced" data structures, linked lists and binary trees. These are left out of most other C books, bar those dealing with data structures specifically (university texts etc) but it is here that the power of the C language becomes apparent.

Topping off the book is a chapter in file handling. Text and binary files are discussed.

The range of topics, clarity of expression and *working* examples (I compiled every program in the book without error...) makes this book an essential addition to any C programmer's library. I hope another book from this talented author is on the way soon! (How about Java or C++?)

A friend recommended this book after I complained of the difficulty of learning C, having tried more popularly recommended books. I'm glad she did, for this book made C easy and fun to learn. An excellent book, strongly recommended.

I had Noel Kalicharan (UWI) for my Year 1 programming. Used many of the books he wrote and can vouch for the calrity and ease of use of his books, overall high quality. Even better when combined with his lectures.

A fantastic book! Its simple, clear and systematic presentation and explaination of concepts along with the abundance of examples make learning to program in C an easy task. And all the scary stuff you may have heard about pointers in C become mere rumours after reading the relevant chapters! An excellent book for learning and teaching.

This book is one of the best books explaining ANSI C. It starts from the newbie level and delivers the knowledge needed for any good C programmer to survive.

The writing style is very nice, the author has done some fine efforts in keeping his threads of thought clear and easy to follow.

For people who already know C, this is also good as a quick reference and is something concise to quickly refer to, in small issues. They could also just use it to quickly refresh their knowledge of C every once in a while.

It doesn't cover any advanced topics, but it does what it promises to do, so there's nothing serious to put this book down.

This book could have helped me greatly when I was just starting to learn C programming, but it didn't... Just because I only bought it too late, at the end of my C programming days!

-Mokhtar M. Khorshid

I found the information in this book helpful from the very first page. The tips Mr. Clothier shares in his book are very practical and specific, from writing course material to dealing with "difficult" students. Although the print date is almost ten years old, I found the information to be quite relevant even today. I am not certain, however, whether it is worth the $110 price currently listed. I paid $40 used, and I don't regret a penny that I spent. I keep it at my desk and refer to it often as a refresher.

I have been teaching computer classes for over 5 years. I learn something new everytime I read this book. This book contains many of the things I tell my friends who are struggling with trying to do computer training. I think this book would be good for any company that is interested in computer training.

This is the only book that I have seen which deals with IT training - even as an experienced trainer I still got ideas from it.

Just after reading a few pages I already had enough ideas on how to change my training practices that I made changes on my next course (which was the next day).

I will continue to read, and review everything in this book.

Read it, don't miss out!

This is the only book that I have seen which deals with IT training - even as an experienced trainer I still got ideas from it.

Just after reading a few pages I already had enough ideas on how to change my training practices that I made changes on my next course (which was the next day).

I will continue to read, and review everything in this book.

Read it, don't miss out!

As a human resources and workforce learning/performance professional who has managed and executed all phases of end-user training at various times since 1982, I can't recommend this book highly enough. Although "Encouraging Independence" should be required for all novice computer instructors regardless of where they teach, it still serves as an excellent reminder for the more experienced. (I'm revamping some courseware as a result of that chapter.) "Training Delivery" provides a great outline for a train-the-computer trainer program. And for senior practitioners like me, "Trainer Development" and "Adapting to the Learner" are simply superb. (In the latter, he offers tips for handling different types of knowledge gaps plus cognitive and psychomotor challenges. With congenital and acquired neuropsychological disorders on the rise--meaning greater, not fewer, individuals with these conditions in the workplace now and in the future--plus the aging workforce, such issues have begged to be addressed in books on instructor effectiveness. Clothier rises to the occasion beautifully.) On a lighter note, I'm relieved to read Clothier's recall of an irony I've had: that limited sleep the night before a class has led to greater instructional effectiveness, adrenalin rushes notwithstanding!