Software Books

You'd realy be surprised to find out what San Diego has to offer in the way of hiking and trails. This book is your guide for those trails. From a 90 foot Waterfall (Cedar Creek Falls) to many other wonderful hikes. I highly recommend this book if you want to learn more about hiking in San Diego.

This book is the best hiking book I have come across, and I have many. Not only is it well planned out, with attached maps, and hikes separated by areas, but it also grades the level of difficulty very accurately. As for the comment on this book being old and vague on location... well, it's not designed to be an all encompassing guide, and you will have to dust off your map or Map Quest the locations.

We just recently moved to San Diego, and it's been a great source in discovering all the area has to offer, I feel that without it we would have missed out on so much.

My co-worker was telling me about all the wonderful waterfalls and boulders that he saw when he was hiking, and he told me that he learned about the trails from this book. I immediately ordered it, and so far, it has been handy to have.

Each trail is labeled with its difficulty, length, and even the best times to go. The descriptions are very useful and are pretty accurate.

There is an art to describing hikes in a succinct yet useful manner. Like with movie reviews, you don't want to give everything away, but you want to give the reader enough information to decide if the subject matter interests him enough into going to experience it for himself. Jerry Schad is THE master. It is simply amazing how much information he can pack into so few words. Once you do a few of his hikes, and reread his descriptions, you can quickly learn what exactly he means by certain turns of phrase and the like. This is because while English (or any language) is a poor tool for communicating this type of information, it's all we've got when reading a book. But what Schad does is describe practically every worthy hike in San Diego County in a consistent fashion, so you can apply what you learn he means by a certain description for one hike that he uses for another hike.

San Diego County is an amazingly diverse area of natural wonder. To discover it without Jerry's help would be very difficult. I strongly recommend his book for anyone interested in such a discovery.

However, I do recommend that you take several 1-star hikes before going on to a 2-star, and several 2-stars, before a 3-star, etc., primarily to learn how to read and use the book most effectively. Picking up the book and planning a 5-star hike before going through the rest of the process is NOT recommended.

Have fun!

Exhaustively researched, comprehensive, with good descriptions of why you'd want to pick a certain hike, so you'll know what you've got to look forward to.

This may be the only book you'll ever need on the subject, but it's not the only thing to take on a hike: you'll need that most uncommon of things, common sense" -- and that means you'll also need to bring a MAP and water, and the rest of the "Ten Essentials."

Remember, it doesn't replace a USGS or topographic map, let alone good hiking sense. It's "just" a trail guide, albeit the best one the county has had for about 20 years. And frequently and responsibly revised, too. No guidebook, or map, is of much use unless you know how to use it: a little knowledge is a dangerous thing, right?

Don't expect too much. With San Diego's exploding population, your enjoyment of trails can alter seasonally with use, let alone by weather. Schad makes every effort to anticipate your tastes when he describes a trail, when it's best to go, what you'll get most out of a hike. You'll learn how to make your hikes match your tastes the more you use this excellent book. And you'll learn to appreciate, up close and personal, the scenery of the climate you moved here for.

San Diego county has great places to explore, and a wide range of habitats: from coastal to montane, to high & low desert. Most of it makes great scenery, but up close it can be intimidating. Schad's book won't let that stop you.

Most trails, even those in state or county parks, are not well marked except at trail heads (about what you should expect when park budgets are so meager these days).

This book and a topographic map are just the things to reawaken a sense of purpose, and to give our desires a sense of direction. And these, in turn, unlock our sense of beauty and wonder.

San Diego deserves nothing less from its inhabitants, and they and it deserve nothing less than such a resourceful book as this.

As a travelogue, Welcome to the USA is pretty good, Kalpanik certainly made me think about wanting to go to San Diego, Seattle and Nashville.

as a character. Kalpanik seems simultaneously incredibly thoughtful and serious and yet someone who has a carefree attitude towards life, someone who handle life as it happens!

It's a light reading, and yet thoughtful; funny yet serious; conversational yet literary!

This book takes many life concepts expressed in different forms and combine them in a mishmash. He structures the 12 different personal essays, each highlighting a particular transitional period in his life or a specific experience in to a beautiful collage of experiences in this book very successfully. What a funny memoir!

Kalpanik S. is a fine writer with a lot to say about a lot of things and a unique way of making you laugh! I highly recommend her book.

This is the story of a brilliant young man who seems to be always on the move, moving from one interesting city to the other.

At the beginning, the author leaves New Delhi for US, where he is awarded a fellowship to study at University of California, but he gets caught into culture shock, as well as an internal dilemma, seeking a deeper meaning of life. While he is most vulnerable, he manages to fall in love with one his student but is unable to express his feelings.

Then he seems to have gone through the roller coaster ride of the technology industry emerging as a winner, a successful technologist leading a group of innovators.

We end in beautiful San Diego, with a moving story about how the author and his family face the Inferno, the great wildfires of 2007.

I don't believe anyone has experienced living unless they have ventured around like the author has. It is in his narratives, his reaction to the challenges he faces and his observations of people and culture of various places that he truly shines.

It is my top read of the year!

Whether you ever wondered about meaning of it all, or you want to read something light amusing, or want to see places like Seattle, San Diego, and Nashville from the eyes of the writer, or vicariously live the life of a student at University of California, this book is for you!

This book combines elements from good humor, a memoir, a scenic travelogue, a touching love story, science fiction and philosophy.

The author, pretends to be an Artificial Imagination computer program simulating human creativity, describes the life/career journey of a modern nomad through the Hi Tech world of California and Washington (Settle). The book is clever, witty and obviously written by someone very intelligent but still manages to be very down to earth and funny! it's light reading, the author has a conversational style, you feel as if you are reading a letter from a close friend!!

ReKalpanik S. takes us through his arrival in USA as a student and subsequent travel to several places - San Francisco, Seattle, Nashville, and San Diego. In each places, he focuses on similar aspect of his life as a technologist and an immigrant - acceptance by local people, standing out as a ethnic minority and foreign born, life as a technology execuitve and family life. In addition, he covers local food, people, culture and sources of enjoyment, joy, and finally, and his quest for love and balance.


He adds so much meaning, passion and humor, he is so open with the readers that I felt like I was reading a private letter that someone would write only to their best friends.

The writing is refreshingly unexpected, humorous and meaningful. Great read!!

Had never used the product and needed a crash course and this was very helpful at the time.

This is an excellent manuscript for teaching yourself Captivate. Its even helping me review while learning the upgrade.

There arent many books on Captivate. It's too bad, because this software is very common in the education and eLearning field.
I needed to teach myself the software for my job, and this book helped a lot. It is full of practical lessons and examples. Upon completing the book, I had a very good command of the program. I highly recommend this for anyone who wants to learn Captivate.

Well written with excellent instructional design. The best way to learn this powerful software quickly. I couldn't have developed my project without it.

I ordered this a couple weeks ago and just got around to using it two days ago. I wasn't in a hurry because I have viewed the videos about Captivate 2 on Lynda.com and thought this book would just be review--which it isn't. As an educator I should know the difference between just watching something done and actually doing it. In this book you do the exercises--which are clearly explained step-by-step in easy bits! I'm halfway through the book and all I can say is how thankful I am that I ordered this. I've been wanting to create interactive online material for my courses for the past five years. Now, with Captivate 2 and this book I will be able to do it.

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 will give this book George Shrinks 5 stars. I do like this book because it is action pack and it is kind of funny because a boy that small can do all his chores.I do recomend the book to people that have a sense of humor.I think this book is for all ages.

"Mayo Clinic Family Health Book" covers nearly everything that takes place in life from preconception to death. Diagnostic and treatment advice is easy to read and accentuated with diagrams and photos.

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.

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.

I found this book at the local library and kept renewing it because it was so helpful. I have elements 6 (the book is for elements 5) but this is by far the best book on elements photoshop that I have found. I have used it many times on my photos. If you are a beginner with elements like me then you will love this book! In case you are wondering, I have also purchased 3 other elements 6 photoshop books before I purchased this book. The first was 'Photoshop Elements 6 for Dummies', then 'Teach Yourself Visually Adobe Photoshop Elements 6' and last 'Photoshop Elements 6 in easy steps'. Now I can stop!

I love this book. It makes my life easier. What more could you ask for. This was just what i needed.

In one word WOW! You have to have this book, Matt explains things in simple terms and makes using PSE easy to use.

Bill

MATT KLOSKOWSKI DOES AND EXCELLENT JOB. VERY EASY TO FOLLOW! MATT'S HUMOR IS A DELIGHT. THE EXAMPLES MAKE IT EASY TO LEARN.

THE ONLY NEGATIVE IS THE BINDING ON THE BOOK. IT IS OK SO FAR. BUT I USE A BOOK HARD, I AM CAREFUL. BUT MYEXPERIENCE WITH THIS TYPE OF BINDING IS NOT GOOD. THEY SHOULD USE A SPIRAL BINDING.

This is a wonderful book. I have had it now for almost a year and use it constantly. It reads like a recipe book, which makes it extremely user friendly. I use it alone and in conjunction with "Photoshop Elements: The Missing Manual".

This book does for Ruby what Kernighan & Ritchie's "The C Programming Language" did for C. It provides a concise, accessible introduction to the Ruby programming language.

Starting out with a tour of Ruby, you are then taken on a deeper dive into chapters on "Structure and Execution", "Datatypes and Objects", "Expressions and Operators", and "Statements and Control Structures". Some of the real power of Ruby is revealed in chapters on "Methods, Procs, Lambdas, and Closures", "Classes and Modules", and "Reflection and Metaprogramming".

The book closes with chapters on "The Ruby Platform" and "The Ruby Environment". The chapter on the Ruby Platform is like a condensed API guide to Ruby's core library. The chapter on the Ruby Environment will help you navigate through the Ruby interpreter's command-line arguments and environment variables as well as a grab-bag of extra Ruby topics that were not covered earlier in the book.

The book is well organized and easy to read. Each chapter is peppered with code samples. If you are serious about learning Ruby, get this book! It sits on my bookshelf, next to a copy of the Pickaxe book and The Ruby Way. Bonus: each chapter of the book starts with a work of art by why the lucky stiff!

The Ruby Programming Language is my new favorite Ruby book. I personally think it is a better text than the famous "Pickaxe" book. While the Pickaxe has a great class/module reference (it's over half of the book, after all), the actual explanations of how Ruby works in The Ruby Programming Language are clearer and go into much more depth. Most importantly for me, The Ruby Programming Language covers some of the more complicated topics, such as metaprogramming, with MUCH more depth. From the Pickaxe alone I had trouble understanding how some of these Ruby features worked. But with this new book, it's much clearer.

If you want the defacto Ruby book, this is it.

This book is quite simply one of the finest software development books ever written. The style, the length, the scope, and the structure are all absolutely perfect. The balance creates a reading experience that seemingly opens a channel to your brain and feeds the information in.

Flanagan is a master author of technical books, especially languages. His JavaScript book is equally well done. Matsumoto's unique technical mastery here leaves no stone unturned. And even the artwork by "why the lucky stiff" added a fun element that just rounded out the book as the best in its class.

If I could forget the whole thing, just so I could read it again, I would. It is that good.

Really found this to be an excellent guide to the Ruby programming language. This is definitely not just the API rehashed in print.

The difference in the style of this book and some others, in my opinion, is the difference between a map and a travel guide. A map may show you what and where things are, and may even be useful for figuring out how to go between locations, a travel guide will often include maps plus the inside scoop on what is interesting.

This book is similar. The writing style is like having an expert sit down and explain to you the various facets of the language, how to use them, points that are notable, etc. And all of this content is within a reasonable 400 pages.

Highly recommended.

I wish every book about a programming language was written like this one:

First, it is fairly compact and doesn't waste space (and your time) explaining to you what is a byte or a register, like some 800 page "volumes about everything" do. It correctly assumes that the reader is a programmer and explains the language, not the programming.

Second, it covers Ruby in depth. Read this book and you'll easily understand the most craziest Ruby code examples that could be found inside of Rails and other popular libraries. Moreover, I've found a few tricks in the book that I don't believe I saw in the wild.

And finally, author's language is very clean, free of buzzwords and needless repetitions. As always with O'Reilly books, this one is also very neatly structured and makes an excellent reference book.

Buy it.

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.

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.

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 was going to give this book four stars, but I was going to be unfair with it. This is not a guide to create a lean enterprise, it was not meant to be one and I was going to judge it as if it was.

This is a great introduction to the Toyota Production System and lean philosophy, by nobody else but the architect of the system.

It had been a long time since I read such a dense book about any subject. If you are interested in getting started in the Lean methodologies then this book is a must read. If you work in a manufacturing plant or are in management then the insight on this book will be valuable for the rest of your life. I recommend it to my boss along with the Toyota Way because I think we need to start implementing all the techniques and management principles, specially when it comes to Human Resource management and policies, that made the Toyota the world leader it is.

A+.

The book is very good. But I am charged for an additional 10 euros by the mail delivery company for which I was not informed on the website.
So be careful when buying a book from here.

A "must read" for anyone in manufacturing. It is the basis for all modern manufacturing, and for any business process or flow. The author describes the two pillars of the Toyota production system as autonomation and just-in-time. He explaines the six rules associated with the kanban. He also describes the seven wastes and the value of asking "Why" five times. The book is very easy and quick reading, and provides a complete backgroung to the Toyota development and success.

Toyota Production System: Beyond Large-Scale Production
Great tool for understanding basics and roots of TPS

"Toyota Production System" was published in 1979 in Japanese and, in English in 1988. It is the source material on the toyota production system and, in my view, it is often good to go back to the source. Sadly, I found this book disappointing. The writing style is clunky (perhaps a poor translation) and the book lacks structure; being more of a semi-random collection of points than a development of ideas. Nevertheless there is some interesting stuff in here. The honesty that this is a long slow process (taking Toyota 30+ years) is refreshing, and I hadn't realised that Mr Ohno ranked kanban (with quick changeovers) as the core of the system and essential to success. Often in lean kanban seems to be a bit of a side issue: here it is vital. Also there is an interesting analysis of some of Henry Ford's early writings compared to TPS. This would be good material for a student essay. However, for the philosophy of TPS you will get much more out of "The Toyota Way" or "The Toyota Way Fieldbook"; and for the tools of lean go to "Lean Production Simplified" or the many other books in this area. Overall this book is a bit of a let-down I am sad to say.