Software Books

This book was a big help in passing my TCP/IP exam, but I do not recomend it as a single source. My strategy, which has served me well, is to read the book once, take a practice test (eg Transender), figure out what concepts you do not get, study those areas of the book, take practice exam, repeat untill you are scoring high on the practice exams. This book work out great for that and it is cheap and a quick read. Perfect.

Only get this book if you're already experienced in the TCP/IP world. Passed the test with flying colors! I used this book to review beforehand. Wished it had a little more practice questions, but overall good material!

This is a great book. Even if you're not interested in takingthe test, this book is worth the price. It seems to cover almosteverything on the test. Buy the book if you want to take the test.

It is a very good book. It is not a thick book, but it contains many materials relevant to the exam, and you can get the main points from this book. I would say its content is even better than other training guide in the market. Of course, it is just a revision book, you cannot get any training from it, just get the facts only. In addition, I also find that its content is even same as the live questions that can help me pass the exam.

If you already know TCP/IP this book will help you slam-dunk the test! Its explanation on subnetting is the best I've seen. If you're new to WINS, DHCP and DNS then you better try another book. New Riders Training Guide on TCP/IP (ISBN 1562059203) is great- know this book and you know TCP/IP on NT! I studied both of these and scored a 966.

The information in the book is clear, easy to understand, and worth reading. The formatting of the text, the fonts used, and the overall style of the book is lacking. The end of the book was actually a few mm shorter than the spine on my copy, but nothing was cut off, so it doesn't matter beyond looking a little odd.

I would buy it again, even if the previous version is available for free online. It's great to read when you're not near a computer, as (for a programmer) the book is easy enough to follow without needing to try every example yourself.

One of the best programing language books I have read. If only the programing guides for other languages could be this clear and concise.

Good examples, suggestions, and notes. Is a must have for any one looking to program in Lua.

Naming this language after the moon is ironically apropos, as many of its lunatic creator's cognitive processes seem to randomly scramble themselves according to the phase of said moon. I'm no language designer myself, but if I were trying to come up with a high-level scripting language that would appeal directly to C programmers, the last thing I'd want to do is start array indices at 1 rather than 0. Sure, you have the option of altering this behavior in the constructor, but in the author's own words:

"I do not recommend the use of arrays starting at 0 in Lua. Most built-in functions assume that arrays start at index 1, and therefore they will not handle such arrays correctly."

Talk about giving you just enough rope to hang yourself. But it gets even better. Array elements in Lua are to be removed by assigning their indices the value of nil. This is all well and good, but, again in the author's own words:

"Lua uses [the nil] value as a sentinel to find the end of the array. When the array has holes--nil elements inside it--the length operator may assume any of these nil elements as the end marker. Of course, this unpredictability is hardly what you want."

No shoot, Sherlock. So why not get rid of that unpredictability? As I read further I came to the conclusion that this decision was made because doing otherwise would spoil the running theme of the language. Another favorite passage comes from page 32 when discussing the numeric for loop:

"you should never change the value of the control variable: the effect of such changes is unpredictable."

Great! I love unpredictable results. They make so much more sense than raising a predictable exception or pointing out a predictable old syntax error. Let's see now... How else can we anger C programmers? How about if we make it so "a break or return statement can appear only as the last statement of a block"? Wonderful! Now let's get rid of one of the primary attractions of high-level scripting languages--regular expressions--and say we can't include them due to size concerns (we really need to be able to brag about our entire distribution fitting on a single floppy disk, and the PCRE library is just HUGE).

These things are marginally less obnoxious than Python's significant whitespace, but still obnoxious, and apart from the multiple return values thing, I really didn't find any compelling reason to join the Lua fanboy camp in this volume. Maybe if I were a Warcraft player I'd feel differently.

As for the book itself, the writing is terse and very obviously coming from a non-native speaker. The typesetting is atrocious (good typography is one of those things you never really appreciate until it's gone) and the entire thing looks like it was printed on an old laser printer that was low on toner at Kinko's. If it were cheaper, I wouldn't care, but it's not, so I do.

Stick to the free PDF if you really have to learn Lua for something. The changes in 5.1 are not significant enough to warrant a second edition, and the flimsy, smudged paper is really not worth paying for.

Buying this book does more than support the Lua project. Having the book available will change your opinion of integrating script with C code! "Progamming in Lua" is a well-written text that makes using Lua practical. All of the best features of Lua are covered; the sample code is concise, clear and complete.

Lua is very different from C, and so allows a programmer to easily do things that are difficult in C. That makes it a perfect companion language. The only obstacle is training a C programmer to use it! That's where the book becomes useful. It's a quick read and covers all the essentials.

Even better, Lua is so well-connected to C that it is easy to switch back and forth in the course of a typical programming day, writing performance code in C and high-level logic in Lua. It is even possible to easily interact with Lua data structures in C without writing Lua code for situations where the data structures are desirable but Lua code isn't required. If you're looking for a scripting language for your next project, you need to know about Lua, and this book is the quickest way to make an informed decision.

Excellent high-lvel book for anyone involved with software development and implementation. This book digs deep with enough details of security in coding and testing practices and how to avoid security related bugs and vulnerabilities. The book also does well in terms of secure coding, white box and black box testing very well.

Few things where this book falls short "Ignorant" to emerging application landscape and the coding complexities in a multi-platform and application integration environment - J2EE, .NET, XML Web Services and SOA. I am sure, the author will agree on those gaps hopefully we see in the next edition of this book.

The book deserves 5 stars for the concepts + illustrations and 3 stars for those keen on development details for distributed applications.

A required reading for anyone involved with software development and implementation. This book drills-down to security in coding and testing practices and how to avoid security related bugs and vulnerabilities. The concepts illustrated on secure coding, white box and black box testing are excellent. As a developer/architect, I thoroughly enjoyed this book and I suggest to everyone who wants to get started on secure coding and testing practices.

Couple of things I QUIBBLE with are... the book does'nt realize the emerging issues and how-to's for build/refactor security for distributed application proliferation as your it - Portals, Web Services and SOA. The way we develop software is changing, the applications are becoming more pervasive and no-longer contained standalone to a system which makes the built-in security brittle impeding the agile business requirements for application/process orchestration, b2b federation and Web based application mashups. I am sure, the author will realize those gaps in the next edition of this book.

Havingsaid - This book is still a must-read for the budding security developer who wants to focus on secure programming and testing.

What is MISSING - You will not find answers for how you do secure web-centric applications, XML Web services - message-level security, identity federation and other b2b application complexities.

Software Security is the best book for learning to integrate security throughout your software development lifecycle. It contains all the security material that is missing from software engineering books. The author understands that your software development lifecycle is different from his, and so focuses on seven touchpoints that can be introduced into any software development lifecycle, instead of attempting to sell you a new lifecycle. He also understands that no matter how important security is to you, you can't change everything about you develop software tomorrow, so he introduces the touchpoints in order of effectiveness based on his extensive consulting experience, starting with tool-assisted code reviews and architectural risk analysis.

If you're a software developer, Software Security is an essential book to have on your shelf, and you'll also want a secure programming book like Secure Programming with Static Analysis (Addison-Wesley Software Security Series) or the author's own Building Secure Software: How to Avoid Security Problems the Right Way.

The root cause of many security vulnerabilities is poorly written software. Often, software applications are written without security in mind. The logical, yet elusive, solution is to ensure that software developers are trained in writing secure code.

Software Security: Building Security In is a valiant attempt to show software developers how to do just that. The book is the latest step in Gary McGraw's software security series, whose previous titles include Building Secure Software and Exploiting Software.

In past decades, writing secure code was left to the military and banking industry. Today, with everything on networks, all sectors must get into the act.

Much of the problem is that organizations target their security elsewhere--specifically on networks--rather than on software. But so many malicious attacks are directed at software that it is foolish to leave this vulnerability exposed.

McGraw goes into detail not only about writing secure code but also about key related areas, which he terms "the seven touchpoints of software security."

These points comprise code review, architectural risk analysis, penetration testing, risk-based security tests, abuse cases, security requirements, and security operations. A major portion of the book effectively discusses these "touchpoints," making the work a recommended tool for inculcating software developers with a security mind-set.

I read six books on software security recently, namely "Writing Secure Code, 2nd Ed" by Michael Howard and David LeBlanc; "19 Deadly Sins of Software Security" by Michael Howard, David LeBlanc, and John Viega; "Software Security" by Gary McGraw; "The Security Development Lifecycle" by Michael Howard and Steve Lipner; "High-Assurance Design" by Cliff Berg; and "Security Patterns" by Markus Schumacher, et al. Each book takes a different approach to the software security problem, although the first two focus on coding bugs and flaws; the second two examine development processes; and the last two discuss practices or patterns for improved design and implementation. My favorite of the six is Gary McGraw's, thanks to his clear thinking and logical analysis. The other five are still noteworthy books. All six will contribute to the production of more security software.

Gary McGraw's book gets my vote as the best of the six because it made the biggest impact on the way I look at the software security problem. First, Gary emphasizes the differences between bugs (coding errors) and flaws (deeper architectural problems). He shows that automated code inspection tools can be applied more or less successfully to the first problem set, but human investigation is required to address the second. Gary applauds the diversity of backgrounds found in today's security professionals, but wonders what will happen when this rag-tag bunch (myself included) is eventually replaced by "formally" trained college security graduates.

Second, Gary explains that although tools cannot replace a flaw-finding human, they can assist programmers trying to avoid writing bugs. Gary is the only author I encountered who acknowledged that it is unrealistic to expect a programmer to keep dozens or hundreds of sound coding practices and historical vulnerabilities in his head while writing software. An automated tool is a powerful way to apply secure coding lessons in a repeatable and measurable manner. Gary also reframed the way I look at software penetration testing, by showing in ch 6 that they are best used to discover environmental and configuration problems of software in production.

Third, Gary is not afraid to point out the problems with other interpretations of the software security problem. I almost fell out of my chair when I read his critique on pp 140-7 and p 213 of Microsoft's improper use of terms like "threat" in their so-called "threat model." Gary is absolutely right to say Microsoft is performing "risk analysis," not "threat analysis." (I laughed when I read him describe Microsoft's "Threat Modeling" as "[t]he unfortunately titled book" on p 310.) I examine this issue deeper in my reviews of Microsoft's books. Gary is also correct when he states on p 153 that "security is more like insurance than it is some kind of investment." I bookmarked the section (pp 292, 296-7) where Gary explained how the "19 Deadly Sins of Software Security" mix "specific types of errors and vulnerability classes and talk about them all at the same level of abstraction." He's also right that the OWASP Top Ten suffers the same problem. Finally, Gary understands the relationships between operators and developers and the importance of security vocabulary.

I was pleasantly surprised by "Software Security". I reviewed an early draft for Addison-Wesley and wondered where the author was taking this book. It ended up being my favorite software security book, easily complementing Gary's earlier book "Building Secure Software." In my opinion, Gary is thinking properly about all the fundamental issues that matter. This book should be distributed to all Microsoft developers to help them frame the software security problem properly.

Word cannot begin to say how insightful this author is. And still speaking to us many years after his death.

Once again Andrew Murray gives excellent counsel for spiritual growth. Every believer needs help along the way and Absolute Surrender is a great tool to use as a springboard. The message is meaty and to be taken in with the intent of life transformation! As Jesus lived His life in absolute surrender to Father God, so must we, and this book points the way!

THIS IS THE MOST WONDERFUL BOOK I HAVE EVER FOUND OTHER THAN Andrew Murray,THE POWER OF Intercession. I suggest the whole world would Understand the Bible A whole lot clearer if they just read Andrew Murray Books. What A wonderful Evnagelist he was.

This book was truly insightful and should be used as a tool to assist all who strives to improve their Christian walk.

Right up there near Brother Lawrence's "The Practice of the Presence of God" (free online at the Practice Gods Presence web site) are the wonderful works of Andrew Murray. "Absolute Surrender" is a classic in every sense.

These gifted children of God have a way of restating, enlivening, and magnifying the very words of Our Lord and do greatly glorify Our Father.

Jesus christ, i can't think of how many times i've referred to this book over the years, and i don't think i've even covered 1/3rd of the material. If you're a self-taught access programmer, you can only get so much from google searches and developers' forums. If you want to learn new concepts in depth and generate ideas for how to be a more effective programmer, i can't think of anything more helpful than reading this book one chapter at a time. For example, I wanted to learn about ADO, so I read the chapter on ADO. Without any specific goals, I read the chapter about forms and learned to substantially increase the user-friendliness of my forms. In general, this has made me a better "modular" program, and I think in terms of re-usable functions rather than task-by-task code.

Getz' writing style is remarkably lucid, and there's an example in writing and on CD for just about every concept he teaches.

i bought the paperback version and now that the binding has come apart i keep the book in about five or six different places. i also broke the straps on both of my south american backpacks trying to carry this book (each volume is about 1500 pages long...) If you're going to be programming Access for a while, i'd recommend getting a hardcover edition.

If you need to know anything about access 2002 this book has it! i use it all the time

What do I mean by the "gold standard?" As a professional Access developer, I use a lot of reference materials. Besides the Internet, my bookshelf is full of Acces, SQL Server, VBA, T-SQL, and Office reference books. But there is one publication that I always check first when I'm perplexed or curious. It's my gold standard if you will allow me that hyperbole. I'm speaking of the Access 2002 Developer's Handbook, published by Sybex.

Versions of the Access Developer's Handbook have been a staple of professional Access developers since the early days of the Microsoft Access product. My first attempt at serious Access development was during the days of version 1.1. Was that 1993? My team and I recognized the importance and power of this new Windows database product and started to build marketing applications using Access and macros(!) in Windows for Workgroups 3.11. I discovered a copy of the Access 2.0 Developer's Handbook as we migrated to Access v2 and I never looked back. I could not believe the wealth of information in that single volume. I didn't understand much of it, but that was the beauty of it. Here was a reference that revealed secrets and held promises of knowledge to be gained for the inspired reader. Incarnations of this book have remained at my right hand since the first day I opened it.

Whether you need to know more about tables, queries, forms, reports, collections, SQL, relational design, Jet security, multi-user issues, networked databases, or whatever, the Access 2002 Developer's Handbook is the reference for you. It's currently published in two volumes, Desktop and Enterprise editions. Buy both as a set. Combined, they are the gold standard of Microsoft Access reference materials.

Without question, the finest books available on Access database programming. I've purchased (and held onto) each edition since 95. I really cannot express in words my enthusiasm for this series. They aren't traditional 'learner' or traditional reference books, but they meet both needs -- read them once and refer back to them for years. Full of code samples that drop easily into your applications. If you work with Access on a regular basis, you REALLY, REALLY NEED TO HAVE the Access Developer's Handbook set.

If you are just a beginer you might find parts of the Developer's Handbook set difficult to understand, but as you enhance your skillsets you will find these to be a must have. For a serious Access Developer these books are a definitely a must have. I've written in-house applications for years since Access 2.0. Now, I'm writing commercial applications using Access 2002 and the Developer's Handbook set has been a tremendous resource. It covers things you just have to know if you are going to create serious and dependable software applications using Access. Plus, the files that come on the CD's come with code samples you can really make use of. Of all the people I've read of in the Access Industry, these guys are masters of Access. I'd listen to anything they have to say. They know their stuff, big time.

I looked high and low, and this has to be the best option for developing an LDAP or ADSI component in C++. Find this out of print book and buy it instead of buying another book that is still in print.

Really awesome AD programming book. Covers all the basics of AD and ADSI and then dives into the LDAP API which all other authors try to avoid and dont cover well. You do not need any other AD programming books if you have this one.

Very good book, extensively covers LDAP programming
unlike others.

I've struggled with using LDAP and this explains it all with code samples, which for the likes of makes it easy to learn and best of all Copy and Paste

Really awesome AD programming book. Covers all the basics of AD and ADSI and then dives into the LDAP API which all other authors try to avoid and dont cover well. You do not need any other AD programming books if you have this one.

Dos ultimos livros que tenho comprado, assim como os da serie Head First da O'Really este livro superou muito as minhas espectativas.

Como um livro de tutorial foi maravilhoso e me trouxe muito conteudo !!!

Realmente vale a pena !!!

It's an excellent book, the book teaches you how to develop a site in three layers (presentation, business and data) in my ishe goal of this book.

It is cover a lot of great part of asp.net 2.0. It is easy to understand and implement. Some code is very profession and hard to understand. Most of them cover SQL,ASP,WEB service,security issue.I will say it is the cool part of ASP.net. You can see author spend a lot of time to collect the beauty of asp.net. You will like it no matter how many time you read the book.

'Beginning ASP .NET 2.0 E-Commerce in C# 2005: From Novice to Professional' by Cristian Darie and Karli Watson is one of the most unique and important books out there for anyone that is developing an E-Commerce site with ASP.NET 2.0. Starting from scratch, the authors step by step show you how to get a site running and WORKING well and efficient. Packed with 650+ pages of material, the authors break the steps down in logical parts, show how they go about the work to be done, and then provide the code which does the dirty work. Not only is it helpful, but it's a joy to follow the steps as so much of the curtain is pulled away to show the developer how to get the job done. This is easily one of my favorite Apress books that I have seen. One of the nicest things about the Apress line of books is the fact that they write and publish books that no one else seems to and this is a perfect example of this. I'll close with a chapter overview for your inspection:

01. Starting off
02. Laying Out the Foundation
03. Creating the Product Catalog: Part I
04. Creating the Product Catalog: Part II
05. Searching the Catalog
06. Improving Performance
07. Receiving Payments Using PayPal
08. Catalog Administration
09. Creating a Custom Shopping Cart
10. Custom Orders
11. Making Product Recommendations
12. Adding Customer Accounts
13. Advanced Customer Orders
14. Order Pipeline
15. Implementing the Pipeline
16. Credit Card Transactions
17. Integrating with Amazon

Tack on 2 appendixes to the end and you have a MUST-HAVE book for anyone that is looking to achieve the same goals that this books does!!

***** HIGHLY RECOMMENDED

This book covers it's topic E-Commerce very well. It also takes advantage of the new features found in ASP.Net 2.0 including some of the new ADO features. If you are getting ready to setup an E-Commerce site I highly recommend this book. I also recommend it for beginning developers wanting to know more about ADO and database design.
The authors have a great approach to design that anyone doing E-Commerce would do well to follow. Better yet they mention the pros and cons of different approaches and explain why they chose their approach. I've been thrilled to learn some new strategies to improve performance that I hadn't considered before as well as some new features in ASP.Net and ADO 2.0 that I wasn't aware of.
The only negative, for me, is the database as well as ADO basics this book spends many pages covering. However there's plenty of worthwhile content to justify the price. So if you are familiar with database design and have a working knowledge of ADO you can just skip past those pages. I do recommend you skim thru them though as, like me, you may learn some new 2.0 features you weren't aware of.
The book covered all my E-Commerce questions: catalog design, how to scale up/performance considerations, SSL, Security issues, credit card processing, and costs involved. They even point you in the direction of a few recommended credit card processing businesses. Best of all they approach the site creation in such a way you can quickly get up and going and then later on focus on fine tuning payment options and really making the site standout with features.

My three-year old grandson loved the book. The story is good and the art is exceptional.

As an artist I tip my hat to William Joyce! I read in an earlier review someone saying it is done in simple watercolor but thats not watercolor unless its watercolor pencils. Such meticulous detailed work even as George ventures down the railing of the stairs he passes a depiction of "Sunday afternoon on the Island of Le Grande Jatte"! This book is a prize the story line is so cute the text is perfect for age 2-6 and the adventure and art are unforgettable. No wonder PBS made it into a show!

I loved this book. It was so cute. I thoughtit was good for every one. It was about a kid who wonders about how it would be if he was shrunken and when he was sleeping he actully shrunk. But he had to do some chores and they were the simplest things like watering the plants or feeding the goldfish turn into the biggest adventure.

I gave this book a five because a little kid name George has a dream of him being small like a "teddy bear". When he had the dream he was in his bed sleeping, his mom left a note of chores and he was doing the chores. The "scary" part in the book was when the cat sees George and thinks his is a toy and the cat tries to put his claw on him ,but George runs and hides from the cat. This book is great and I think William took a long time doing the cover and pictures and I say the book cover and pictures are really beautiful. I love this book because he had a dream that was weird that he was small and that he had to do big chores. I would recommend this book because it is a cute book for a 1st and 2nd graders I think they will love it because all of the cute pictures and the funny pictures they would love to read this book a lot of times and I would like to some day read it again because it would be so nice to read it over and over.

I love this book and give it over and over to all the children that I care most about

If I could get someone to write down everything I don't know about LotusScript and Java, it would fill a book. Well, this is that book.

Hatter and Banks aren't wordy and target this book strictly at the experienced developer looking for a reference work. That makes this incredibly useful. These days I carry this book (thankfully light despite being 700 pages) between sites all the time. The lovely posters from Lotus might list all the properties and methods, but these guys provide the details underneath it.

The remarks on each class are pertinent, yet brief (as for NotesRichTextItem, "you must call the save method of the parent Notes document to save the data to disk") They include examples not only for classes, but also occasionally for methods and properties.

Interestingly, a quick check of the index for 'Index, databases' found only a reference to the updateFTIndex method for Java Database class and not to the LotusScript NotesDatabase class, while 'Registering Users' listed the LotusScript page and not the Java one. Perhaps the editors need to work on that. Fortunately, they provide a lot of cross-references on the pages, giving you page numbers for the classes mentioned in the text, reducing the need to refer to the table of contents or the index.

The print's small, but they use fonts, abbreviations and familiar symbols to get the message across clearly.

On balance, it's well worth the (money) I paid Amazon for it - it probably saved me an hour today and none of our hours come cheap, do they?

I bought this book originally expecting a full reference to Lotus and at first was a little dissappointed that it only covered LotusScript and Java. After reading it, now it is the only reference I use for LotusScript. I too have several other books, but none give the information and detaill in an easy to read format like this book. Anything you want to know about Classes, Methods, Properties, Events, and new R5 LotusScript features are covered in this book in detail with good examples. I also like how each class has it's own contents page giving page numbers for all of the assosiated Properties, Methods, and Events for QUICK reference.

This book has minimized my LotusScript related headaches! It is a one-stop resource for methods and properties for the predefined LotusScript Classes. It is hard to believe, but ()it takes me less time to write scripts, which gives me more time to enjoy the finer things in life. I would highly recommend this book to anyone, beginner or advanced.

The authors did a great job providing examples of how the properties and methods are used. I haven't written any Java yet, but when I do this book will be right by my side!

If you are new to LotusScript do not buy this book. This is a reference book for LotusScript and Java classes and a very good one at that. The developer help files can be confusing at times and it always helps to have a reference book near you.

If you are an intermediate or experienced Notes developer this is a terrific book, I have it by my desk all the time.

If you want a book to teach you LotusScript but Practical LotusScript it's great!

Exactly what I've been looking for: A no nonsense reference manual for the LotusScript and Java class libraries. Probably the most useful book a professional Notes/Domino developer can have.

FOUND THE GENERAL INFORMATION OF SPECIFIC DISEASES AND ITS POSSIBLE TREATMENTS. VERY GOOD AND PRECISE INFORMATION.

We purchased the Mayo Clinic Eeference guide to serve as a family medical book. We are very pleased with the descriptions and information about comon medical issues. I highly recommend this book for individuals who want more information about common and not so common medical difficulties.

This is a book no household should be without. Very informative and helpfull. The index is great and the information is to the point... Excellent photos and drawings. Only drawback: a bit bulky!

The Mayo Family Health book is a "wealth of information."
My husband recently became ill and was hospitalized. We were able to pinpoint symptoms in the book which helped us along with our health provider get appropriate testing and treatment for his condition.

With healthcare today, we must be "informed consumers".
I have worked nearly 35 years in clinical laboratory medicine and I still learn something new everyday....this book certainly helps.

I like the format of this book. The six sections seem designed to truly make the work user friendly.
They are:
Part I: Living Well II: Common Conditions and Concerns Through Life's Stages III: Making Sense of Your Symptoms
IV: First Aid and Emergency Care VisualGuide: Anatomy and Common Disorders Part V: Diseases and Disorders
VI: Tests and Treatments
The great prayer is that most of what one learns from reading and going through this guide will not have to be useful or relevant.