Software Books

This is a great book cover to cover. For the admin who has never participated in an Active Directory roll out this book is a must have. The chapters quickly familiarize you the most powerful aspects of Active Directory without much repetitiveness. This is an excellent book for those wanting an overview or for a beginner with Active Directory. Well worth the purchase price.

Hudson and Fullerton definately come through in their presentation of Active Directory! Their clear and concise approach, drawing from their experience in training and consulting shines through! I am in the process of upgrading the network where I now work from Windows NT and this book is an invaluable resource!

The authors have done a very good jobs of explaining several complex matters. More importantly, the authors have clearly shown that they have trenmendous amount of real-world experiece. It's good to know that we still have some authors like that instead of too many professional writers, who have no real world experience and who just paraphase what M$ says about their product on the online help.

Thanks.

Tam T. Nguyen, MCSE

Special Edition Using Microsoft Active Directory provides the network administrator with complete, authoritative, "user friendly", in-depth coverage of the newest directory service from Microsoft. Sean Fullerton and James Hudson use their extensive previous training and administration experiences to expertly explain how to design, implement, and troubleshoot using the new directory service "Active Directory". Special Edition Using Microsoft Active Directory is very highly recommended for users ranging from Beginner to Advanced levels of experience. 554pp.

This book is very helpful if you are planning a Windows 2000 Active Directory design or already have one and need to get the most out of your AD. The authors have organized the book very well making it easy to find the information you need. The book is very useful as a quick reference. Additionally, material is presented in a logical order making it easily readable cover-to-cover if you need a comprehesive understanding of AD.

The authors stress the importance of a solid DNS design and drive home the point just how critical DNS is for good AD operation. There is a good description of forests, trees, and domains as well as much helpful information on planning sites and site replication. The book also goes into detail on printers and scripting.

I found the book very useful for setting up and administering different features of Windows 2000 such as group policy. There are good chapters on Group Policy Architecture and Managing Group Policy.

As an MCSE+Internet certified analyst assigned to the AD design team for a Fortune 500 company, I highly recommend this book. It makes a good operational reference for your bookshelf. Although not geared specifically for Windows 2000 certification tests, it is worth reading if you are preparing for the exams.

This book uses Smalltalk to teach the basics of object oriented programming on Mac or PC. Before getting my hands on this book I have to say I was having trouble grasping the basics.

I personally bought the book as I want to learn Smalltalk. For some reason the "with Robots" in the title had me skip over this book for almost a year. Most, if not all the other Smalltalk books I got, although great, usually assume differing levels of pre-existing programming knowledge and experience and approach the teaching of Smalltalk skimming over the stuff that is a required foundation to *understand* it. Stephane Ducasse does an excellent job of explaining that missing foundational stuff. And he does it without getting too deep into Smalltalk or Squeak itself.

As others have pointed out this book is not really focussed on teaching Smalltalk - Smalltalk is the tool used to teach basic O-O programming. However, he's done an excellent job of doing both!!!

Having finished this book I'm writing basic programs - and finally understanding better the programs of others.

The use of an Integrated Development Environment [IDE] for a user to learn a language in, and to then program within, is well known. Microsoft has made powerful IDEs for its languages. And the open source Eclipse can be used for Java. Along these lines, Ducasse offers his book. It teaches Smalltalk using the Squeak IDE.

The twist is that Squeak uses the visual metaphors of robots and robot factory, to convey the crucial concepts of objects/classes. As Ducasse explains, Squeak can be directed at an audience that is perhaps of high school age or even younger. So a clear visual feedback between example code and what the student sees then happen is vital, given her limited background and possibly limited attention span.

Squeak uses Smalltalk in part because that is a very minimalist language. If you come from C++, Java or C#, you may be struck by its simplicity, compared to the oodles of classes and notational intricacies of those languages. Which of course also makes it easier for a young student to learn Smalltalk or Squeak itself.

I wonder a little about the book itself, though. A motivated high school student could easily use it. But for some younger students? In that situation, it may well be that the book could be best directed at a teacher, who can then instruct from it.

I whole-heartedly recommend this book for introducing the novice to the nature of computing. I am giving a copy to my 14 year old grandson to introduce him to the fascinating world of programming. He lives 500 km away from me, so he will largely be on his own. I do not expect this to be a problem because the book is perfect for self study.

I want my grandson to learn the essence of computing without spending time on things that he will have to unlearn later or that prove to be blind alleys on his road to computer proficiency . This book is ideal for this purpose. It will let him experience the basic notions of computing in carefully graded steps. Each step tells him how to do fun experiments in the provided environment where he directs a robot/turtle to draw interesting patterns on the screen. The 22 steps take him from a simple sequence of commands to the creation of elaborate simulations; ending at the point where my grandson should start creating his own classes and subclasses.

The experiments are all done in Squeak, a dialect of Smalltalk. It could be argued that my grandson had better learn Java or some other mainstream language. I believe Smalltalk is a better choice because it is simpler, cleaner, and more immediate. The basic concepts are universal and my grandson can easily switch to some other language after he has mastered the fundamentals.

The book is written in a fluent, idiomatic English. It is written in the first person; the writer speaks directly to the reader. This writing style combined with the examples being concrete makes for the smooth communication of what are really abstract ideas.

Anybody wanting to understand more than e-mail and text processing could not do better than to install the free robotic environment on their computer and work through the book’s text and examples.

I've used this book and the BotsInc environment to show my 12-yr old daughter how much fun writing software can be and it's been a wild success!

In fact, it all fits together so well that I'm planning to use it as the basis of an introductory series of classes on software writing as craftwork, to be offered through a local craft organization.

Help train the next generation of software writers! Buy this book!

This book actually teaching computer programming, rather than teaching a computer programming language. It has to use something, and Smalltalk (Squeak) is gentle enough that it doesn't get in the way of the topic.

Stéphane Ducasse, a prolific writer about object-oriented programming, says in his preface: "The material for this book was originally developed by my wife, who is a physics and mathematics teacher in a French school where the students are between eleven and fifteen years old". Indeed, the pains taken to make object-oriented programming understandable to someone with no background are quite apparent, and they certainly pay off. The author has more than met his goal "to teach you object-oriented programming, because this paradigm provides an excellent metaphor for teaching programming".

Instead of teaching Smalltalk, the computer language he uses, he's actually teaching programming. Smalltalk, originally designed as a teaching language, has minimal syntatic issues and it very simple once the student knows a few basic rules. The reader of this book doesn't have to know much to start workign though, since the author distributes a working Squeak environment that's ready to use. He's already provided a "Bot factory" and a working (virtual) robot to which the reader can send commands, much like the LOGO language and its turtle. Without getting caught in the details of object or class design, the readers start out simply by interacting with objects and sending them messages to control their behavior.

As the reader learns more about what the robot knows how to do, the author devises trickier problems for the reader to solve. These usually involve causing the robot to move in such a way as to draw out a pattern. In doing so, the reader is actually writing programs that control the robots behavior to accomplish the goal. Although the language is really SmallTalk, the author effectively hides most of that through the use of the robot's little language.

The Squeak environment the author distributes is easy to use for anyone with a basic idea of computers (i.e. mouse and keyboard, click here, and so on). It's easy to install because you only need to download it and click on the file. From there, you see the Squeak environment and a ready-to-use robot. Move the mouse near the robot and a speech bubble with a blinking cursor appears. Type a command and the robot responds. Easy peasy.

If you are already a computer programmer, or have some experience with computer programming and want to learn Smalltalk, this book is probably too basic for you. However, if you go to the authors web page (Amazon tends to edit links from reviews, so google the author's name) you'll find links to many free Smalltalk books that you can download as PDFs.

then get this one. I learned enough about the reasons for using it and also how to configure it to authenticate against an LDAP server.

Well worth getting and keeping on your shelf.

Squid: The Definitive Guide by Duane Wessels is a great book for someone with aspirations of setting up and getting the most out of Squid. It is lengthy at just over 400 pages, but that is to be expected and desired in O'Reilly's "The Definitive Guide" series. One point worth mentioning is that Duane Wessels (the author, for those with short synaptic cycles) is the one who started Squid and still works on it today. Each chapter builds nicely on subsequent chapters, so there isn't any skipping around. If you're just looking to set it and forget it, this book is probably not for you. Otherwise, read on.

The first three chapters are pretty basic: history of Squid, downloading then installing. For those with no concern of going through downloading and installing, there is a nice section describing each configure switch and, while weighing in at a healthy 48 options, it may be helpful to have this as a reference.

Chapter Four, Configuration Guide For the Eager, is an often desired, but often left out chapter in technical books. By just reading chapters one through four, it is possible to have a fully functional setup of Squid, albeit not very secure or ready for the pounding of the masses. You will, however, begin to understand how Squid operates. This chapter discusses the most often used settings, such as: minimum/maximum size of cached objects, log files and ACLs to restrict addresses, etc.

Chapter Five, Running Squid, covers what you expect. It includes such topics as, boot scripts, chrooting and rotating log files. Again, basic stuff, but necessary for the sake of completeness.

Chapter Six, All About Access Controls, covers one of Squid's major powers and attractions, access controls. ACLs give the administrator extremely fine-grained tuning. Some of the choice highlights for limiting access to addresses/domains include, but not limited to: filter by subnet, MAC, IP address or administrator assigned group. Furthermore, regular expressions can be used to filter URLs or URIs. A most likely seldom used, but very cool, feature is the ability to filter by BGP AS (Border Gateway Protocol Autonomous System) numbers. HTTP request methods such as POST, PUT, DELETE, etc. can also be filtered. Filtering by time or restricting access by user name is also supported. Each topic is assiduously explained and leaves little to be desired.

Chapters Seven and Eight cover disk caching with chapter Seven being basic material and then Eight covering more advanced topics. Discussions on object pruning, size limits, cache replacement policies and many other cache optimizations are covered in these chapters and are necessary to thoroughly understand if you are situated in a relatively large environment or just want to squeeze every bit of performance from your Squid.

Chapter Nine, Interception Caching, covers transparent proxying. This chapter discusses the benefits (no need to configure clients) and drawbacks (cannot do user authentication) of implementing such a system. It then goes on to discuss how to configure Alteon/Nortel, Foundry, Extreme Networks, Arrowpoint, iptables, pf and ipfw to perform the routing to the Squid box.

Chapter ten, Talking to other Squids

Scalability is another favorable attribute of Squid. Running in parallel with previous chapters, this chapter details the advantages (load balancing and increasing your cache hits) and the disadvantages (security problems with having to trust neighboring Squids) of a caching hierarchy. In addition, it explains how to configure connect timeouts and other tweaks to keep Squids aware of when their siblings are down.

Chapter eleven, Redirectors, covers another great attribute of Squid. Redirectors can be used, among other possibilities, to remove advertisements in web pages or rewrite client requests based on their given URL or URI. This chapter details how they work, from a protocol level, and provides example configuration settings such as sending only specific users through the redirector or conversely, letting specific users bypass the redirector altogether.

Squid can be configured to use various user authentication methods to allow or deny access. Chapter Twelve, Authentication Helpers, covers these options. Squid can talk HTTP Basic, HTTP Digest and NTLM. Each type is well explained in how it works and detailed in how to setup.

Chapter Thirteen and Fourteen fully explain logging and monitoring. The logging chapter explains the type of information each log file catches, a full description of each error or information type (which is a great reference that I made full use of) and configuration directives that change what is logged or how it is logged. Monitoring Squid covers the Squid Cache Manger (A web front-end to many great statistics), a brief mention of using Squid-RRD and using SNMP. Such monitoring statistics include, file descriptor allocation, byte hit ratios, cache hits and cache misses and a wealth of other useful information.

Chapter Fifteen, Server Accelerator Mode, explains Server Accelerator Mode, which is also known as Surrogate Mode. It is a neat trick where Squid stills runs as a proxy, however, the Squid server is proxying the world (or a select few) to your server. One obvious advantage includes performance (or Slashdot hardening if you will). There are several config directives explained here as well as some gotchas.

Chapter Sixteen, Debugging, is the is one of the few chapters that I did not need to reference. Although, if you need to, there is some good information provided.

Appendix A comes with a config file reference that actually provides more information then the comments in the configuration file (Holy moley!...they better trademark that idea before other authors catch on!).

Appendix B briefly covers memory caching and optimization.

Appendix C shows how to use delay pools to limit user bandwidth.

Appendix D details file system performance benchmarks to show you filesystem and operating system differences.

Appendix E discusses running Squid on Windows using Cygwin.

Appendix F covers auto configuration of Squid clients to avoid needing to physically visit the many machines you administer.

In conclusion:

Pros: This is "The Book" for Squid. No skipping from chapter to chapter, the author was also the designer and still one of the maintainers, fuller descriptions of the configuration file directives that the configuration file comments. It is a great reference.

Cons: Really the only thing that I didn't like was that he only discussed HTTP proxying. There is a brief mention of FTP and SMTP, but only a couple of sentences. To be fair, in the preface he did mention that he would would of liked to written on these topics but didn't have time.

For the new comer I recommend to buy this book if your finding an alternative for Microsoft box like ISA or MSProxy 2.0.

Squid is robost and a very stable Proxy Server, you can use it even in Entreprise consumption..trust me I use it since 2001.

If your looking for technical books or documents about Squid, this is the one your looking for...

Back in 1998 when I was running my own ISP, Squid was a lifesaver because it allowed me to provide excellent web response to customers over a very modest upstream connection.

When I moved on to consulting Squid was the answer to a wide variety of client problems from employee Internet access control (Redirectors) to company website performance (Server Accelerator Mode) to plain old web page load times (Proxy Cache).

Now that I've moved in-house in a large corporation (30,000+ employees) and I've found out what commercial vendors are charging for their solutions to each of these problems, I have gladly used my knowledge of Squid to save us money.

Of course, that knowledge was not easily won, at least not for me. Because Squid was an open source project there was a lot of information available on the Web, but, of course, because Squid was an open source project, it was hard to find a definitive answer to my particular problem without asking a lot of dumb questions on newsgroups or making a lot of trial and error attempts tweaking compile time options, system changes and configuration file settings.

I have waited for this book for a long time.

I was concerned that it might be too detailed to be readable. Thankfully, Duane Wessels, the primary architect of Squid , has laid out this book to provide simple access at the Macro level. The chapter arrangement and organization are very intuitive. And yet the book still contains enough information to satisfy almost every question.

The one caveat I would make to a reader is to maintain situational awareness while delving into a chapter because, without noticing it, you can suddenly be confronted with pages and pages of configuration file details. There's no avoiding it, when a book says `Definitive Guide' on the cover you expect to have full coverage. It's just that the book is so lucidly written that the transition from high-level discussions to detailed facts might catch you un-aware.

And, really, it's that kind of feeling that lets you know that you're reading a very valuable text. I spent the first hour after I got this book skimming each chapter, happy at each additional topic I discovered. Then I went back and asked it the two hardest questions I have faced using Squid over the past year, in each case the answer was easily found and fully explained (Mr. Wessels deserves an award for making transparent proxying understandable).

The wait for this book was well worth it. I highly recommend it to any person working with, or thinking about working with, Squid.

This guide will pay for itself many times over. If you are considering a caching server for home, office or business you need this book.

My previous experience with proxies was MS proxy server 2.0 and I was a little apprehensive of this project; not to worry. Forty six pages into the book, squid was running; total time invested including installation of the program was about 2 hrs.

Another two hours of reading and precious few changes to config files and my log files are rotating, all ports I need exposed are open and the rest are hidden. I have already been able to tune squid to accelerate delivery of content using *only* this book as a guide. I haven't even had to look at the online documentation for squid (the first time I ever recall that happening).

Not only is my internet connection now available to all users, but also every one is browsing faster than they were before on single dedicated dial ups.

I can't say enough good things about the book or the program. In 14 years of networking I have seen the good, the bad and the ugly. This is one of those rare guides whose author is extremely knowlegable and the material presentation is flawless. I have a large computer science library and in my experience, it doesn't get any better than this.

Bravo Mr. Wessels!

In my view, this book is an excellent introduction to the Struts 2 framework. The authors approach to the reader is well thought out and the book is actually a "good read". The conversational tone with which the book was written lends itself tremendously to the reader grasping a firm hold of the technical information. It's not "dumbed" down at all, it's just explained very well. Each chapter builds on previous information presented to provide a clear picture of how the framework operates.

According to the authors, there is foundational knowledge that must be understood before Struts 2 can really become a useful tool in a developers hands. (See chapter 4: Adding workflow with interceptors.)

They do an outstanding job of taking the reader though the key concepts of the frameworks architecture. At the end of each chapter, I understood what they were saying and I had a clear idea of the concepts they were attempting to get across. Not many technical books do this very well, however, this one does.

As far as Struts 2 being the "best" framework? I won't go there. However, Struts 2 looks to be more than capable of handling the requirements when developing both simple and complex web applications. It appears there have been lessons learned from Struts 1.

In summary, it is the opinion of this reader that if you want to learn and *understand* the Struts 2 framework this book will get your there and you will enjoy the journey as well.

This is a proper "In Action" book. I do strongly recommend it. If you plan to buy only one reference in the subject, look no further this is it! Down Brown is a Struts PMC member and an authoritative voice, among others he is the author of the Struts 2 REST plugin which is a superb addition to the framework from version 2.1.2

The book is very well written and easy to follow. I personally found the explanations very concise and appreciated the most their unique and clear way of breaking down and explaining all code snippets. This is really a great reference.

The first two chapters are a very good introduction to the framework. I am a pure version 2 user and had to learn most of these concepts from online documentation and from the Struts mailing lists.

Among all the topics covered I enjoyed and appreciated the most the coverage of:
- Interceptors
- OGNL and Type Conversion
- Validation! before this book, you could only find the relevant coverage of this topic scattered online in e.g. WebWork articles outdated
..for Struts 2. The authors did an excellent job explaining validation in chapter 10
- Really unique was the coverage of:
..... Unit testing actions
..... Tiles plugin
..... execAndWait interceptor "processing your request, please wait .."
..... UI component templates
..... Writing Struts 2 plugins

On the big plus side, the authors did a superb job keeping the book agnostic to minor versions of Struts 2 i.e. there were several differences from 2.0.x to 2.1.x and I was very happy to see that the examples and explanations were not outdated for the later.

On the down side and as a trade off I can only complain that the book left the Ajax topics out; maybe also because there have been many changes on this topic from minor versions of Struts 2 e.g. the ajax theme of Struts 2.0.x was converted to the dojo plugin in version 2.1.x. In any case, I somehow find the Ajax topic in Struts 2 to be one of the best documented online.

I believe that the Practical Apache Struts 2 Web 2.0 Projects (Practical Projects) book from Ian Roughley is a very good complement to this one. If you want to find coverage on topics like Security and Ajax in Struts 2 you will want that one too. The only issue there is that the coverage of the ajax theme is partially outdated for the newest version 2.1.2 of the framework

Struts 2 In Action is the best resource (hard or soft copy) for Struts 2 available. I took a look at this book as someone with quite a bit of experience using Struts and Struts 2. I really thought I had a good understanding of the core framework before, but many of the topics that lack online documentation were covered in more depth than I had seen in the past. As an example, many others have shied away from covering OGNL because it is a language all by itself. In this book you will find what I consider to be the most thorough explanation of how OGNL fits into Struts 2 and how to use it yourself. I was tempted to give the book 4 stars because there are a few things that I thought could have gotten more coverage, like Spring/Hibernate integration and AJAX, but I realized that it really would be impossible to cover everything in one volume. Struts 2 is a large and comprehensive framework and with anything of that scale, a good understanding of the fundamentals is the best way to start. This book delivers.

If you are wondering what is covered, you will find comprehensive coverage of the following -
- writing actions
- action workflow basics
- type conversion
- OGNL
- form tags
- non-form tags
- results
- intro to Spring/Hibernate integration
- validation
- i18n
- struts 2 plugins
- migration from struts 1

I had to learn Struts2 quickly since I recently changed jobs and my new team has several web application projects built using Struts2.

Overall, I thought the book was done very well if you are looking for a good introduction to Struts2. The first 8 chapters are very good.

The main negative is the source code for the book's examples. The authors provide one very large war file with all the source code embedded into the war file along with an overall web application divided into sub-applications for each chapter.

This packaging of the source code into the war file made it difficult for me to create individual projects in my development IDE that demonstrated just the material in a specific chapter. I had to spend quite a bit of time breaking down the source code into individual web projects and then figuring out on my own what jars needed to go into each project, what the struts.xml file needed to have, and what ever else was necessary to separate out just that chapter's sub-application so I could run that example and play with it.

Where this really became a problem was in chapters 9 and 10. Chapter 9 is a very advanced introduction to integrating Spring and Hibernate/JPA into Struts2. I never could get this chapter's example to work correctly.

However, chapter 10 on the validation framework then uses the same code as chapter 9, so you really cannot separate out the code for either chapter 9 and 10.

The validation framework is likely something even beginning Struts2 developers will want to use, while Spring/JPA/Hibernate is for more advanced developers and should have been well after the chapter on how to use the validation framework.

Also, the authors really don't give you a good understanding of what Struts2 jars you need to have to build a basic Struts2 application. There is some information about this in chapter 13 (setting up your IDE) but this information should really be at the beginning of the book. Also I don't think the list the authors provide is accurate since my basic HelloWorld (get the user to enter a name, call an Action class, and then display Hello userName in new jsp) worked with far fewer jars. Note there is apparently a new example war that just is a basic Hello World so there may be some information in that war file. That war was not on the manning web site when I purchased the book.

This book is good but be prepared to struggle working with the code examples if you want to work on the examples in your own development environment.

I recommend the authors create separate complete war files for each chapter's example to make it easier for users to just get that chapter's example code into their development IDE.

Lastly, the book does get 4 stars because the author's explanations of the basics of Struts2 (chapters 1-8) is very easy to follow for experienced Java developers. I'm now ready to tackle the Struts2 applications in my new job.

I took a chance and pre-ordered this book because I have recently started a Struts2 project and wanted to learn more about the framework. The book did not disappoint.

The authors explained the concepts behind the framework clearly and used examples that were immediately useful. The book is a little too short and in many cases a few more details would have been appreciated but it seemed to be a deliberate decision to leave out some of the less common use cases to avoid cluttering up the book. Thus, this book is ideal if you are new to Struts 2 but have some prior experience with Java web development.

I like the fact that an entire chapter was dedicated to integrating Spring and Hibernate into the framework. It brings all the bits and pieces from the online documentation together in a cohesive and comprehensive package.

Chapters were also dedicated to validation, internationalization, best practices and migration from Struts classic. The authors spent several chapters on how the Value Stack and the ActionContext worked and how OGNL fits into this framework.

All in all there is enough information in this book to start and to produce a complete Struts 2 application.

This book is excellent. It is very thorough and easy to understand. There is sample code in every chapter so the concepts are very clear.

I have been using subfiles in RPGIV for many years - this book taught me some new tricks I wasn't aware of!

This is THE subfile book for AS/400 RPG programmers.

Mr. Vandever approaches the subject with a sense of humor, lots of examples, and excellent technique. The examples are written in ILE RPG IV (RPG III programmers will find the book useful, as well), and do a nice job of showing off recent RPG IV enhancements by incorporating them in the examples.

I have developed lots of subfile programs, and read the other books on the subject. This is by far the best treatment of the subject that I have seen.

As a programmer new to RPG 4 and programming for the AS/400, I needed help with subfiles. This book proved easy to read (I can't say I've read it through, but enough to get what I needed) and there are lots of helpful code examples. I used the sample program for a page-at-time subfile application almost verbatim to get started on one of my programs, which saved a considerable amount of time and effort. Overall this book has been quite useful for me.

Book really explains subfiles in terms anyone can understand. The CD/ROM has sample code that you can use immediately as "models" to develop your own programs. Author does an excellent job of explaining how subfiles work. But if you are like me, you will develop several subfile "skeleton" programs for your own future use. That's where the examples can really help...

The best book you can ever get in General surgery. If you really want to enjoy surgery while you are reading, get Greenfield's. The sub specialty sections are awesome as well, you don't have to look elsewhere when you get this book.

i found this book the best surgical book covering
basic scince,general surgucal and subspescility topics including
anatomy,pathophysiology of surgical dieases and managment in details.

I came across this book back in early 2002, and since my best friend had the Sabiston and we were on a budget, i bought this one. This is deffinetly the best and the most complete book i could have bought on general surgery. It takes you from anatomy trough physiology in each pathology you read upon. Would recomend it to anybody, either finishing medschool, or starting your residency in General Surgery.

i'd rate in terms of comprehensibility &modern thinking greenfield>sabiston>schwartz

I happened to pass through this most wounderful book by mistake, but when I read through it,Ii felt really sorry for not depending on it as an additional but essential referrence during my college and postgraduate years, the chapters are well organized and deeply written easily read, the illustrations are very clear and informative, although I might suggest a second more expanded chapter on infections being one of the most serious sergical enemies infections. ..I really want to thank the editors and contributors for the enormous effort they have put here and all the knowledge I found in this great book.

This is by far the best SAS book I own (and I have a whole shelf full). I have made use of it repeatedly. The examples are excellent. This is definitely a methods book, not a theory book, but the presentation of the statistical concepts is clear and easy to follow and apply.

If you have data that fit the general category "time to event," and are not suitably analyzed by repeated measures ANOVA, you are probably looking at doing a survival analysis (also known by several other names). If you are working largely on your own, and you learn best by doing, you cannot--as far as I know--do better than Allison's book. Of course it all but locks you into using SAS for analyses, but his explanations of proportional hazards and other models are the best I've found among a dozen textbooks and stats package manuals (some of which made sense only after reading Allison). What makes this book so good is that it will have you running your analyses in just hours. The examples are superb take-off points. I was not a SAS user before reading the book and therefore took a little extra time to figure out dataset manipulations and such in SAS, but that was minor effort compared to the rewards of having Allison's clearly written book as a guide. The price of this book represents only a fraction of its value.

This book is well-written, well-organized, and very practical. I found it invaluable in conducting my research. My only recommendation for the author for his next edition is to include a chapter on dealing with correlated event times, like time-to-promotion and time-to-quiting in his policemen example (pg 249).

I've used a number of this author's books and they all share in common lucidity, utility, and rigor. This book makes it easy to grasp complex ideas, provides comprehensible examples, gives sample SAS code so that implementing the methods is as straightforward as possible. Plus, it is clear that the author is a subtle and first-rate methodologist, who innovates in this area as well as teaches it.

So far, this book has been a useful reference for survival analysis. It is clearly written and the xplanatins are understandable and helpful. It would be nice to have a newer edition that addresses changes in later versions of SAS.

The teach your self visually books are fantastic for easy learning, I have the excel and access books, and they are both great.
Thanks to the book creator!.

One of the newest and brightest features of Microsoft 2007 which includes Excel 2007, is the addition of The Ribbon, which replaces toolbars and menus in previous editions. This is quite complex and not very user friendly, but when you learn it, it can be great! If you struggled with old menu bars, you will definitely struggle with the New Ribbon.

The series of Visual Books has been quite popular, mainly because anything as dry as instructional material is greatly enhanced by pictures. The colorful graphics that define the category of work you want are bright, amusing, informative and large. An example is for the section: protect a password shows a big yellow book with a key lock; or change data color shows paint cans and one color spills onto a worksheet. The computer illiterate can "get the picture" even if you don't know what the book refers to.

However, my grief comes with too many big pictures and not enough pictures of the screen. A most important element is viewing the screen, but each pic of the computer screen is way too small. But you do have explicit instructions in the sidebars.

My question remains, why couldn't the writer incorporate larger-size views of the computer screen. This is so needed, because of the elaborate menu bar...or ribbon as it is called in Excel 2007.

Other than that, one point is the Database section has been advanced from the 2003. This element of the software eliminates the need for ACCESS 2007, which is much more advanced. So, if you don't want to explore the challenging ACCESS, you can simply use the Database function on Excel. This works great for smaller projects.

Overall, this is one of the best books for learning excel. Graphic and text are well spread out, it is user friendly, colorful and includes a ton of help.......Rizzo

This book is more than the five star rating. Visually Excel learning the only right way to go. The book is excellently done too.

I use this book everyday, easy to understand, easy to use. My spread sheets look just as good if not better than those in my work place that do this everyday. I am just slower, but who would know.

For those of us who lack computer savvy, a book like this is an essential. Personally I learn much better if I can read text AND look at a picture. Never really having done a spread sheet before, I learned in no time at all. I keep the book right by my computer. I have found all the 'Visually' books to be helpful

For anyone who has grappled with the question of why technology hasn't lived up to its promise in schools, this book is a must-read. Pfaum's observations are fresh and candid, and he examines the question of the "technology fix" of schools without an axe to grind or pre-formed conclusions. This very readable book will ring true to those who have spent time in classrooms and have wondered why technology has not had a greater impact on improving student achievement.

This is a wise and thought-full book. Unlike many books about technology in education that are often too theoretical, too empirical, too uninformed, or too polemical, this book is anchored in real classrooms. Rather than starting with a breathless vision of the future or a cranky rant about the imagined glories of the past, Bill Pflaum begins with what is happening in classrooms right now. He gathers his data first hand - not from surveys, focus groups, or aggregated data but from a year-long personal journey through classrooms all across the country. His careful, thoughtful (and often entertaining) observations are neither completely unexpected, nor completely predictable - instead they explode with authenticity. From such a solid foundation, both personal and universal, he reflects carefully on what is working and what is not working - and offers thoughtful suggestions for a better future that is both reachable, and worth reaching. I liked reading this book.

This book is a must read for decision makers at every level.

Data rules in the age of standards. This is the only book that I have read that discusses educational technology with a genuinely human voice. Pflaum takes a refreshing welcome approach to the task of thoughtfully examining the use of technology in America's schools. Instead of recycling mountains of data from research studies, he visited classrooms across the country and talked to students, teachers, principals, and technology co-coordinators who are on the frontline of the problem.

For educators, like myself, who deal daily with the problems and the blessings of technology in the schools, the book is raw opportunity to view the problem outside of the boundaries of their state and local district.

Pflaum ends his book with some clear, realistic guides for future directions, but the real value of the book is in its rich, constantly thought-provoking portrayal of things as they are now.

Computers have been a part of our schools for about two decades now. Many people believe that computers are the solution to the problems of American education; however, it is pretty clear that they have not been the magic bullet many thought they'd be. The questions then arises: why? Why haven't computers fulfilled the promise they seemed to have in their early days?

In The Technology Fix, William Pflaum tries to answer the question. Taking a sabbatical, he travels the country and visits a number of schools, trying to get a sense of the impact computers are actually having. This book is mainly a report of the visits he made and the different ways he sees computers being used (or, more than likely, not being used) in the classroom. He then gives some of his interpretations of what this means and suggestions for how technology might be used better.

What impact this book has it has through its observations on what is actually happening in schools. As a consultant for schools on technology, I have seen many of the same things Mr. Pflaum has: computers sitting unused, resources managed inappropriately, focus on computer bells and whistles over curriculum content, etc. I agree whole-heartedly that computers have yet to fulfill their promise and I find Mr. Pflaum's categorization of implementation on the basis of commitment and focus to be very revealing. On the other hand, despite the depression I feel sometimes after visiting a school where technology, if it is being used at all, is being used poorly, I maintain my belief that technology is the future and we can use it more effectively. Mr. Pflaum seems more pessimistic.

Within his descriptions of what he's seen in schools, Mr. Pflaum has some useful insights; however, when he tries to build these into universals at the end of the book, he is less powerful. Not that his suggestions are necessarily lacking merit. Instead, some are so obvious as to not be worth the effort of a book-length study. Use computers for assessment? I would think so. Use computers to align standards, instruction and assessment? Of course. Coordinate computer skills across grade levels? I hope so.

This is not to say that schools are actually doing these things. Many aren't. But he's pointing towards obvious best practices here that just need to be implemented. His one controversial suggestion--that computers be target towards those that can use them most as opposed to spreading the wealth equally--is practical but also a sign of his pessimism. We aren't committed enough to do what we should so we should at least do what we can.

In his book, Mr. Pflaum has provided valuable insights into what is actually going on in schools today per their use of technology. This alone makes the book valuable. Though his suggestions for improvement are a bit short-sighted, they have their place and could open the eyes of some administrators and teachers. Still, his bleak view clouds the possible bright future and growing impact technology could have if we are willing to have commitment and focus. I hope readers won't let his attitude bring them down.

Too many books are either all for technology in schools or completely against it. Neither kind of book is very useful for teachers who are trying to figure out how to use technology intelligently in their classrooms.

This author takes a walk through 20 or so schools, and describes what he observes with the insight of a seasoned educator. He does a very good job of spotlighting the intelligent uses of technology, and an equally good job of uncovering the dreary, wasteful uses. I found the book is a wonderful way to hone my own thinking.

Moreover, the book is a fast read, and very engaging. Pflaum writes with an uncommon honesty and humanness, and he has that wonderful ability to draw pictures in your mind. I'd recommend it to both teachers and parents who have input in the way schools are run.

This is a well written book, code is easy to download, and a number of topics. All in all though, the writing is clear and easily understood so it's well worth the money...

I am a Java web/search programmer who wanted to "get into" text mining. I found this book an excellent resource for this. Text Mining is a field in which active research is still going on, and other Text Mining books I have looked at reflect this - the authors expect you to have a certain degree of mathematical background to understand what they are saying. This book explains briefly the math behind each of the approaches, but it focuses more on the algorithms that result from the math, so it is easier to read.

Of course, a side effect of this is that the approaches described are not necessarily the state of the art for solving any given problem, but once you get the basic approach to solving a problem, it is relatively easy to find and understand the documentation on the web for the more advanced approaches, since you now know what you are looking for and how it differs from your basic solution.

The book does have a (fairly long) chapter where it covers the math background necessary to get started with Text Mining. If you understand the stuff in there, you will actually be able to think up solutions to text mining problems that are unique to your own situation.

The algorithms in the book are in pseudo-code, but the book comes with a CD (or download from the author's sourceforge project textmine.sf.net) where you can see working Perl code.

Overall, I think this is one of the most useful books that I have purchased in a while. It should appeal most to programmer types who have programmed in their language(s) of choice for a while in areas other than text mining, wants to get into text mining, and doesn't want to spend a lot of time relearning high school and college math before starting off.

Text mining is one of the most exciting subjects of the web, and too few books are dealing with it. This one is one of them, and it gives quite a few examples of text mining applications, like spam filters or search engine ranking algorithms. The style is easy to follow, and the concepts easy to understand given some maths background.

However, I expected more details, and a richer content overall, thus the four stars. This is still a good book.

Software developers learn how to mine information on the Web and turn it into valuable data; but developers need to understand how data mining works. For a programmer's application-oriented review, Text Mining Application Programming is the item of choice: it reviews text data, how it's found, and how search engines locate and gather it. Next, it teaches how to build spiders to crawl the Web, how to use the information, and how to monitoring it. Perl developers will find its Perl-based code useful, but it's not necessary to know Perl to run the software herein. An excellent guide to mining the Net.

There is an old expression that half of knowing anything is knowing where to find it. And there is little more frustrating to be looking at 'My Computer' trying to find what you know you have stored in a file somewhere. Well, perhaps just as frustrating is to go to one of the search engines and try to find something that you know is there but just don't know the proper words to find it.

In this book Dr. Konchady talks about how to go find data that is in text form on your system, on your network or out on the web somewhere. It talks about search engines, but also about other techniques that can be used only by programming.

The CD that comes with the book contains several Perl software snippets that help to find named entities, parts of speech, phrases and gives a summary of text documents. This area includes developing web crawlers that can be adapted by individual users to go out and find specialized information. It further contains an Open Source software package called Text Mine that is designed for mining operations. In addition it has utilities to build and enhance Text Mine and utilities to build and manage MySQL database tables. This is an excellent book on everything from the basic hints and types through some of the mathematics that underlies text mining.

His section on the nature of an English language Question and Answer system is the best I've ever seen.