Professional Books

The "how to" leadership books are spilling off the shelves, so I thought that "Trust Me" to be another ineffective book on this subject. However, as I began to read I couldn't put the book down. I read it through in 2 days. I've then re-read it 2 times. It is GREAT!

Ron Potter and Wayne Hastings have managed to peel away to the true core of leadership.

From insight about the greatest leader of all time to colorful stories about other leaders, it's a riveting book.

This book has personally changed my life and my leadership style. I have incorporated the principles from the book and have created personal goals in an attempt to be a better leader.

If you lead people...either a business executive, production line worker, a team player or a parent, "Trust Me' is essential reading.

I found this book fascinating as the authors focus on the internal world of leaders who are trustworthy, and the nurture of a character that others will want to follow. My favorite quotes:
--To be teachable, one must devote a significant amount of time to learning.
--Leaders are defined buy those who follow them.
--A successful mentoring experience does require a significant prerequisite: a quality person to mentor.
--The mentoring or coaching role is mainly about creating a safe environment to discuss any topic.
--Trustworthiness means being reliable, faithful, and unfailing. Trustworthy leaders are honest and transparent, committed, dedicated, and keep promises and confidences. They also have the moral courage to do the right thing and to stand up for what they believe even when it is difficult to do so.
--In practical, day-to-day leadership, only what is accomplished matters.
--Compared to high-profile leaders with big personalities who make headlines and become celebrities, the good-to-great leaders [leaders who have taken companies to unprecedented long-term growth] seem to have come from Mars. Self-effacing, quiet, reserved, even shy--these leaders are a paradoxical blend of personal humility and professional will. They are more like Lincoln and Socrates than Patton or Caesar.
For aspiring leaders, this book will help you clarify the character traits needed inside before the power accumulates outside.

Presents a style of leadership based on 8 values: humility; development; commitment; focus; compassion; integrity; peacemaking; and endurance. The authors explore how these spiritual values are keys to building trust with people and becoming a successful leader, as well as building a successful career. This book has its distinct point of view-no question about it. But given the abundance of bad leadership in business, politics, and other spheres, the spiritual qualities this book links with effective leadership deserve serious consideration.

Trust Me is one of those rare books that provides timeless insights with personal insights and help for all of us. Hastings and Potter take the reader on a leadership journey and challenge us at the end of each chapter with thought-provoking questions and personal growth suggestions. I literally could not put this book down! It has helped me and my team to understand how we can be successful leaders. This is a must read for any person wanting to improve their leadership skills.

Wayne Hastings and Ron Potter have written an inspirational book that provides the key principles we all need to guide us in our personal and business lives. It is a book to be kept close at hand to keep our thinking and actions on the path of a principle based life. The real life stories and the opportunity provided to reflect after each chapter with thought provoking questions about ourselves and how we interact with others helps teach us how to be leaders others can trust.

Honeynet solutions were seen just as a research technology a couple of years ago. It is not the case anymore. Due to the inherent constraints and limitations of the current and widely deployed intrusion detection solutions, like IDS/IPS and antivirus, it is time to extended our detection arsenal and capabilities with new tools: virtual honeypots.

Do not get confused about the book title, specially about the "virtual" term. The main reason to mention virtual honeypots, although the book covers all kind of honeynet/honeypot technologies, is because during the last few years virtualization has been a key element in the deployment of honeynets. It has offered us a significant cost reduction, more flexibility, reusability and multiple benefits. The main drawback of this solution is the detection of virtual environments by some malware specimens.

The detection of honeypots has always been one of the main concerns in the honeynet community, basically because if the attacker can identify them, they are useless. For this reason, one of the chapters is just focused on providing some light, tips, and tricks about what an adversary can really accomplish. In fact, we have not seen lots of real-world incidents where the attacker actively checks the existence of honeynet setups.

I have been working with honeynets during the last 5 years. We founded the Spanish Honeynet Project on 2004, and almost at the same time we became part of The Honeynet Project and released the Scan of the Month 32. The main honeynet/pot book reference till last year was the book published by the Honeynet Project. As this is a rapidly evolving field, definitely it has been replaced by this book, written by two project members.

The first chapter is a very brief introduction to honeynet technologies and basic tools. You can jump through it if you are not new to this field. Then, the book covers the main two honeypots types: high and low interaction. The high interaction section provides details about the tools to virtualize your honeypots: VMware, UML, or more specific solutions, such as Argos. The low interaction section provides details about some the most relevant honeypot types to cover lots of detection scenarios: worms, traditional server attacks, Google Hacking, Web-based attacks, etc. It is a wide overview that will give you lot of ideas for new deployments.

The whole book has been cooked with a how-to mentality , and it explains in detail how to install and configure the different tools and software elements covered. Additionally, it provides guidelines, best practices, and analysis recommendations for each tool based on the authors experience. However, for the how to portions take into account that most of the solutions are Linux-based, and the installation and setup process will vary based on the tool version and the Linux distribution you are using (library dependencies, etc). In any case, the step by step guides are very useful as a general setup reference.

From my perspective, the most valuable part of the book is chapters 4 to 6. The authors, Niels Provos and Throsten Holz, are the lead developer/architect for honeyd (chapter 4 and 5) and strongly related with nephentes (chapter 6), respectively. These two are the most famous and advanced low-interaction server-based honeypot and malware honeypot. They know what they are talking about :), and you cannot find a better reference out there for these two tools. The book is an excellent guide, covering from the design principles and innovative deployment ideas, to all kinds of configuration options and possibilities, including limitations on real-world scenarios. Chapter 6 is complemented with other less popular malware-based honeypots (except for Honeytrap).

The book includes some extra material, covering academic and research hybrid solution, still on their early stages, but that can give you and idea of where these technologies are evolving to and the major challenges we are facing nowadays. This pretty much theoretical content is well balanced with the case studies chapter, where real incidents involving different honeypot types are presented. These are always a fun read and a way of getting experience and learn how to deal with intrusions.

Finally, one of the main expansion areas we are involved today is the creation of new client-based honeypot technologies. This book section (highly recommended) does a great job introducing multiple high and low interaction honeyclients currently available, their benefits and drawbacks (chapter 7). This information is perfectly complemented by the last two chapters, focused on tracking botnets and analyzing malware with sandbox environments. Once a client is compromised, it typically becomes a member of a botnet, and for easy and quick categorization, we start by performing a malware analysis of the specimens. I recommend you to add all this knowledge to your incident handling and response capabilities.

Something I would have liked to see in the book is a section about a fully virtualized honeynet environment, showing how using VMware, you can build up a virtual Honeywall (just slightly mentioned on chapter 2) and different honeypots, creating a complete, cheap, mobile and multi-purpose virtual honeynet infrastructure. Also, we receive multiple questions related to this kind of setup in the Honeynet Project mailing lists, because all the previous whitepapers are obsoleted now. I've been deploying these type of solutions for fun and professionally during the last few years and I strongly recommend you to start using them. You won't be disappointed about how much you can learn of what is going on in your networks and systems, and this book is the best starting point.

If you have any relationship with the intrusion detection, incident handling and forensics, threat analysis, or SOC and CERT security side of things, definitely this book is for you. Go through it and improve your capabilities with easy to deploy virtual honeypot solutions. You just need a (not so new) computer, virtualization software, and some time!

The book is well written and I feel that I will be successful in setting up my first honey pot once I get my network segmented for security purposes.

Excellent, really good, sorry for my bad English, but is EXCELENT BOOK.

Regards

Carlos

I have relatively little to add to the praise that has already been given of this book, but I found it extremely enjoyable. In particular, the chapters on collecting and analyzing malware were quite good, in my mind. I think the book delves a bit too deeply into man page territory with the level of detail provided on the minutia of utilities, but that doesn't detract from the book, as it is very clearly segmented away from loftier topics.

Overall, I found this book to be quite excellent, and very informative and accessible to those new to the arena of Honeypots.

It's fairly difficult to find good books on digital defense. Breaking and entering seems to be more exciting than protecting victims. Thankfully, Niels Provos and Thorsten Holz show that defense can be interesting and innovative too. Their book Virtual Honeypots is your ticket for deploying defensive resources that will provide greater digital situational awareness.

A security technician with some degree of proficiency should be able to read Virtual Honeypots and then implement at least one of the solutions presented. This sounds like a fairly common event, but too often technical books do not provide the detail required to transform theory into practice. Virtual Honeypots offers installation and operational guidance for a variety of deception and analysis systems, primarily for server-oriented technologies. I especially gained a better understanding of Honeyd and Nepenthes, the two applications about which I cared the most.

While I liked the first 2/3 of the book, I have to say I really enjoyed the last four chapters. These covered Detecting Honeypots, Case Studies, Tracking Botnets, and Analyzing Malware with CWSandbox. Of these the final chapter was superb. Ch 12 has probably the clearest explanation of hooking I've read anywhere. I am not a rootkit writer or Windows kernel programmer, but the text was so well written I had zero problems following along.

I gave Virtual Honeypots five stars because it is so unique and well-written, but I do have a few minor issues to mention. First, I was somewhat disappointed by the honeyclients section (ch 8). I was not as confident that I could implement a honeyclient solution after reading the great material on server-oriented honeypots. Perhaps the second edition or a separate book will give greater attention to this area. Second, I found a few small technical items. On p 4, it isn't accurate to say "TCP...[gives] each packet a sequence number." Bytes of application data are numbered, not packets. On p 13 we are told to use a snaplen of 1500 bytes, but this will cut off the last 14 bytes of many Ethernet frames. Try it with ping -s 1472 while sniffing with Tcpdump. As you can see, these minor issues are easily fixed in a future printing and do not justify dropping a star.

If you are at all interested in potentially deceiving intruders, buy and read Virtual Honeypots. You'll learn about more than VMware (QEMU, UML, etc.) as well as numerous open source tools you can download and try for free. I look forward to reading more from these authors -- perhaps a book of true case studies?

Dr. Froehlich writes a refreshing view concerning globalization of economies and markets, but you shouldn't expect this book to tell you where the money is. Well, I guess it does; it's in the market somewhere in one or a combination of five sectors (Pharmaceuticals, Technology, Telecommunications, Financials, and Energy). Besides that common knowledge, he also explains that the market is currently moved by fear and greed and people should think and invest "long-term" instead of acting on emotions created by mass amounts of information and constant hype. I didn't need to spend $29.67 for that info either. The book simply explains that the world of economics is changing because of shifting demographics, globalization, technology, government, and business trends. The thing that I like most about the book is that it made me sit back and think about the "big picture" for a moment. It's not a bad read as long as you don't expect to finally get to the page that tells you where the money is.

Thanks, Dr. Bob, for a great book on investing! This book is something I have needed to read for a long time. When reading investment books, the advice is often about IRAs, 401(k)'s, bonds, stock market, market timing, etc.

Dr. Bob's advice is in a totally different area. He believes in something called "sectornomics" which means if you look at all the industry sectors and determine which ones will do well in the next five years, then invest in several companies in that sector, your portfolio will do well. Don't worry about which particular stocks too much, just pick the right sector. Pharmaceuticals, let's say. Then, for the majority of the book, Dr. Bob goes on about the various trends in the US and worldwide which will whip the stock market sectors one way or another.

Should you bet on a Japanese resurgence in the next ten years? Don't think so. How about betting on the graying of America? Sure, says Dr. Bob, but remember, Europe and Asia are graying too.

Doesn't sectornomics break the rule of investing that "the only thing that makes the stock market go up or down is a surprise?" Doesn't everyone know about the graying of America? Yes, they know, but no, it doesn't break that rule. Sectornomics means "looking at the same thing everyone else looks at, and seeing something different." Your own perspective can give you the added advantage over the market.

Inspired by Dr. Bob, I began my own personal portfolio based on alternative energy, because I have found out that this sector is about to boom in the next 10 years. A little research (using the Internet of course) and now I have a list of about 30 companies who are extremely well positioned to make a lot of money once alternative energy goes big. The key for me was seeing the big players (United Technologies, Idatech, Xcel, BP, etc.) investing heavily into this sector. BP makes millions of dollars yearly from manufacturing solar cells.

Dr. Bob's knowledge of statistics is absolutely amazing. And his writing style is very approachable.

I heard Dr. Bob speak at an investment seminar in Columbus, Ohio. His speech was good but his book -- excellent. Just buy it. It is the best investment you will make this year.

Not the most insightful financial book I've read. It contains a fair amount of fluff. It does point out some major trends based on demographics and the concept of sector investing.

If only all of the talking heads on CNBC, CNNfn, Bloomberg and the other financial media were as easy to read and understand as Bob Froehlich.
Readers who wish to truly understand money, the economy, the stock and bond markets, and future investment trends should read this book. They should make sure their spouses and older children read it, too. I know I wish I had read it before the last bull market, and the correction in 2000.

Robert J. Froehlich has written an informative and highly readable guide to understanding the emerging global economy. Never dry, dull or dense, his book focuses on the factors that combine to create both major and minor global economic trends. If you understand these trends, he maintains, you can make wise investment choices now and in the future. At the end of the book, Froehlich includes a glossary of terms, though - unlike many investment books - you don't find yourself lost in a sea of insider jargon while reading. He writes delightfully, easily shows you how global trends connect and conversationally explains what this means to you professionally and personally. We [...] recommend this book to all readers, since no matter your area of expertise or interest, if you live on this planet your economic well-being is affected by globalization.

I've read other books about finding life's purpose and calling, but they often do not give you the tool just to do that. This book does!

I've been using the Calling Card exercises to help my family and friends discovering their life's callings. It's a very easy and effective tool to find life's calling.

Books like this do everything in their power to get your drive going. And every time I read one (which isn't often), I do feel good about myself. But in the end, I'm back on Earth a few days later. OK, I am sounding pathetic, but the truth is, there isn't a whole lot of practical advice here, just motivational anecdotes. To be frank, there is nothing wrong with that. It just needs more to distinguish itself.

It starts out promising with the part about choosing the characteristics you most want in a job. However, it goes downhill with the straight out of "Touch By an Angel" cabbie stories that start every chapter. What I really did like about this book is that it makes you reevaluate the situation you are currently in to make the most of it. It doesn't preach dropping everything and chasing after your dream because not all of us are in a position to do so. Another thing I liked is that it keeps the message short (under 200 pages). There is no need for a book like this to be 300+ pages. All in all, it's a good starter book for those looking to make a career change.

This book helped me put a Name Tag on my life's calling.
I also found out how often I am able to use it in my job (only 10% of the time).
Now I need to know what jobs I could get that would maximize my use of my gifts - so I will never have to 'work' another day.

There are 52 transcendant calling cards from which everyone can pick their gifts. There were not enough examples of how people use their callings appropriately. I would have at least wanted to see a list to match jobs to calling cards.

I highly recommend this book. I've been trying to figure out what I wanted to be when I grew up for a long time. Now I finally am able to put a name to it.
I got the book from the library, I wouldn't recommend buying it.

Get control of your career and your expectations of what career means in your life. This book does a great job of guiding you along as you question where you are in life and where you want to be. Redundant at times and interactive "take control books" usually don't appeal to me, but this one is an expection.

Davey is a great guy. He rides his bike all over Seattle. He wears really cool glasses too. I'm honored to be mentioned in the book. Dave is a great writer and philosopher. Everyone should buy this book and give copies of it as gifts to their friends.

I needed to read this book. I am in the process of pursuing a private pilots license and this was so beneficial to me to be able to read a book that answered those questions I would have never thought to ask.

I must agree with every positive thing said about this work. It has really inspired and carried me through into actually taking action. Like having a friend by your side, giving advice.

Very well written introduction for anyone considering becoming a pilot. This book provides a short, but thorough, analysis of just about all that being a pilot involves - from initial training to life as a General Aviation pilot. Finally - a book well worth the money!

Your Pilot's License provides a simple, concise guide to getting your license to fly. Eichenberger describes both how to actually fly a plane as well as the process by which one learns how and is licensed to do so. Eichenberger's experience as a flight instructor (CFI) clearly shows, as much of the book reads like a flight lesson.

The book is a must-read for anyone thinking about taking up flying or who has just started taking lessons. Not only does is summarize what to expect, it also provides a wealth of knowledge that should help make your lessons more effective. Eichenberger explains complicated concepts in simple English. Particularly helpful to the beginning pilot will be his explanations of how lift works and how to "fly the box" taking wind into account.

For those who have been flying for a period of time, the book offers very little (other than perhaps nostalgia about those first flights). If you don't already know what is covered in this book (and in some areas, significantly more than is covered) you really shouldn't be flying a plane.

For those looking to get their flight instructor certificate, this book holds particular value as it will help you learn how to teach your students! It is also very helpful in remaining us how if felt "from the other side."

I am a CFI (Certificated Flight Instructor) and have read several popular 'Private Pilot Training' manuals. Many of them are expensive, and very thick. I don't use them though...I use THIS book. It covers 90% of what I want covered in ground school, and I augment it with other materials as I see fit. It is quite inexpensive, and it is very well-written. I highly recommend this book to prospective pilots, to student pilots, and to certificated pilots as a handy 'quick refresher'. If you have ever considered becoming a pilot (trust me, it is worth every penny), this this book gives you a great overview of what flying is about.

This book is absolutely not a book for beginners, but a great desk reference. A must have for any serious Access developer.

As the word 'Developer' should imply, this book is not for MS Access beginners, but once you qualify yourself as 'intermediate' or better, you will feel right at home. Very little of this book is devoted to boring you with rehashes of stuff in the help file (as most other books seem to do). There is a great deal of depth and insight into areas that apply to everyday usage, complex projects, and solutions to many problems MS tends to ignore version after version.

The writing is excellent and they have a web site devoted to updates, errata and such which is very helpful. Chapters 10, 14 and 15 have had an extremely positive impact on the quality and usability of my projects in MS Access as well as VBA and Visual Basic. Many of the code samples are outstanding and written so that you can just drop them in to your projects with no modifications. Many of them are done so well they seem like natural extensions to MS Access (stuff MS 'should' have included in the 1st place).

Complaints? None. Well, okay, I do have 1 minor complaint. They devoted almost 30 pages to The Office Assistant. IMHO these pages and the Office Assistant itself are a complete waste.

This book and its previous versions are the best money I have ever spent. They continue to save me hundreds of hours while adding reliability and capability to all my projects. Highly recommended!

Not only is this series the absolute best when it comes to MS Access, it is the best technical documentation I've had the pleasure to use since the early days of Vax/VMS. A perfect blend of explanation, examples, syntax, and guidance. A level of art to which all others should aspire (and regrettably too many do not).

I'm comfortable with Access but when it comes to VBA I'm a newbie. This book doesn't only tell you what to do, but explains the why behind it. I have a database that I've put double digit hours (10+) into one problem. I got the book read up on combo boxes, the problem area, and in 30 minutes debugged my code to make them do what they were suppose to do. If I get nothing else out of this book it was worth it for that one issue, but upon further reading I'm learning the why's of Access. The code is still a little foreign but now I'm much more comfortable working in VBA. They use Reddicks naming convention which is different to me, but that's easy to look past. A great book!! Thanks Sybex!

Without a doubt, THE best book on Microsoft Access you will find. Most Access Developers will have several books on the shelf next to their desk gathering dust while they search through Google to resolve their latest dilema. Although I'm a Googler as well, my copy of ADH is frayed and worn...but never dusty. The authors write confidently and authoritatively, yet it seems that they take precautions to avoid intimidating the novice. I've seen reviewers referring to this book as "not for beginners." I was at the beginner-intermediate level when I first thumbed through it at a bookstore. I thought the pricetag was a little too high, but after about ten minutes I had to own it. Since then, it's brought me a long way. Whatever your level, if you really want to learn this stuff you will find great value here.

Where the K&R book is terrible for learning C, this book makes it a snap.
It provides an organized and complete tutorial for the novice C programmer as well as a useful reference for the more experienced C user.

As some one who took an unguided path into C programming, I can really appreciate how much of a difference this book would have made if I came across it earlier.

This book elegantly lays down the structure and parts of the C language. It presents the reasons behind various features of the language.

This is the book that will teach you to think about programming in an intuitive way.

I have read the second edition and recently bought this third edition that has ANSI standard C in the main body of the work, rather than K&R C. I am using it to brush up on C that I have not used in a while. It is still a great book.

I have read the other reviews from December 1997 through February 2004. I do not have much to add to what has already been said, other than what the others write is true. I wish all technical books were this well written.

The perfect balance of complete, useful information on ANSI C. All technical information (data types, operators, declarations, pointers, arrays) is there. It it all explained in sufficient, readable but not wordy detail. It is remarkable in its efficiency.

It's all in there - the preprocessor, railroad diagrams showing the syntax of each statement, code snippets where they useful. Data structures, starting with the bit datatype, then defining and explaining more advanced concepts of unions, structures, and the user-defined types using _typedef_. Then full examples tieing it together with linked lists, then doubly linked lists.

A brief section on software engineering concepts showing the importance of design and test, and finally a complete working C interpreter.

What really sets it apart though is its complete reference of the most-used standard library functions - formatted and file I/O, string and memory manipulation functions. Effective use of the proven library functions is one of the marks of the software professional, and the outer framework of most useful real-life programs is getting data in and out.

The book begins with a very high-level overview of programs to establish its context, but this is NOT a how-to-program book. If you already understand the fundamental concepts (arithmetic and logical operations, looping) and you need a comprehensive book on how to use C, this is the one. There are lots of books in the "this is a reference, not a tutorial" class (e.g. K&R) and lots of wordy tutorials that never get to the difficult parts (like 'how do I pass a pointer to a multidimensional array.'). This is one book that is sufficiently organized to be a reference, with enough clear explanation that you'll learn how and why things work.

I've had my 2nd edition of this book since it was new in 1991 and recently purchased a copy of the reviewed edition for a friend. It's still excellent, with improved coverage of new features and extensions, and removal of the obsolete adjective "new" when referencing the ANSI standard that's been ratified for a good long while now.

There is no mention of C++ - this is a C book. Good ol' ANSI C is still the language of choice for many if not most embedded projects, even new design. I believe a solid foundation in C will serve any C++ programmer well - under the 'object' layer of C++ lie member functions that actually do the work, and those functions look a lot like C...

Like most good technical books, this one's not cheap, but it's a quality Springer-Verlag binding on acid-free paper that will last a career if not a lifetime. And considering the depth, breadth, and clarity of the content, it is a bargain.

A must-have.

15 years ago I came across this book accidentally in a second hand shop primarily selling Springer books.
I already had K&R because it was best known, but was not really satisfied with it as a transitioner from Fortran.
This book had all I needed, especially on pointers (see all other reviews).
I always enjoyed reading it. It's not about becoming a C obsfucation contest winner,
but about C as a tool for software engineers.
Combined with Harbison & Steele's "A C Reference Manual" and Hanson's "C Interfaces and Implementations",
which are my other most referenced C books, you will have a solid basic library to rely on as a C programmer.

I have a few books on my shelf on this topic, but this one was the most impact-full to me in terms of its intensity.
This was due to how extensive the examples of abuse are.
Like Fox's book of martyrs, I had to read it in bites, and put it down occasionally.
I guess I'm not very thick skinned :~/

If you are a serious leader in the church, you should be familiar with this material.
Some will say that these events prove that Christians can find safety from abuse within the institutional walls.
But so didn't the children of Israel find safety within the well protected walls of Egypt.
Every institution of man has its pros and cons.
And if you know what to look for, you can always identify the servants and the masters there.

This is why I found this particular book so important.
As I observed the characteristics of one abusive Christian system after another, I started to see the necessary building blocks which lead to the abuse.

For me, the bottom line is, that there are large numbers of people in the world who are very happy being followers. And out of these, are a large number of vulnerable souls.
Vulnerable people are easy to take advantage of.
And it takes a very high level of Christ-character not to be drawn into doing so.
The seed of abuse is inherent within our first Adamic nature.
When the environment is conducive, the seed germinates, and if the new-man does not cast it off, (Hebrews 12:1) we soon have a very large tree.

To be the CEO of Enron requires a high level of academic achievement, business acumen, and charisma.
And so, when an instructionalized clergy-laity system, based on the template of the world exists, the fruit is inevitable.

Men who are put into positions of leadership within a church, which following the template of the world, selects them solely by academic achievement and charisma.
Men, in authority with very little Christ-character worked into their lives are seed beds of abuse ready to germinate.
Place that seed into the ground of vulnerable and submissive followers, and you have today's Christian version of Enron.

This book will help you to see the signs.
100% thumbs up.

I believe we all know of people who have been in abusive relationships and even abusive job situations but it is sometimes hard to imagine people getting involved in abusive churches. That is why this book is a must read for every disciple.

This book exposes abusive churches. Dr. Enroth even names names. Every chapter opens with an abusive story. Each person is real. Each person has been hurt by abusive churches. The irony is that the leaders discussed in the book fail to see their abuses. Many try to cover them up or simply ignore the pain they have dealt to others.

In the end, I appreciated Dr. Enroth showing the reader that Jesus is not the abuser. While most of these religious groups claim to be speaking in His name or even quote Scripture, they have twisted the teachings and practices of Jesus to be something He never intended (1 John 5:1-4). Truly, Jesus is not like men (Hebrews 13:8) and He will not cause us the pain that is found in this book (Matthew 11:28-30).

There are extreme forms of church abuse and subtle forms. As we grow as individuals we need to learn how to use our wisdom to prevent us from getting involved in abusive situations like church cults. I really didn't need to read much of this book to know the author's motivation for writing it. I was a member the church that ultimately inspired Mr. Enroth to write this book. Fortunately for me, I was not easily controlled, but there were still things that I went along with simply to appease people I assumed were my friends. Unfortunately, there were members who were not a strong willed and this led to broken homes, severed relationships, and suicide attempts among many other things that left me questioning my own sanity for being involved in something that so obviously had nothing at all to do with God. Read this book if you or someone you know is involved in a religious cult because it might very well save a life or at the very least save someone's sanity.

This book is helpful and encouraging. Find the life in it and you'll be glad you read it.

In a world of "mega-churches" and cults of personality, it more important to arm oneself with the truth, and not someone else's version of it. While the examples in the book are taken from the late 1980's, and back about a century, there are many examples everyday of the devastating consequenses of spiritual abuse. Whether it is David Koresh and the Branch-Davidians, Jim Jones and Jonestown, or even Andrea Yates (who's mental illness was only worsened by her husband's minister) the results are tragic. Bad churches happen when good people don't step up and say anything. Read this book and recognise the patterns.

This is a very good book for people who want to learn the in depths of routing in general and cisco routing in particular. Protocol description is very well written going from beginner to advanced level. I recommend this to everybody who wants to make a networking career.

This is a corner-stone of Cisco routing engine explanation. It doesn't contain any braindump stuff like many books do. But it covers many topics: theoretical basis, IOS pseudo code explanations, configuration examples and trace/debugging methods. There are also many interesting details and gismos that I didn't find anywhere . It's very useful as a preparation guide -- you have to read this book if you do want to pass some sort of serious Cisco's exams (I mean CCNP or CCIE). So it's outstanding title (in other words -- it worth to spend 50+ bucks for it guyz!) :))

Btw, now I'm waiting for your next book. Why not? Will it be dedicated to MPLS or MLOSPF? Huh? :))

This book is not for the faint of heart.
Ever read a book and find a sentence that makes you say "man that one fact was worth the cash!". You get about one sentence like that every page in this text.

Example:
ip route 192.168.1.0 255.255.255.0 s0 172.17.1.33

I bought the book because I wanted to understand when, why, and how that command works. All of my questions were answered.

Since I'm not a programmer some of the explainations took me awhile to get, but worth it.

Gold.

With my CCNA exam date staring straight at me, I decided to finally read my copy of Alex Zinin's 'Cisco IP Routing.' This book clearly exceeds the level of knowledge to pass Cisco's entry level certification. It is aimed more at CCNPs or CCIEs who need a deeper understanding of Cisco routing. Nevertheless, I found the book's explanations of certain subjects to be absolutely outstanding, even for a CCNA candidate. I recommend anyone wishing to learn Cisco router operations read 'Cisco IP Routing.'

This book seeks to deliver the 'why' as well as the 'how' of Cisco routing. It was published in late 2001 and uses IOS 12.1 as its reference platform. This IOS version is recent enough to meet my expectations, so don't fear that the book may not apply to more recent Cisco software and hardware. Remember that the 2600 series router was introduced in January 1999, and the modular 2600XM series arrived only in May 2002.

The first compelling aspect of 'Cisco IP Routing' is its exceptionally well-written and thorough explanations of various routing topics. Although my understanding of the subject was improved by reading Todd Lammle's Sybex CCNA books, Alex Zinin's approach assisted me immensely. For example, he helped me understand that classful addressing offers basic subnetting, which 'was used in the real world long before VLSM [Variable-Length Subnet Masks] appeared' (p. 22). He made it clear on p. 52 that 'when multiple matching routes are available to the same destination, routers choose the longest matching route to forward the packets.' This allows specifying a default route that is only used when more specific routes do not match a given destination.

Beyond very insightful routing discussions, Alex makes his point using a variety of methods. In some cases he presents tables that compare protocols. Elsewhere he uses diagrams or figures. Throughout the book he demonstrates syntax and configuration, along with debugging messages showing how protocols work in real life. His innovative use of 'pseudo-code' shows how Cisco might represent protocol information within IOS itself. In many chapters he presents and answers frequently asked questions. These help to dispel myths readers may have concerning Cisco routers.

I cannot complain about any real aspect of this book. As a minor point, Alex's thorough examinations of routing packet headers should have been augmented by real packet traces. I would like to see a companion volume introduce topics like spanning tree, BGP, and other routing and switching issues. Readers looking for such coverage now might like Radia Perlman's 'Interconnections, 2nd Ed' and Iljitsch van Beijnum's 'BGP.'

If you want to truly learn what your Cisco router does when it makes forwarding decisions, you must read 'Cisco IP Routing.' I have not seen any other books so powerfully expose the inner workings of these critical systems.

The first time I heard this book is when I took the Internetworkexpert's online course. Brian McGahan recommended it. Becuase of its high customer rating, this book should have something worth studying. After reading through a couple of chapters, I feel it is a great book in IP Routing protocols.

This book presents concepts along with router outcome, so it's fairly easy to follow the author's logic in each different technology. This makes this book easy to digest. The way it presents how routing protocols work is very similar to Doyle's TCPIP vol.1. Yet, its editing style is more concise and it covers more in-depth materials in the IGP area.

Associated with Doyle's TCPIP and Parkhurst's OSPF, this book should be a required reading for CCIE RS candidates.

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.

This book gives you a better understanding of the patterns than in its original version (the GoF one). I am not a SmallTalk programmer but a 9 years C++ one. At work I had to use the GoF book and never liked reading it. In contrast to this, the SmallTalk companion is easy to read and you can understand the patterns within the first few lines of their description. Take the Bridge pattern and compare their discussions in the two books. If you really like the Gof one then buy it. But according to me, it would be a big mistake buying the GoF in favour of the SmallTalk companion. Trust a C++ programmer :-)

This isn't a Smalltalk translation of "Design Patterns." Instead, it's a companion to that book. You'll need to read the first one to get the most out of this one. If you have read the first one, you'll find this one is better written and really casts essential light on some of the GOF material. The Smalltalk aspects of this book are really a non-issue (except perhaps showing static-typers how many hoops you don't have to use in Smalltalk). This is required patterns reading.

I bought this book because of the unresolved questions I had after spending so many hours exploring the GoF original book. I am an experience C, C++, and Objective C programmer, not a Smalltalk guru at all. And I found the GoF very confusing and intimidating. My current projects these days are written in Java (I miss Objective C). I looked for a book that would cover the pattern catalog in Java because I was really questioning the purpose of some of them in that language. Creating some mechanism to overcome the C++ language is somewhat understandable, but why bother with Java. Take the prototype pattern for example: "...It's (the prototype pattern) less important (to use it) in languages like Smalltalk or Objective C that provides what amounts to a prototype..." (page 121) Sure, ok, but what about Java? Can you give me an example on how it would benefit a language that doesn't really require it like Obj C, or even Smalltalk? Then the sample code refers to the maze example but not much material is given here. I bought several books with Java and Design Patterns in the title but was very disappointed with the beginner level these books approach this problem. The titles are seductive but the content is not that great. I don't need another ADOO (I've read Larman's book already. Get it if you are new to OO BTW.) So I ended up getting that book as a last resort. And you know what? It's great. I program in Java all day (and sometimes all night, sigh...) and this book spends more time on my desk than the GoF original one. So, if this comments remind you some of your experience, you should give this book a try. And this book lighted up another bulb in my brain: I ended up downloading Squeak and prototyping in Smalltalk some of my projects just for the fun of it, but that's a side effect I guess ;-)

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.