Networks Books

This book discusses most aspects of network design to an impressive level of detail. No fast answers are given as is appropriate for a design book. The author's approach is such that he immediately commands the readers respect and from what I have seen is only matched by Cormac Long's design book. The only gripe I might have is that I found the style a tad long-winded at times, since I personally prefer books to be as concise as possible.

this book has cleared up a lot of clouds in my mind about Internetworking concept as well as router/switch issues. Thanks, Howard.

I really like this book. Despite a slight tendancy to ramble, Berkowitz style is very enjoyable, humourous at times, and he explains everything in detail. This is a book geared towrds understanding the concepts of routing and switching, rather than analyzing everything from the manufacturers viewpoint. As a result, you get a firm understanding of the fundamentals. Where appropriate, he does discuss manufacturer specific design/philosphy (e.g. cisco, nortel, etc.), but for the most part it's completely independent of that. Hence, this is useful regardless of what gear you're using. This is a must for every network engineer's library.

Delightful might seem like a strange word to describe a technical book, but it's exactly what I mean to say. I find myself being delighted with Howard's unique way of presenting the essence of a network technology. I hear myself say "ah hah, that's what all that incomprehensible text in those other books meant!" Howard uses analogies and real-life examples to ensure that the reader really understands the basics and the details. Great book for learning routing and switching architecture design.

This book is incredible. Howard speaks with a voice of absolute authority. He presents all sides of the issues and leaves the reader to come to his/her own conclusions. He is obviously a master of his craft, and reading this book is sheer pleasure. It would be a fantastic book if it was comprised of dry text and facts, but that's far from the case: this book was written by a man who understands the writer's prerogative to keep his audience awake and entertained. To my knowledge a better book on network design does not exist. Highest recommendation.

An excellent account on the application of Network Centric Warfare theory. Well written and understandable this book will be standard on the emerging theory of Network Centric Warfare. This book is a must read for anyone interested in either the realities associated with the modern battlefield or perhaps even the corporate boardroom of the future.

An excellent account on the application of Network Centric Warfare theory. Well written and understandable this book will be standard on the emerging theory of Network Centric Warfare. This book is a must read for anyone interested in either the realities associated with the modern battlefield or perhaps even the corporate boardroom of the future.

An inspiration and catalyst for future books on the subject. A very comprehensive guide that is the current authority on Network Centric Warfare Theory. Well Done.

An inspiration and catalyst for future books on the subject. A very comprehensive guide that is the current authority on Network Centric Warfare Theory. Well Done.

First time I have seen this topic addressed in a complete , well thought out manner. Excellent for both experts and novices. Frist Rate, highly recommended

This book is a must read for anyone involved in the ever-changing world of technology. Reading this book provided an amazing plain-english understanding of all issues surrounding network security especially as they relate to my businesses and my clients. As an attorney, this book gave me the ability to understand the language my clients speak and to relate to the specific needs of their different businesses - especially in light of today's regulatory environment (i.e. Health care, Securities, etc). It has also proven to be an essential tool for my own IT department regarding our own issues when dealing with sensitive and confidential client information.

This book is a must read for a business owner or IT Director. The authors do a wonderful job of breaking down security issues in such a way that an executive can understand the dangers that exist, and IT staff can recognize and diagnose exposure within their own networks. They bring many issues to light that may otherwise be overlooked, and are able to break down a complex and cumbersome topic so that it can be understood and applied to an individual company. The reader learns how to asses his or her company's risks and what to do to mitigate the damage. An essential tool for any manager. Beautifully organized and illustrated, it allows the business person to understand the technological issues while bringing the business concerns associated with network management to the IT department.
Have at least one copy of this book on your company's shelves.

I'm not a computer wiz, far from it actually. I consider it a successful trip to the internet when my computer doesn't freeze up or start spouting error messages at me. Never in a million years would I think that this book would interest me. Boy, was I wrong! A friend of mine (computer geek) had this book sitting on his coffee table last weekend and I picked it up to see what was what with something I know nothing about. I was expecting the usual technical manual, a Saltine, dry, uninteresting, tasteless. What I found was a witty, colorful, and interesting tome on network security. The guys who wrote this book obviously know what they are talking about and they make it easy for a layman like me to understand a field of knowledge I thought I'd never be frolicking through.

When I bought the book, I didn't know what to expect but am now very happy I made the purchase. It clearly and concisely informs, pointing out the holes that may exist and providing the tools and know-how for business-driven solutions. Now I have a whole lot more confidence in my ability to address security concerns and articulate our capacity to investors, helping to reassure them that we are vigilant in practice.

The map is indispensable, perfect for rendering network issues in comprehensible terms. When network security questions arise, it'll be nice to have the map handy to help illustrate explanations, which, the book demonstrates, need not be unwieldy.

Both tech guys and execs should read the book. It provides a common language with which to talk about network security, facilitating communication on the most serious of organizational priorities.

With intelligence and wit this book tackles an issue that keeps business and IT executives up at night. For an intelligent business person, the book strikes the perfect balance between readability and technical content. It fills the wide gap on the shelf between the dumbed down primers and the textbooks for doctoral candidates. The graphic interpretations (that Edward Tufte would appreciate) perfectly complement the text.

You'll find the book indispensable if you are a non-technical executive who needs to understand network security or if you are an IT professional who needs to explain it in business terms.

Networking By Example is a beginning level guide to teaching the latest technologies and putting this knowledge to use. Using high-quality, detailed photographs and diagrams, author and computer expert Barry Press makes learning simple and straightforward. Barry Press explains various techniques and a broad number of subjects on setting up networks for the small business or home. Beginner, 448 pages

A few months ago I compared networking books at a bookstore with a generous collection of computer books. I have a background in PC hardware, introductory networking and an intermediate understanding of Linux, and I needed a book that was not specific to one operating system. Important components of my home network would be linux-based, but I also needed to include some windows 98, ME and 2000 services too.

The problem with many of the networking books out there is that they are geared to the networking specialist with an advanced knowledge of networking already, or they are dumb-ified for the home-user who would be connecting things with Windows 98. So you are faced with a choice between 1000 page tomes which go into more detail about netware, netbui or wiring than anyone would be interested in. Or you can choice a friendly book full of colorful Windows 98 screenshots (a perfect and actually informative example of that would be "Complete Idiot's Guide to Networking Your Home" by by Mark D. Thompson.).

It is surprising to see how few of the home networking books out there seemed to talk about Linux, although perhaps by the summer of 2001 that will have changed.

"Networking by Example" is a remarkable book because it gives equivalent functions by operating system, 98, NT, 2000 and Linux. It does not go into great depth into configuring services for Linux and Windows (like web servers, samba, etc), but it provides just enough detail for the reader to make sense of chapters from another linux book on apache or samba. This book is one of the rare books that covers both OS's and how to integrate them (the only other book being Unix and Windows 2000 Handbook: Planning, Integration, and Administration by Lonnie Harvel)

One of the most valuable things about the book is the space it devotes to choosing the right hardware and how choice of an operating system might affect your choices. Unfortunately, the book gave a shallow treatment of wireless technologies and somebody looking for wireless information might find better information elsewhere. Sometimes it recommends specific products (which is probably not a good idea, given how quickly models change), but the book gives very practical questions about things to look for when buying a router or cable equipment. The book provides a good number of black and white photographs and illustrations for installing things, and the book contained several chapters near the start that discussed PC-hardware. I skipped through these chapters, but others might find them helpful.

The book does a great job of discussing print sharing and file sharing in both Windows and Linux. It also spends a good bit of time talking about setting up DSL and cable modems, as well as advanced firewall and security topics.

In short: this book is an excellent introduction for the person setting up home networking. Because it is so clear and describes everything so well, it might even be helpful for the would-be networking administrator before he or she pursues more advanced topics. At the time I bought the book, Networking by Example was the ONLY home networking book that discussed Linux and Windows in the same book. By now there are probably others. It gives great advice on picking hardware and setting up linux services. It's only 430 pages, but I've gotten more out of it than books that are twice that size.

I picked up "Networking by Example" because of its simplicity. I was very surprised by the depth and detail the writers took in both explaining and situating Networking. Barry and Marcia Press are very good at explaning Networking. Their writing style is unincumberd by repeteive techno-babble. Instead, they reserve technical terms only when needed. Their pictorials are easily understood and specific examples are given to answer any existing questions.

Very good book for anyone interested in Network basics. Very recommended to those interested in the IT field.

I read this book many many years ago, early on in my I.T. career. It's a good book, and one I would highly recommend for anyone who is new to setting up a network at home (or in a small office). Parts I found especially useful were Chapter 12 "Sharing an Internet Connection". The book has a good description of routers. It also does a good job of describing how your ISP provides you with an IP address for your main machine, and then how you can give your other machines private IP addresses (Ch. 7) and then use NAT which will change all the private IP addy's to the single address your ISP gave you, so those machines can go out on the net.
I also like the fact that there is some discussion of including Linux machines on your network. This book will get you started on SAMBA so you can share stuff between MicroSoft and Linux (Ch. 9).

Recently I posted a review of this very excellent book. I wanted to point out one bad thing about the book, which I guess had to do with timing. Red Hat 7.1 no longer includes linuxconf to do most of the linux configuration, so a lot of the examples do little good for those using Red Hat. (The authors used linux-mandrake, which I guess still uses linuxconf).

One frustration I have experienced with using this book is that it overlooks a description of the files accessible through the command line. Instead the book relies on linuxconf to illustrate. Of course, it's not the authors' fault that red hat no longer uses linuxconf, but that's the problem with explaining things in terms of a gui interface. It would have been nice to include more samples of config files (and commands to run) and less screenshots. I reluctantly conclude that this book wouldn't give enough information to do linux network configuration, although it gives an excellent overview.

What a great book. The author just oozes old timey experience. He didn't dumb down the material. He does cover some detail of XDR and RPC, which I find rather welcome actually. Other prerequisites are expected to be met before reading the book which delves into all kinds of aspects about NFS.

This fine Addison-Wesley tome is an excellently welcome reference right alongside the works of Stevens, etc. in my library.

Amazon lists this as paperback-only, but I delightedly lucked into a hardbound copy from a used marketplace seller. Hooray!

As with all the books in the "Illustrated" series this book isn't a tutorial and it doesn't hold your hand... never the less, if your an experienced admin who's spent years with NFS but just never quite felt like you and NFS understood each other then this is the book for you.

The book is two things... on one hand each chapter begins with a short introduction about a protocol and with it a fascinating history lesson. The rest of the chapter covers the gory details. The history lesson and insights scattered throughout the text shed light on why NFSv2/3 became the mess that we all know and love. NFS is simple on the outside, but if you really stop and think about it... why are there all those protocols, I mean, why do we need a damn port mapping daemon just to keep it all straight!? The fairy tale unfolds throughout the book and finally, I'm glad to say, I think I understand NFSv2/3's sorted past and I'm happy to say I forgive her.

If you've looked at NFSv4 but, deep down, just don't really see the point... I mean, NFSv3 has been around, works everywhere... well, this is the book thats going to make you realize just how desperately we've needed NFSv4 and you'll never want to go back.

Sure, you can read the RFE as other reviewers have suggested, but thats not what your buying here... your buying the Deluxe Behind the Scenes Edition with a commentary that, well, illustrates the whole thing.

This book is getting harder and harder to find. Buy it, have it on your shelf. Its a quick read and an invaluable reference.

This is a very readable and well organized book on NFS. The information is presented such that a reader could read the book cover to cover and gain a detailed understanding of RPC, NFSv2, NFSv3, and related protocols such lock manager and mount. It may and should also be used as a reference for those already familiar with NFS. The one missing part is details of rquota. Otherwise, it is perfect. I highly recommend this book to anyone working on NFS implementations. It is a lot more user friendly than the RFC!

If you're tough, save some cash and read the RFC.

If you want a book which is nicely formatted and organized, get this.

This is a good spec but not too much more. If you're working with NFS much you probably want this.

I saw this book in [local store] and had to have it. For anyone interested in the nitty gritty details of NFS this book is a must! The writer provides a comprehensive and rich discussion of every aspect of NFS 2 and 3 which many environments are still implementing today. Also the writer provides a very detailed discussion of the relationship between lockd and statd and discusses mountd and nfsd in great detail also. For Unix admins who want to become more intimate with NFS I think this is a great resource.

These boys are hot!! The calendar rules!! Especially the September pic( Ashley's pic!!). U should definitely get it!!!!

I just want 2 say how happy i was when i received my o-town calendar. It was a lot better than i thought it would b and it came really quick. I've made my mate well jealous as she wantsme 2 now order her 1. Thank u so much for me bing able 2 order it as the shops in england r (bad) and don't stock it.O-town r fab!!!

otown is awesume their self an the calender is just another item u can get to show u love em'

I bougth this Calendar and it is great. I love the guys and the pictures are hot. Buy it if you truely love O*Town and what they do. Ashley, Dan, Jacob, Trevor and Erik are the best.

If you're a real fan of O-Town, Lou Pearlman's newest pop sensation, you won't want to miss this great 2002 calendar with beautiful pictures. These pictures have never been seen anywhere else! The calendar starts in September so you'll be ready for school. If you're a truly #1 die-hard fan, you'll buy it and love it!

Despite the widespread controversy surrounding the outsourcing of information security, organizations must understand and consider what costs and benefits are incurred and gained, respectively. Author C. Warren Axelrod has done an outstanding job of presenting the controversy surrounding the intersection of the two most dynamic, difficult, and controversial areas of information technology today, namely, outsourcing and security.

Axelrod begins this book by defining the scope of the treatment of the joint topics of outsourcing and security. Next, the author lays out the range of information security risk that are confronted daily, whether an activity is outsourced or not. Then, he looks at the risk of outsourcing. In addition, the author describes in detail the categories of costs and benefits. He also describes how the outsourcing costs and benefits relate to the Request for Information (RFI) and Request for Proposal (RFP) processes. Then, he looks at the outsourcing evaluation process that takes place once the information has been collected and sorted. The author then delves into the specific security considerations that affect the outsourcing decision and how they should be handled. Finally, he summarizes the full flow of the outsourcing evaluation and decision processes.

With the preceding in mind, the author has done an excellent job of presenting how outsourcing opportunities have become a continuous process as new services become available, new services of those services appear, and business takes on more of a global aspect. At the end of the day, it behooves a nimble organization in a competitive market to keep its outsourcing options open and its ability to evaluate choices finely tuned..

There are a bunch of reasons to outsource information security. You can get specialists who have a broader range of experience than your own company. You can get an outside view of everything from how to read the various logs your system puts out to what anti-virus program to install. There may be a cost savings to have someone else be monitoring your systems along with several other companies at the same time.

There are a bunch of reasons that you don't want to outsource information security. When it hits the fan, you are still the one responsible (especially so now with Sarbanes-Oxley in force, the real rules of which we still do not understand and won't until it's been to court a few times). You have more control over your own people, and you can much more carefully monitor them. This is especially true if the outside company has reduced its cost by establishing the monitoring center in some place like India. You can much more easily check to see if your new employee has just come from a few years vacation in Marion, Illinois.

It would be interesting to see how outsourcing information security would be treated by upper management. It's a cinch that they wouldn't understand enough to make a valid decision. You have to make the decision yourself, and unfortunately then you have to live with it.

This book is just about the only one on this subject. The author reports on some good situations, and some that didn't turn out so well. If this is a decision you have to make, here's at least a good start.

This book provides a great overview of the issues surrounding the decision to outsource information security and also gets into specific issues and recommendations chapter by chapter. Outsourcing Information Security is written clearly and concisely; making it easy to read given the depth and sophistication of the subject matter covered.

The author is truly an expert and shares important anecdotes from his own experiences that all can learn from. This is not a sugar-coated diatribe about the bliss of outsourcing, nor is it a condemnation of companies that use these strategies. This work gets to the heart of the matter from a balanced and measured point of view; leaving the reader to decide for him or herself, if they should consider outsourcing information security.

I would highly recommend this book for anyone who is interested in this subject and is responsible for making key technology decisions on behalf of their organizations.

When it comes to the outsourcing of information security functions specifically, the situation is even worse. Far too few organizations know the inherent risks involved with outsourcing security, and don't properly investigate what they are getting into. The same company that makes it nearly impossible for an employee to enter the office supply closet to get much needed toner cartridge will outsource their intrusion detection, email and firewall systems without a blink.

One of the many reasons companies turn to security outsourcing and managed security services providers (MSSP) is to use their limited internal security staff for more interesting areas such as web development, VPN and e-commerce applications. They will then outsource the boring activities such as firewall and IDS monitoring and maintenance to a MSSP.

Given that activities such as firewall monitoring and administering an IDS in large enterprise requires 24/7 support, it is not unusual for a company to want to outsource such activities; monitoring and administering are not core functions of most organizations.

The trouble comes from the lack of due care often given to choosing a MSSP. With that, Outsourcing Information Security is a long-overdue book that asks the questions that are necessary before an organization decides to outsource any information security function.

The author's general tone is against the outsourcing of information security; but provides readers with the various benefits and risks involved in outsourcing security, and let's them ultimate decide if outsourcing security is right for their organization. It is the reader who must define, evaluate and manage those risks and determine if outsourcing is a viable solution. These include technology, business and legal risks.

The book comprises nine chapters and three appendices totaling a bit under 250 pages. The first two chapters provide a good introduction to and overview of outsourcing and information security, and the associated security risks.

Chapter 3 details various reasons why outsourcing information security makes sense. The chapter includes various tables and references to the many reasons why a company would want to outsource security.

Chapter 4 takes the other side and analyzes the risks of outsourcing. The chapter details the traditional risks, in addition to other factors such as hidden costs, broken promises, phantom benefits and more. The book shows that while many organizations hand over information security responsibility to their MSSP, when things go wrong, they can't effectively blame the MSSP. When things go wrong -- and they will -- all of the fingers in the world can be pointed at the MSSP, but the ultimate responsibility falls on the organization itself. With outsourced security, if something goes wrong, those fingers will point back to the company's security manager, not the incompetent firewall administrator in Bangalore.

The chapter provides a balanced look at the risk of outsourcing, and while calm in its overall approach, the chapter should at least make the person considering outsourcing information security think twice. In fact, the author concludes the chapter by stating "when all of the risks of outsourcing are considered, one wonders how anyone ever makes the decision to use a third party." Nonetheless, there is plenty of evidence that many security activities are indeed outsourced to MSSP, and are often satisfactory from both the buyer's and seller's perspective.

Chapters 5 and 6 provide a thorough summary of the costs and benefits of outsourcing, and provides a method with which to categorize them. The chapter is well suited for a CFO with its discussion of direct vs. indirect costs, controllable vs. non-controllable costs, and much more. These two chapters show that creating meaningful financial numbers to see if outsourcing makes financial sense is not such an easy task. It is important to understand that outsourcing sometimes makes financial sense, but certainly not all the time. For those organizations that don't crunch the numbers seriously at the beginning, these costs can later come back to haunt them in a big way.

Chapters 7 and 8 detail the processes involved in commencing an outsourcing project, from requirements gathering to placing policy against the outsourced company. A mistake many organizations make is failure to ensure that the MSSP is abiding by the client's information security policies, rather than their own.

Similarly, one of the most overlooked areas of outsourcing information security functionality is regulation. A U.S. company may be under numerous regulations, from HIPAA to Sarbanes-Oxley, GLBA, SEC and more; when they outsource their security functionality, the remote technician may not be under the jurisdiction of the SEC; but the corporate data still must be protected according to those regulations.

The main part of the book concludes with chapter 9, which provides a 20-step process to determine if an outsourced security solution is appropriate. In seven pages, the author specifies the various events, tasks and steps that make up the typical outsourcing project.

Appendix A provides a breakdown of the various services that can be outsourced, with Appendices B & C providing brief histories of IT Outsourcing and Information Security.

The only downside to the book is its $85.00 price, which is at the high-end for technology and business books. While the price is high, the book is a huge value for anyone considering outsourcing security. The book asks the questions that are often never asked, and details how the outsourcing of information security is not the slam-dunk that the MSSPs often portray it to be.

For those who know what their security issues are and look to outsource their security functionality to a trusted MSSP, Outsourcing Information Security shows how it can be done. On the other side, for those who are drunk with the panacea that outsourcing security is supposed to provide, Outsourcing Information Security will be a sobering wake-up call.

There are a bunch of reasons to outsource information security. You can get specialists who have a broader range of experience than your own company. You can get an outside view of everything from how to read the various logs your system puts out to what anti-virus program to install. There may be a cost savings to have someone else be monitoring your systems along with several other companies at the same time.

There are a bunch of reasons that you don't want to outsource information security. When it hits the fan, you are still the one responsible (especially so now with Sarbanes-Oxley in force, the real rules of which we still do not understand and won't until it's been to court a few times). You have more control over your own people, and you can much more carefully monitor them. This is especially true if the outside company has reduced its cost by establishing the monitoring center in some place like India. You can much more easily check to see if your new employee has just come from a few years vacation in Marion, Illinois.

It would be interesting to see how outsourcing information security would be treated by upper management. It's a cinch that they wouldn't understand enough to make a valid decision. You have to make the decision yourself, and unfortunately then you have to live with it.

This book is just about the only one on this subject. The author reports on some good situations, and some that didn't turn out so well. If this is a decision you have to make, here's at least a good start.

John Day has created a master technical work on the theory of networking for our consideration. This is the most instructive and intriguing book on the subject I have read since Uyless Black's "OSI: A Model for Computer Communications Standards".

John's book is informative both on a technical basis and a sociological one. In it he explains much about the history of standards in both the Internet protocols and the OSI standards. I have been involved in standards work and have seen the dynamics he describes, and thoroughly enjoyed this telling of the history of how we got to where we are today.

On the technical side, I think his recursive "one-layer" model is elegant (The Distributed IPC Facility, DIF). To me it encapsulates what we see happening in all layers -- that is they all seem, at some point, to borrow from the requirements of others to perform their services.

I especially enjoyed the scalability and ability to tailor implied by separating mechanism from policy. Some other key elements were the emphasis that addresses much change from physical to logical at least once; that we need to distinguish between topological address, node address, and application address; that there is a continuum of function between connection oriented and connectionless messaging and how they can change roles from one DIF to another in the goal of achieving the desired Quality of Service (QOS). What matters most is that the Application can convey the needs of QOS along with a message so that the DIFs can affect the appropriate and optimal transfer.

I heartily recommend this book for anyone working in applying network communications to new application areas and especially those involved in standards work.

Thanks, John for a great read.

Students of network architecture and teachers assigning reading will find PATTERNS IN NETWORK ARCHITECTURE an excellent survey which takes a different approach to solving network architecture issues. Seven basic, still unanswered, questions identified during the ARPANET's development reveals protocols, patterns, and common conflicts. The result is an outstanding guide for any advanced networking computer library.

Prof. Day does a wonderful job decomposing, analyzing and reconstructing Internetworking (and the Internet) to plainly expose the good, the bad and the ugly. He colors the discussion with his insights and opinions concerning the decisions that went into creating the Internet from arpanet, although at times his color tastes of ax grinding.

The book is didactic, reading like a text book (although it probably will not see the light of day in university classrooms in its current guise). The style may put some readers off, but it is worth laboring through as the nuggets of truth and wisdom are worth the effort.

As a professional network architect, I strongly recommend this book to my peers as well as to educators currently teaching data networking and related topics.

In Patterns in Network Architecture, John Day has challenged the community of computer science to be truely a science by understanding the theory behind networking. The study of computer technology is abreviated by focusing on minor repairs to a system that may have fundamental flaws. Day encourages us to understand how we came to our present technology. Only through understanding of the underlying theories do we have any chance of moving toward a better, and possibly necessary, theory and practice.

When it comes to the kind of people involved in computer networks, there are four different types; the architects, engineers, IT professionals, and the end users. The architects design, the engineers build and maintain, the IT professionals configure for the unique business purpose, and the users work on it. This book is written by an architect for architects (and engineers aspiring to be architects). I'm doing this review with the perspective of someone who works mostly as an IT professional but spends about 35% as an engineer.

With many endeavors, it is easy to focus on the short-term with little or no emphasis on the long-term. John Day, as seen through this book, has both the unique experiences of designing and addressing very specific technical topics but also standing back and looking at how networks have evolved in perspective historically and where they need to go. This kind of work is indeed extremely important as our world becomes more interconnected every day, knocking down communication barriers and making more critical information available to people everywhere. We need to closely examine where and why the Internet has ended up where it is today so we can make the best long-term decisions for the future and that is exactly what John Day does in Patterns in Network Architecture.

This is very technical book that brings detailed processes together through both history and theoretical patterns. I can see this book being used in educational environments concerned with network architecture design (103 level classes) and organizations that place a high amount of significance on practical theory. I'm giving this book a five because of the amount of detail it covers and the flow he keeps throughout the book. Most writers covering this type of information get lost in the logistics but I felt like I was engaged at a lecture (instead of studying after a lecture).

Came when expected and was in great condition.

This textbook is a wealth of information on what is normal and what is not. It has extensive and readable text, appropriate pictures, and a self-assessment at the end. The reader can even apply for continuing education credits for taking the test! I hvae recommended this text to the nurses at the hospital where I work, and they all agree that it is a valuable and affordable reference.

This is so much cheaper than I could have purchased in the UK.
This is an excellent text for anyone considering examination of the newborn. I would recommend this to midwives everywhere.

This is a required textbook for my PNP program, and it is great! :) Definitely one that I will resource frequently in the field! Also, I saved money by buying through Amazon. It may take a couple of weeks to get it, but if you can wait that long, well worth it!

This book is a thorough and excellent guide to accessing the newborn. There is a comprehensive test at the end that serves to reinforce learning and can help with your ceu's!

With so many business strategy books, it's easy to get lost among them. Pieces for Profit is an easy read that does a "deeper dive" than other strategy books such as Good to Great, Execution, or Who Moved My Cheese. It's the best business strategy book I've ever read. Yeghiaian does a great job providing details for all concepts presented in a format that any CEO or leader can immediately put into practice to achieve organizational success. Presented as 3 simple pieces -- Strategy, People and Customers -- this book should not merely sit on a book shelf, it can and should be used as a roadmap for greater profitability.

Integrating business strategies, people and customers doesn't need to be rocket science, and David Yeghiaian provides an understandable description of how to do things right. "Pieces for Profit" illustrates the correlation between key components of business success without burdening us with unreadable narrative. A valuable resource for beginning business students all the way through senior executives.

This book creates a stunning view into the way a business should be by showing ways to solve real life business issues concerning strategy, people and customers. More importantly how to combine the three and create not just an immediately rich company, but a sustainable organization focused on long-term wealth, achievement and profit. Two thumbs up for Pieces for Profit.

Pieces for Profit All the pieces of this puzzle make sense. Up until now, there hasn't been a way of directly linking all the components together (strategy, people and customers). Without this knowledge, many companies focus on one part of the business. Then the spotlight shifts to another area while neglecting the previous. And on the cycle continues. Yeghiaian's step-by-step approach explains how the parts interact and guides the reader toward balance - a good fit.

Yeghiaian's name might be difficult to pronounce, but there is nothing difficult to understand in this informative book detailing a holistic approach to business. The delivery and concepts are strong with real world examples sprinkled in for practical implementation. Yeghiaian's approach of including strategy, people and customers made me realize that in my business, as hard as I work on improving any two of these, there is a way to make all three work effectively together, for optimal profitability. Just a fantastic, practical business -- no organizational -- success book.