Software Books

The book was very good with the best history of JavaScript (server and client-side) I have ever read. However, nobody in the professional world will start a project today in SSJS, the language is extinct. Only legacy web applications will be using this and there are so many better server-side languages available now.

Have been using code from this book with great success, extending the functionality of SSJS objects (SuperFile, SuperMail)--until now (SuperClient). SuperClient can't seem to see the [client] object in an iPlanet WebServer 4.1 environment. So, digging around in vendor supplied documentation for that version, we find [customClient]. The description of this [customClient] object is very similar to [SuperClient]. Now, while merging the functionality of the two, the book continues to be a wonderful asset.

iPlanet Web Server, Enterprise Edition Server-Side JavaScript Guide (v4.1)* March 2000 (p140 ff) Creating a Custom [client] Object

EXTRACT: Properties of the predefined [client] object can have only string values. To extend the [client] object with a custom object include the following line at the beginning of pages that require it: [var customClient = getCustomClient();] If this is NOT the first page that requests the object you get an existing object, otherwise a new one is created.

I have been using and referring this book to development teams for the past year. An excellent tutorial and reference point for people exposing the power of Server-side JavaScript.

I have scanned this book, and true to what the other reviewers have said, this book looks excellent. I like that SSJS seems to separate the business stuff from the presentation stuff (HTML) unlike ColdFusion and ASP's. How many people are using SSJS?

If any one wanted to learn good SSJS programming techniques, this is the best buy. Authors not only have real stuff but they explained in a much better way than anyother about SSJS concepts with wonderful, real life examples. Ofcourse, you shoud know about javascript fundamentals (core javascript) before you read this book and authors are very specific about the content of the book and their target is only for users of SSJS

I purchased the Bible for handout at the local prison. I, myself, do not speak or read Spanish but those who received the Bibles were happy with them. It allows them to join in with the Bible study.

Spanish Bible: Reina-Valera

Extremely useful for comparing meaning from another language.

It was perfect. One of my co-workers mentioned she'd like a spanish bible and was soo please when she received it. I'm so glad I was able to find it so easily and inexpensively.

This is an awesome Bible! I sent it to an inmate in jail and he was so happy! Now he is able to participate in Bible studies and Church. What a blessing!

Read the Bible everyday for incredible heroes (JESUS, SAMSON, MOSES, KING DAVID), incredible miracles (parting of the Red Sea, creation of the earth, the resurrection) and powerful testimonies (from the disciples, Lazarus, those who were once blind). Start off with the PSALMS and PROVERBS, then go to the New Testament and finally the Old Testament. GOD BLESS YOU!!!

This is a great general resource for learning to use and program Director MX. I beleive the title is misleading, however, because it is not the only book you will ever need and because it is not just about using Director MX, it is about programming with Lingo as well.

Two things I like about this book are the coverage of Multiuser programming and networking. One thing I did not like that much was the slim coverage of 3D programming; nevertheless, for a general Director book, it is great and pretty easy to understand and follow.

The book covers all the software functions and almost all the lingo functions exists.
The code sources are good and clear, and the language the book written is clear to read and understand for none English native.

Thanks for this book!

I hope adobe will not kill director...

This is a great book on your way to understanding Director. Its a well designed and not too hard to follow book.

This is a great reference book - the author says it is not really meant to be read all the way through and it is described as not for beginners, but I think any Director user except perhaps the most advanced could benefit from this book either as a reference or complete read or both. I especially like all of the side notes scattered throughout the book, plus the troubleshooting and Did You Know? sections at the end of each chapter. His descriptions of some components of Lingo were the first I've read that I really understood. He also includes 7 bonus chapters and a Lingo reference on the CD! This book is packed with info, and even though it is now one version of Director behind the current one, I still recommend having it on your reference shelf. If you really use Director for either work or play, you won't regret it!

I really don't have to get into detail. This is the book you want to have when you need something to go back on and read. This is the 1st book that helped me the most i only used 4 books but this one was the one that made me go back and read up again and me as a person that hates to read, I learn a ton of stuff from this very book. I'm telling you right now no one here can tell you all the details this one book has but if you pick it up and read it you will see for your self that this book is worth more then it cost. He even has a mixure of games inside the cd its crazy. This book chills in my back pack when i need some lingo codes and which im back in director for the 3d field im just useing it to bring back the old codes which this book holds. All i can tell you is that this is a great book for director and perhaps one of the best i have encounter you won't regrate it trust me on that.

It is one of the best books on SQL I have read. This is a good book not only for those who want to use SQL Anywhere but for all SQL Afficianodos. It is both comprehensive and compact. I found this book useful while trying to understand Mobilink. I recommend this book without any hesitation to anyone who wants to understand how everything works in SQL Anywhere.

In a word: Awesome! This is the definitive book on Sybase SQL Anywhere 9. If you use this at work, especially in a replicated environment, then you MUST have this on your shelf.

This is a down-to-earth, no-holds barred approach to dealing with the good/bad/indifferent aspects of SQL Anywhere Studio 9. I am a data architect for a company that manages over 4,600 remote databases and this book has single-handedly helped me solve issues we have been having for months.

The author, Breck Carter, is a man who has been in the trenches with "the rest of us" to solve some of the most vexing data management problems. The solutions are as simple as they are elegant.

Written in a "real-world" tone, this book gets to the nitty-gritty of 99% of problems. The chapter on Mobilink replication is worth the price of the book alone as it goes into extreme detail on the how/whens/whys of moving data around and how to best utilize this impressive feature.

Highly Recommend!

Some of the documentation in this book is included no were else besides Sybase official docs. Given that "official docs" have such a dry reputation, I was happy to find this book. Indeed it is much easier to read, and contains lots of important information for configuring and programming in your SQL environment.

This book is packed with pertinant, in-depth info. The author does not have an overly-wordy style, so there is no inflated page-count.

This book is simply a must-to-have for db-developers; it presents a complete and compact reference for experienced developers as well as it offers a comprehensive immersion in SQL Anywhere to beginners and less experienced ones.

If I had to use only one word to express my opinion about this book I would just say: RELIEF. Relief of not getting drowned again in hundred of pages of irrelevant topics, misleading information, decorative pictures and tools descriptions.

I highly recommend this book to application programmers, as myself, accustomed to flirting with different db-engines but still seeking a solid understanding relational db paradigms.

I started using Sybase SQL Anywhere before Sybase owned it--when it was called The "Watcom" Database Engine. "SQL Anywhere Studio 9 Developer's Guide" is an outstanding reference. The book was written by someone who obviously has a great deal of experience using SQL Anywhere Studio to build real-world software solutions. Highly recommended.

While some passages are repetitive, on the whole, this book is very informative. The author leaves nothing to chance and is thorough in his explanation of various methods and how to reproduce them. The explanations by example are flushed out with no assumptions made about user knowledge, which was great in my case because before reading this book, all I knew about SAS is that it existed. Now, I can apply various and powerful statistical techniques on my own. Thanks Prof. Hatcher!

More detailed explanation of every subject discussed. Nothing was assummed. The appendix include vital information for new SAS users.

This is the single best statistics text I've ever read. It's extremely easy to follow, very practical, and gives outstanding examples. Everything is so clearly described in the book that one might call it Factor analysis and SEM for Dummies. I only wish that the book covered nonrecursive SEM models.

Very easy to read. Examples are simple and effective. The book explains the statistical concepts as well as the SAS programming tricks. In fact, the book provides complete code - you will be able to get good amount of analysis done just by copying that code. However, you also need to buy the "The Little SAS Book" if you never used SAS before.

This outstanding book was one of the mainstays for my Ph.D. dissertation. It explain factor analysis and SEM techniques in a clear and effective way, with an hands-on approach that guides the reader during all the data analysis and result interpretation phases.

When this book was written software testing was starting to consolidate into an 'honorable' profession, and the number of good books about testing could be counted on your fingers (and probably a few toes). The discipline has matured into a profession, and there are so many excellent books on the subject now that it boggles my mind.

You'd think that the top ten challenges listed in this book would have been long ago resolved and replaced with a new set. Sadly, that isn't the case. Each challenge listed is as valid today as it was when this book was written, and except for #10 on the list (getting trained in testing), which has dramatically improved, the other nine are still there. Read the book. Take the advice of the two authors, both of whom are seasoned professionals who give the solutions to these challenges, and move the profession forward.

Here are the top five challenges that I see today, drawn from the list in the book:

#1 today, #6 in the book: Communicating with Customers -- And Users
#2 today, #3 in the book: Hitting a Moving Target
#3 today, #1 in the book: Having to Say No
#4 today, #4 in the book: Testing What's Thrown Over the Wall
#5 today, #2 in the book: Fighting a Lose-Lose Situation

Your order may be different, but I am willing to bet that the list will be the same. This book does give realistic solutions to these problems, so if you agree with the list, then you'll find this book valuable.

Testing has often been the misbegotten portion of the software development process. Frequently neglected until the semi-chaotic end of the production cycle, the testing phase has traditionally been shortened to accommodate a fixed release date. The relationships between the developer and test groups are to some extent adversarial, but in so many cases it often breaks down into open hostility. Among developers, it is often considered demeaning to have to soil ones hands by actually testing the code. With such a sullied background, it is no wonder that production code is generally riddled with bugs.
As the authors of this book point out, all of the above are dangerous conditions. With the expansion of code reuse and RAD tools, the development of the initial iteration is going to be done at a faster pace than before. Since the number of pathways through the code is operationally infinite, the only way relatively bug-free code will be developed is by allocating more resources to testing and making the choice and tracking of test cases a more scientific endeavor. The most significant point of the ten made in this book is that the testing process should be considered on an equal basis with that of development so that both groups communicate as equals. Without that, all the fancy, efficient tools in the world are reduced to the level of mere toys.
This is a book that can and should be read by developers, managers and yes, even testers, as all will benefit from the simple words of wisdom.

This book gives excellent insight for the beginning QA professional. It not so detailed that developers and managers will not want anything to do with it either. It explains ways to communicate quality assurance without offending anyone. The content is concentrated on the expressing QA in a brighter light without ruffling too many feathers. I recommend it for everyone in a technical environment with the goal of attaining quality. THIS IS A MUST HAVE FOR ANY QA PROFESSIONAL.

Much has changed in software development and testing practices since this text was written in the late 90's. However, many of the identified challenges are still with us. I find myself rereading this book as it is a useful reference for a test manager. The authors identify dual disparate roles for the software tester. In role one, the focus is on the task of testing software, such as test planning, test design, and execution. In role two, the tester or test manager's role is more as a politician and marketer to protect the test staff and promote the value they bring to each project . The text focuses on the second role, which elaborates on what the authors identify as the top ten people oriented challenges for the software test professional.

The first section of the book includes an assessment to help you identify your strengths and weaknesses in meeting people related testing challenges. The bulk of the text contains individual chapters on the top 10 challenges. The challenges are explained along with guidelines to overcome the challenge. Chapters can be read out of order and this format allows you to focus on your weaknesses as identified in the self assessment. The last section of the book describes a six step change process to implement improvements. My favorite two chapters were "Explaining Testing to Managers" and "Getting Trained in Testing." Highly recommended.

This is an excellent review of the biggest recurring problems of the software testing world. As I read the descriptions of each of the 10 challenges, I was astonished at how many of the pitfalls I fall into on a regular basis. Perry & Rice don't just lay out what the challenges are - they also discuss how to meet each one. Each item on the list has its own chapter with sections on the impact on testing, solutions to the challenge, impediments to implementing the solutions, and helpful guidelines to creating a plan of action. This is without a doubt an excellent book for those of us in the trenches of software testing each day. (One bit of advice, though - if you're looking for a book on "how to do software testing", look elsewhere. Perry and Rice have other good books on the subject, but this one is really intended to help you step back from your daily testing work and see where you could improve on your approach to it.)

I used this book to prepare for the basic exam and passed it first try with a score of about 85%. Its a tough, quite abstract exam but I think a very good one and this book would have been all I needed to pass. The sample exam in the book is a very good indication of where your level needs to be. The certification guide also deepened my knowledge of UML considerably - which I have been using off and on over the past 8 years.
The book is perhaps a little too terse and very dense and thats the only reason I didnt give it 5 stars as a preparation resource.
I'm going to use it to prepare for the intermediate exam too...

Good book to have for UML Certification...I wish every UML evangalist must have for reference.

Really complete book, clear and concise. It's a very good tool to pass both of the exams, as well it's a great resource for those who want to initiate and work with UML.

This is a good book for preparing to the OMG UML exam. Each one of the most important elements of the UML metamodel are treated with a simplified view.

The sample exam of the end is so useful. I recommend the book.

Before buying this book, I had no doubt that it would be instrumental in passing my certification exams. I did pass the the Fundamental exam in the first try itself and I don't believe I would've been able to do so if I had not laid hands on this material. Neither do I think there's a book out there that covers UML with the level of detail as this one does. After all, this guide is published by the same Group that sets the UML standards and administers the certification program! I'll be referring back to it again for my Intermediate-level exam. Thanks OMG!

I own the first and second editions of this book. I keep a copy at home, and one at work. It is comprehensive guide to the UNIX operating system. I always look here first for any questions or help I need with UNIX. I would recommend this book for anyone that uses UNIX.

The Bible of Unix. The one (and final) book you need in UNIX. Your search ends with this book. Well defined examples, explanations, notations. Be it a beginner, intermediate or expert you SHOULD have this book, if you are a Unix user.

Finally, a Unix book that is so comprehensive!

Had to give this one four stars, though, instead of five. The chapter on Tcl/Tk and Expect (chapter 20) is loaded with errors - probably editorial in nature (lots of places where parentheses are used instead of brackets "{}" and these WILL cause errors if you try to run the commands.). Otherwise, this is a fine book for learning Unix or going beyond the beginner level. The authors not only know their stuff, but they communicate it well. Highly recommended!

I bought the original version of this book in 1991-1992. It's still the best UNIX "How-to" book on the market. Absolutely no other book in my "UNIX library" provides more useful information on such a wide variety of topics: shells, networking, user environment configuration, mail, etc., etc., etc. It's all in here. It's especially great for beginners, since it covers all of the basics that normally provide stumbling blocks for beginning UNIX users. I highly recommend it.

As someone with a background in the comparatively 'easier' (and more stable) Mac world, I found this book, more than any other Windows 98 guidebooks, to be the most useful in terms of explaining why my Wintel product was failing. The book is exceptionally well-designed. Not only is the materially organized in a useful fashion, the page-layout makes things easy to read. The author's writing style is crisp and engaging, and that which he is trying to teach is genuinely useful. Indeed, _Using the Windows 98 Registry_ is so straightforward in its approach, I felt like I was reading a tech manual for a Macintosh product. I would second another reviewers' comments, though, that future editions could benefit from the inclusion of case studies.

I purchased the book to understand how Windows 98 registry really works. I had sometimes to correct corrupt registry entries arising from my heavy user actions and this may be very scary.

Hunneycutt's book was the right choice. This is a book written by an expert with high pedagogic skills. I found not only the whys of registry but a number of tips that helped resolving my issues. Reading this book felt me more in control of the machine.

Also useful are some of the freeware and shareware described in the book, like regmon. To be frank, however, I didn't find much use for the featured software that come with the book's CD.

The book offered a lot more than my immediate needs requested. For instance, as a programmer I found it may be a powerful reference tool for those needing to write code accessing the registry.

As a hint for the next edition I suggest increasing anedotical contents for troubleshooting application entries and other heavy user issues.

This book has tons of useful information and goes into detail in the areas where you need it to. Lots of good desktop edits, good CD, and very easy to read & follow.

This book is excellent for understanding the "theory" of the Win 98 registry, but I have not found it very useful for guidance in the practical aspects of actually tweaking registry settings. It usually contains enough information about a particular registry section to know if it is not worth editing, but it often does not give enough coverage to important keys. It would definitely benefit a lot from input by a person who commonly solves problems using the registry. That said, I have sometimes found it helpful when trying to find which key contains a given piece of info that I am interested in tweaking.

This book is one of the best written registry books that I have read. It explains all the hard to find details that most other books barely touch on. It's the only registry book that I recommend!

BUt why do VB when c# is just as easy and you can write unmanaged within it. Its just a no brainer with all the limitations of VB still.

Visual Basic experts Lars Powers and Mike Snell effective collaborate in the Visual Basic Programmer's Guide to the .NET Framework Class Library to instruct intermediat to advanced level users on a full range of issues including: delineating and define the pieces of .NET; explaining how/why .NET was conceived and what this means to VB6/Windows DNA developers; how to execute Windows programming using the .NET namespaces; position the .NET namespaces within the context of the reader's project; how to make architecture decisions when using .NET namespaces; as well as details about the construction of Web Services and how they programmatically communicate with each other. Visual Basic Programmer's Guide to the .NET Framework Class Library is enhanced further with call-outs and highlighted sections will illustrate concepts by relating previous VB6/Windows DNA best practices with the new .NET approach. 1152 pages. User Level: Intermediate-Advanced. Highly Recommended.

I found this book to be a handy 2nd book to have on .NET programming... it doesn't have much content to help you make the transition to .NET (I'd have to recommend Gary Cornell's Programming VB .NET: A Guide for Experienced Programmers for that task), but it does do a great job of helping you find the right class libraries and write code with them once you are up and running with your language of choice.

Each chapter is focused on a namespace. The authors then spend a few pages bringing people up to speed on the spotlight technology (I am new to XML and particularly liked the intro to XML piece). Then they dive right into the details of using the .NET classes to achieve your desired end-result. The class library that ships with .NET is huge, and I found it helpful to use this book as a guide to highlight the classes I should worry about to get 80-90% of my programming work done.

Now for the cons: the sample applications could have been a bit more in-depth, and I really think they should have spent the time to make the book "bi-lingual" by providing some C# code as well - but overall, a great addition to your .NET bookshelf.

The challenge for a reference book like this is to be better the documentation that Microsoft provide - MSDN and the .Net framework SDK. My experience is that this book certainly achieves that.

For example, today I needed to show the "save file" dialog and then write the contents of a text box to a text file. I know how to do that in VB6, but I hadn't done it in VB.Net before. I searched MSDN which gave me accurate descriptions of the menthods and properties of at least four classes for writing data to files, but I still had no idea which one(s) I needed to use.

I am sure the sample code I needed is somewhere in MSDN, but I hadn't found it after 20 minutes searching when I gave up and referred to this book. In five minutes I had found what I was after, my code worked and I was able to get on with my next task. That is what this book is for. If you want to learn about the new programming features in VB.Net (like polymorphism, delegates etc) this is not your book. But if you want help getting your .Net program to talk to anything (files, printers, active directory, browsers, TCP/IP Sockets, XML/XSLT or whatever) This book will be a valuable resource.

Just note that while this book covers ASP.Net and ADO.Net, if you work with these a lot you might want more depth than is provided here. I will be considering the Wrox "ASP.Net Namespace Reference" when it is released.

Because of a project, I needed to finally make the jump from VB6 to VB.NET. After reviewig several books, I grabbed the book by Powers and Snell. It helped tremendously on the key pieces of my project. What I really like are the numerous code examples - worth the price of the book alone! I even contacted the authors to get their thoughts on something and ask a few questions. Not only did they reply with great answers, but their indepth knowledge of .NET helped finalize an important part of my project architecture. Looking forward to more titles by Powers and Snell. Thanks again guys!