Professional Books

OO design and analysis is so very gray. No book can cover every aspect because the possibilities are endless. Everyone's application and environment is different which causes each and every one of us to approach our design differently and value different affects of our coding practices. By far this is the best book I have read that simply lays out OO rules-of-thumb and then explains why each is beneficial and when they might contradict other rules-of-thumb. The book encourages the reader to be reasonable and practical in your application of OO best practices.

I strongly recommend that every development team read this book and discuss it amongst themselves.

Ok, I had to look up heuristics in the dictionary before buying this. But other than that I found this to be one of only a handful I've read that tells you how to look at OOD work you've done and decide if it is good (and how to improve it). Particularly good was the discussion of cases where design goals conflict and how to resolve the conflict.

Regrettably, I disagree with the other reviewers here who seem to have liked this book. I didn't. Not that it's terrible: I found myself in agreement with most if not all of the rules of thumb the author talks about; the problem is more that this book is not well done.

First, this is a textbook; as such it is aimed at a student, that is someone who doesn't know the material yet and tries to learn. But for a tutorial this text overwordy and imprecise, with a generous quantity of confusing, misleading metaphors. If you happen to know what the author is trying to say, then you sorta get it -- I mean, you get it 'cause you already know it -- but a newcomer will be confused.

Sometimes the author doesn't seem to know why a particular rule is good, so he goes something like this: rule such-and-such is good because most software engineers would agree that it's good. I doubt the author conducted a statistically valid survey -- but forget that, suppose most software engineers do in fact agree: so what? All the author has now is a nice and juicy ad populum. But he, obviously, isn't even aware that something's wrong -- and that may be one of the problems with this book: the author may not be experienced enough to write books of this sort. He may be a competent practitioner, but this is not the same as teacher.

He tries to compensate via an over-abstract and smart-sounding terminology (one of the reviewers below jokingly complains that he needed to look up the word "heuristics": that is a telling comment, and it is valid. I, too, noticed that the author takes delight in using a dozen hifalutin words where one simple word would do (and result in a clearer text).

Riel also likes to belabour commonplace excessively ("data should be hidden inside objects"; "Objects should not depend on their users", blah-blah, brush teeth daily, apple a day etc.), anything to make the book thicker -- which brings me to its second defect, less important and quite a common one today: the book is blatantly padded. Out of about 400 pages only about 200 have readable text; the rest is mostly a source code printout (this code could have been supplied on an attached disk or put on the net somewhere). There's also a few pages with a concise restatement of the author's rules, which could have been printed on the cover insides (like in the Stevens network books) or supplied as a pullout; otherwise this list is hard to find and serves no purpose.

To summarize: were it better written, Heuristics could be useful for a newbie, but it's not and so it isn't. A more experienced reader, despite being annoyed, will understand it -- but only because he already knows the stuff himself and will be recognizing rather than learning. YMMV, but in my opinion this tome isn't worth reading time for any reader, new or experienced. I'm sending it back.

I have plenty of books on patterns, but I want to get more information on the basics of OOP and why the patterns are effective instead of "this is pattern X, and this what it does." This is a very complicated subject, which I have no doubt that most programmers on the planet have very little understanding of. We mostly write crummy code that "works", and most of the time that's good enough.

I was uncertain about getting this book because of how old it was, but after reading most of it, I'm happy I got it. Although complex, it is written in an understandable manner with useful diagrams. I wasn't as interested in the "one-liner" heuristics as I was the detailed explanations of the problems caused by particular design mistakes and the other examples and pitfalls presented.

I have been studying the object oriented methodology for some time now. I felt that I had a good understanding of what OOP was all about. I have studied OOA/D and design patterns from numerous sources. All of my sense for OOA/D knowledge changed completely when I read this book. This book really showed me that I was stuck somewhere in the middle of the paradigm shift between action oriented programming (aka procedural programming) and object oriented programming. After reading this, I feel like my knowledge in OOA/D has truly advanced to the next level.

Are you the type of person that knows what OOP is? I mean, if you've studied up on OOP then you are probably aware of what an abstract class is. You know what interfaces, inheritance, polymorphism, information hiding (...etc) are. You may have a sense in when you should use inheritance and when you should use containment. You probably follow certain OOP practices like keeping all of your variables private, hiding secrets from other objects (information hiding). This may all make sense to you but are you also the type of person that just never feels comfortable about your designs? Do you look at your classes and just get a sense that something doesn't seem right, yet you just can't figure out what it is even if your software system is running fine? I am willing to wager that you are in the middle of a paradigm shift. You are probably taking the route that a lot of developers take when they shift from thinking in a procedural fashion (action-oriented design) into object oriented design. There is nothing wrong with this, but if you're like a lot of developers you will have a long hard journey utilizing a lot of experience before you really make that shift. This book is an essential tool that will help you make that shift a LOT faster. After reading this book you will see why you felt your designs were't quite right.

One of the first topics that really hit home for me was when the author Arthur Riel talks about God classes in chapter 3. God classes are classes that have too much implementation in them. Most of the complexity of a piece of software resides in these classes. They are the all-knowing classes that delegate messages between the much smaller, less complex classes. Signs of God classes are classes that have words in their name such as "Manager" or "System" in them. This one hit home because there are numerous classes in the software i'm working on now with the name Manager in them. For example one of our classes is called the "BiDirectional_Dataflow_Manager". This is definitely a God class through and through. While I was reading about the disadvantages of these types of classes I couldn't help but agree with everything Arthur was saying. I began to see the light already and I was just on chapter 3. There are 59 other Heuristics, all equally important in this book.

Most books that teach OOA/D seem to really only teach the definition of OOA/D and perhaps clue you in to the whole idea. You learn the terminology well and you see a few examples (I'm sure you've seen an animal hierarchy a time or two), but you don't really gain a solid understanding in how you actually think in objects. This book will bridge that gap. This is the best book i've read by far on OOA/D. This book will apply to you no matter what your skill level is in OOA/D, unless you're a complete beginner then you might find yourself a little bit lost. If you are brand new to OOA/D then you should probably read a short book on OOP, just to gain the basic concepts first. "Object Oriented Thought Process" might be a good start as it's short and sweet, then you should move on to this book. If you are advanced then you may know a lot of this information, but this book will probably help tweak your OOA/D skills; helping you become an even more solid developer. But for you guys and gals out there that know what OOP is and read a few books on it, but still don't feel quite right about your designs, this book is essential. You guys out there are the sweet spot for a book like this. That's how I was. Now I feel so much better, I feel like i've gained more knowledge in OOA/D with this book then all other books on OOA/D and OOP that i've read combined - and then some.

Arthur Riel is a very talented programmer and author. He is able to communicate ideas to you that are sure to hit home, as if he's right there with you and understands your problems in OOA/D. This book is densly packed. Not including the bibliography and index this book is a mere 367 pages. Even more, if you don't include the example code at the end of the book (all C++ code) this book is only 243 pages. The real meat of this book is in the first 9 chapters (where he talks about all of the heuristics), which totals 182 pages. After that he talks about topics such as handling memory leaks and such. Most of the dim lights will shine brightly after a mere 182 pages! This may sound too good to be true, but as I said earlier Arthur is VERY talented in communicating his ideas. You just have to read this book very carefully, don't skim! Because it's so dense, it may take a couple of passes before you really get the idea but once you understand it you will surely belt out a resounding "AH HA!". This book is 10 years old at the time of this review, but the information inside is far from being outdated.

To conclude this lengthy review (sorry about that) I would like to say that I give this book my highest recommendation. In fact, this may be the best book on software development that i've ever read! This book has influenced my software development more then any other book i've read and that's a fact. This is truly a rare gem. The only downside (not this books fault) is that it's become a bit harder to work on the software that i'm currently working with because I now see where all of the pitfalls are. My co-workers think i'm just being anal about design now, but you don't have to be like them. Step up, become the best software developer that you can be. Just read this book and you will take a giant leap forward in your OOA/D understanding, especially if you're stuck in a paradigm shift like I was. Thank you very much Arthur!

I can't recommend this book highly enough. There is a wealth of advice on best practice for both Excel and VBA, which has not only prompted me to change the way I design new projects, but to revise old projects also. There are also a huge number of examples, including an application developed throughout the course of the book, which demonstrate applications for all the techniques discussed. Definitely not for the beginner, but there's loads of stuff here for intermediate to advanced developers. I think I'll be using this as a desktop reference for a long time to come...

This book of advanced Excel development was recommended to me by a co-worker whose project I inherited that used the concepts in the book based on the "Petras Template" example. It's classy and polished VBA programming and sure, you can brag about the concepts to the techies interviewing you during your next job hunt.

But, be careful.

The book introduces us to the concept of add-ins and templates. So, there you are showing off your project to your manager or users. But, what do they click on? The add-in or the template? What are all those true/false cells over there? How can the user save the workbook? What heppens if you forget to hide the columns that use cell logic. Hmmm. These questions and others will be asked of your typically non-technical users who have NO idea what goes on behind the scenes. If they open up the template and screw around with the code or re-name the add-in, you'll have chaos.

To be fair, there's tons of advanced concepts to learn here and no doubt you'll benefit from them. But, remember, as a developer, your first goal is to produce a robust application. However, you may have click a couple of functions to get all tabs in your template to show. If you don't do that, you can't see them! Oh, and don't forget to save your add-in.xla or all your changes won't take effect.

Not for beginners or dummies, but for VERY careful developers!

This is a great book for power programmers. But be aware, this book is not for those who want to learn Excel. It's just for those who know Excel and want to imrove their programming capabilities.

When picking up this book, I was an advanced Excel user. Having discovered most of its features by trial-and-error, and coming from a fairly solid programming background, I understood well the interaction between the underlying object model and the sheets appearing on the screen to end users. I have also crafted many sophisticated worksheet formulas, and explored just about every suggestion of literature such as "Excel Hacks" and "Advanced Excel Report Development".

Professional Excel Development offers ideas and tools necessary for designing full-fledged, robust Excel-based applications. It does not spend time explaining how various features work, but rather goes into detail on how to put these features to best use.

Here is what I picked up from this book, together with the authors' Excel 2003 VBA reference:
* ways to leverage Excel's built-in features to avoid excessive coding
* advanced design techniques for using Excel as a WYSIWYG interface designer
* techniques for creating custom menu bars and programming their behavior
* various means of interacting with the user and simplifying their sessions by providing guidance as to which steps need to be taken
* restricting the Excel environment to take on the appearance of a product condusive of the goal stated in previous bullet
* using VBA in conjunction with the Excel object model to create powerful object-oriented structures for spreadsheet-based applications
* programming Excel-based solutions in an executable to provide a more standalone application
* using Windows API calls to increase robustness of the application

One key feature of this book is its consistent approach. The authors maintain a consistent structure, using the same application throughout the book for their "practical example" to demonstrate new features made available through the material in each chapter. Also, the "best practices" approach provides a level of consistency that is generally desired of anywhat sophisticated applications. Useable modules are provided on the accompanying CD, ready to be used in readers' own applications.

In the beginning, the authors explain the audiences for which this book may or may not be intended. They separate these into users, power users, VBA developers, Excel developers, and professional developers. The latter three categories of users will benefit the most from this book, each in his/her own way. VBA developers will learn how to use built-in features (I think this is where I started); Excel developers will learn how to incorporate Excel-based solutions into larger applications; Professional developers will be exposed to a great variety of "best practices", optimization techniques, and various other means for developing consistency in Excel applications.

If you do not fall into the latter three categories, you might not pick up much from this book. It is not useless to you, however; you can still find many worksheet/userform design techniques, and get an introduction to the kind of power VBA-based programming can offer. Nonetheless, you may be well-advised to start off with something simpler, such as John Walkenbach's Excel Power Programming (as alluded to by the authors of this book), simply because the present book assumes a good degree of knowledge and leaves much for the reader to figure out from the fully-functional examples provided - thereby covering the ground that it does.

Overall, this book makes for a wonderful reference to the various under-the-hood features of Excel. Even if you've already encountered many of the techniques described, and could technically discover them further on your own, it is useful to have them readily available in a single collection. Very few items are left out; application design, object-oriented programming techniques, database applications, debugging techniques, Office automation, and external interop are all covered here. Professional Excel Development is a solid reference to be consulted for years to come.

When you search the web and most of the books around, you can find solution to your problems most of the time, but you are rarely sure it was the best way to do it and how it would fit to the rest of your code. The authors of this book are not afraid to tell what they suppose to be the best for you, along with full featured versions of code illustrating each chapter.

I found it easy to take the code from a sufficiently leveled chapter and adapt it to get just the application that I needed, knowing it would be fast, clean and complete at the same time, although I didn't understand all the details at first. Now, the book serves as a widely findable documentation for the packages that I make. Highly recommendable.

This book is a must have for people starting a business. I haven't entered ANY business venture without first consulting with this book. I also had the wonderful opportunity to learn with Ed Rogoff himself, he is a very knowledgeable, straight-forward man, and his book is 100% reflective of his real life traits and experience. Great Job Ed!



Elkin

Ed Rogoff has written a must buy for those planning on starting or expanding their business. He takes you through a step-by-step plan from your initial idea to your grand opening. Examples, forms and common pitfalls are all covered in an easy to follow system. If you want to make your dream a reality, "Bankable Business Plans" will get you started.

Chapter 10 in this book opened my eyes to a publication produced each year by the Risk Management Association (RMA). It's called the "Annual Statement Studies - Financial Ratio Benchmarks" and is a compilation of information supplied by member banking institutions that get their information from small business loan applicants. The author of Bankable BPs says a sound business plan must favorably compare to the information in the RMA publication, or it probably will not help the loan applicant get her funds.

I recommend after reading Bankable BPs that anyone creating a business plan will do themselves a favor by examining the RMA publication to use as a guide for creating meticulous financial projections included in their business plan. Don't write the business plan first, and then compare it to the RMA publication figures. Instead start with the figures and then write the business plan.

Another similar (but not as good) publication you might want to look at is called "Financial Studies of Small Business" written by Financial Research Associates.

Besides the impressive information contained in Chapter 10 of Bankable BPs, I thought the book was a great read on the subject of putting together a business plan. The author is an associate professor at one of the CUNY schools in New York. I would have liked the book better if he had not emphasized that a business plan was a tool to help raise capital. But he does point out that a business plan is an important tool for running a small business, too.

The author listed 10 action steps necessary to create a business plan:

1. Define the business
2. Figure out initial needs
3. Outline how the business expects to make money (business model)
4. Perform market research (study industry, competitors, and potential customers)
5. Write a marketing plan
6. Describe sales effort as it relates to marketing
7. Systematize operations & team building
8. Decide on capital requirements
9. Put together pro forma financials
10. Write the business plan in an acceptable format

I'm pretty sure the author felt the action steps were meant to be done in the above order. I tend to agree with the list of action steps, but not the particular order. I think #8 and #2 should be sequenced just after #9. I find it hard to believe it is possible to decide on capital resources BEFORE you have figured out the pro forma financials. And, without knowing the capital resources needed, it seems to me it is hard to determine what the initial needs of the business will be.

All in all, this was a very informative books and I am sure it will be a very helpful book to anyone who has to put together a business plan. 5 stars!

Ed Rogoff gives an in depth but workable plan for developing a new business. "Bankable Business Plans" gives you what you need to go from your initial idea to your financial source. Examples, forms and step-by-step instructions are included in this comprehensive book. This book is a must for business owners of any size business.

This book is terrific because it directly addresses the issue that probably undermines more business plans than any other: unrealistic assumptions. After 20 years as a banker and financial advisor to growth companies, both large and small, I believe that professional equity investors judge entrepreneurs by their ideas, their ability, and the reasonableness of their assumptions. Aggressive business plan assumptions raise significant doubts in the minds of investors, who don't just want 25% IRRs but want 25% IRRs that are achievable. Rogoff wisely advises entrepreneurs to ground their plans in reality, using solid industry data and benchmarking techniques. He teaches you to think like an investor or banker before writing your plan. Very solid advice. A must-read before going to market with your plan.

If you have a colleague who's just starting out, this book is a great way to break the tension that's sure to fill a first year of teaching. John Pearson does a wonderful job of taking us through the ups and downs! Very fun read.

Mr. Woodson: Drew, how did you like my book?
Drew: I liked it.
Mr. Woodson: Really?
Drew: I really liked it?
Mr. Woodson: Really?
Drew: I loved it?
Mr. Woodson: Really?
Drew: I really loved it?
Mr. Woodson: Really?
Drew: Yes, REALLY!!!

What an entertainly addictive read. We teachers hear so much everyday, and it's a joy to see someone share our reality.

Drew in Floresville

This book is a sort of "Sideway Stories from Wayside School" for teachers.
Keep a copy in the teacher's lounge for some needed comic relief.
It's a good 'read-a-loud' book for those stressful days.

What a fantastic and funny look at what it's like to teach these days. John really captures the humor and the heartache that comes with teaching these days. This is a good book for anyone who teaches or has kids...and better yet, for any politician hoping to make laws about education! I think a day or two with Lucifer might make them reevaluate things!

I taught in DISD for 14 years. I left the district 3 years ago and currently teach in Anchorage, Alaska. I missed DISD so much and all that I went through there. When I found John's "Learn me Good" blog through the Dallas Morning News website I was so excited to see that I could follow DISD teachers all the way from Alaska. Well it got to the point that I couldn't wait to get my daily emails from his blog and laugh.

I finally decided to get the book LEARN ME GOOD and see what it was all about. Well, from beginning to the very end he had me cracking up. He brought me back to my days in the classroom in Dallas. I could relive some of the stuff I had to go through. If you plan on becoming a teacher at all in a urban setting, this is the book to read. Keep it also after you finish reading it so as you are dealing with the stresses of teaching you can open it up and see that someone else went and is going through some of the insanity of everyday teaching. This is a book for every teacher. I am still smiling from reading it-Great Job John!!! :)

(An earlier review may also appear after trying to merge and update an older acct with a new acct.) ...I picked this volume up at TechEd 2001. It maintains its relevancy four years later. The competition between related books brought the race down to "McGraw-Hill's Encyclopedia of Networking & Telecommunications" winning by one length over the "Microsoft Encyclopedia of Networking".
Tom Sheldon provided the most well-grounded and well-rounded information to fulfill the title of an "encyclopedia of networking" compared to Mitch Tulloch's very good but more Microsofted (I think microsoft as a verb can now come into play) approach to the subject and its fields.
Sheldon's book contains a greater variety of entries and their corresponding information (i.e. terms/acronyms like "NSA" & "PKI") instead of a namebrand focused presentation. I would like to see a "Special Characters" index category like Tulloch's book has, but this is not as necessary when using the search capability of the book's CD edition (which is included and loaded with hyperlinks to outside information sources).
I highly recommend Tom Sheldon's book. It's user-friendly layout and design are easy on the eyes, and I'm glad to have it at my desk (when I'm able to return it there after tracking down who last borrowed it).

I stumbled accross the old 2nd edition in our library and a day later I was in awe of Mr Sheldons fantatistic book. Unlike most networking books their is no waffle in this one. His style of writing disects networking information into logical digestible chunks. The second edition can be downloaded from his site but I recommend you getting your hands on the latest edition if possile because it is more upto date and has lots of new additions. This book is a one stop shop for everything you need to know about networking and a priceless resource for any networking student.

Firstly I'd like to say...Thanks Tom, for helping to keep me in a job! Up until recently I worked as a Network Administrator in Sydney and believe me, your books saved my bacon on more than a few occasions! I first received the electronic edition of the Encyclopedia of Networking whilst studying Computer Technology and e-business in Sydney. The encyclopedia was included as part of the overall course and many references were made in the college's learning guides to certain chapters when more detailed information was necessary on a particular topic. I'm currently involved in the area of Multimedia and Telecommunications and recently obtained a copy of the latest edition, The Encyclopedia of Networking and Telecommunications and am amazed at how much extra and updated information has been included. I keep the book close by at all times and find myself referring to it quite regularly. I could now honestly say that it's become my IT bible! It covers all aspects of networking, the Internet, Electronic Communication, topologies, protocols, security and various configurations in absolute and thorough detail. The encyclopedia also comes with a CD that can be loaded onto your computer as a PDF file and the search facility works brilliantly. I must say that if anyone is involved in, or wants to know anything about Networking and Telecommunications this book is an absolute must! Personally, I can't see how I could do my job without it. Thanks a million Tom! ...John Botica

Tom Sheldon can capture the core of a hard to read, multi-hundred page networking book in less than a couple of pages. Crystal clear definitions, well structured text and diagrams, plus excellent cross-references make his "Encyclopedia of Networking" a huge time saver for any networking professional. Manuel Vexler, Certified Network Engineer

I work for an ISP in the Upstate NY area in 2nd level Internet support. I have found this book to be a very handy and comprehensive reference on Networking technologies. We are also an ILEC and I am impressed with how well this reference covers terms or acronyms that I am unfamiliar with when dealing with this side of the business. Great job Tom! Keep up the good work.

This book not only deals with the issues of attachment and other developmental issues of the adoptive child, but it gives you practical strategies to overcome and deal with them. This book is very inlightning, but offers hope to parents of hurt children.

I thought this book provided valuable insights and gave good real life examples. I would recommend this book for anyone adopting an older child.

This book contained things that I think all parents should know about dealing with kids and thier baggage. I have refered back to this when dealing with situations with my special needs child, if only to know that I am not alone in my struggles.

This book was very helpful. It helped me even though I haven't ever adopted. It helped me understand hurting kids more. I will buy this book! I would like to adopt older kids when I'm married. Besides I have known several foster/adopted kids. It helped me understand them.

I read this book twice I liked it so much. I found many books minimized the struggle of raising adopted children and focussed too much on only the positive. Although I have not raised any adopted children myself I do plan on it after I finish university. After reading many books I knew it couldn't be as flowery as they put it. Although I am sure no book could truly prepare anyone for the realities of raising childeren it can help you understand where things are comming from. If nothing else I have a greater respect for the adoptive family because of this book!!!

He is my favorite author when it comes in coding. Very systematic and structured. C++ templates is not yet a mature domain and it is not that easy to program. Still this book presents very well the theory and the implementation with plenty of examples and warnings about the traps of C++ programming. If you are into theory math, physics you will appreciate the smartness and completeness of templates. Check also other books from the author The C++ Standard Library: A Tutorial and Reference, Object Oriented Programming in C++

This is best book on C++ templates. C++ programmers who wants to learn modern template programming should start reading this book first, no more no less.

Vandevoorde and Josuttis have written by far the best book on C++ templates. Theirs is literally the only work out there that makes any sense of the utter mess that is C++ template programming. Absolutely essential for anyone using the STL or (especially) Boost libraries.

I like all those description and examples: the topic may be complex, but really an interesting thing when enjoying it slowly.

I used the book when I was working on templates. Book is very clear and concise with proper layout of chapters. I was able to read relevant sections and get clear understanding. It is possible to get all information by reading C++ specs and other sources, but having this one book is a real time saver.

If you work on templates and have some doubts ever then have this book next to you.

Kelly writes in a compelling way creating parallells and connections between him winning the various tasks on The Apprentice and his military experience. I like his style and his sense of taking responsibility even when things go wrong. Humility is deifinetely a trait a leader must develop!

I found the book a pleasant read and I liked the fact Kelly was talking a lot about the lessons he learnt in life and how these experiences enabled him to move on.

I grew up with some idea of what military life was like due to my Dad being in the Navy - but I must admit it's never held a lot of interest for me. Reading Kelly's book did actually shed a whole new light on what advantages military service can bring to other aspects of someone's life. The principles that are discussed in the book (Duty, Impeccability, Passion, Perseverance, Planning, Teamwork, Loyalty, Flexibility, Selfless Service and Integrity) are all really worthy reading for anyone in business and the military slant I found surprisingly gave it more bite and interest.

This is a great book that draws comparisons between Kelly's military service and his rise through the entrepreneurial ranks. I know Kelly personally, and he is not only a successfull businessman, he is also a devout humanitarian. Highly recommended!

I recently purchased "Take Command" for a college course. I chose this book because I am a fan of the television show "The Apprentice." I could not have picked a better book to read before I graduate and re-enter the business world.

The ten principles that Kelly Perdew learned while attending West Point can be used by anyone who wants to get the most out of life. Duty, Impeccability, Passion, Perserverance, Planning, Teamwork, Loyalty, Flexibility, Selfless Service and Integrity. I plan to use these principle's to be a strong leader in everything I do.

I always wondered how I would have handled military training. Kelly details how physical strength is only a small part of it.
I was very impressed with how Kelly got into West Point, as well as what it took to graduate. His business experience explains how to handle a loss and come back and do things better. The experience this guy has at such a young age is unbelievable!

If you are just looking for a college, read this book! If you are graduating and looking for a job, read this book! If you have been working for ten or twenty years, read this book! "Take Command" includes great stories about Donald Trump, Ross Perot and Marsha Evans to name a few. This book will teach you to be prepared for anything and to perform well under pressure or during a crisis.

Kelly Perdew details how the ten principles became second nature during his military training. Anyone can learn and use the ten principles. If you want to challenge yourself to be a strong leader in business and life, "Take Command" will put you in a position to succeed.

This book by Apprentice winner Kelly Perdew is a worthwhile read. Written in the style of many military-business leadership books, it swtiches back and forth between Perdew's Apprentice exploits and anecdotes from great military veterans turned business leaders. The stories about Perdew's career, Apprentice tasks, and about others are both inspirational and entertaining. I am giving 4 stars because he talks about principles, but does not go deep into the reader's application of them.

Nevertheless, this is a worthwhile read for both the Army or corporate officer.

I wanted to use ruby on rails for my web applications, but after some failed attempts I decided to learn a bit of the ruby programming language first. This book guided me to the language, even if you are new programmer I completely recommend it.

Every serious Ruby programmer has a copy of the venerable 'Pickaxe' (the definitive Ruby reference manual) at their disposal, but if you're just getting you're feet wet with Ruby and serious about learning it from the ground up, then Beginning Ruby is just what you need.

The tagline 'From Novice to Professional' well describes the content. But if you're looking to delve into advanced GUI programming, then this isn't for you. This book takes you into the Ruby you need to know as the foundation for helping you become a great programmer. Peter Cooper introduces you to many critical concepts that you will need to master, but does so in a logical and easy to read manner. The text is neither dry nor whimsical, but a perfect blend between reference material and hands-on tutorial.

While I had tinkered with Ruby from 2002 onward, I never gave it any real attention until I stumbled upon Ruby on Rails in 2006. When I came to the realization my programming style looked like less of a 'style' than it did a Rube Goldberg machine, it was time to get back to basics ... and thankfully this book was published.

If you're serious about looking into Ruby, now is the time to pick this book up ... then you can go get the latest edition of 'The Pickaxe'. I almost want to buy a second copy out of sheer appreciation for Peter Cooper providing a great guide to a great programming language!

Beginning Ruby is one of the easier books to following Ruby, and get a decent understanding Object Oriented Programming (OOP). If you don't want to fork the money over yet for this book like I did not knowing if I would understand (I just now have grown a big enough interest into programming to want to study), then I would suggest grabbing the book called Learn to Program from Pragmatic Programmer Series. In that book he runs through basic ruby syntax, and programs that actually function more or less like a BASIC application would. Once you finish the short yet insightful Learn to Program book, this book becomes even easier to follow. Once you make your way through this book though, you will want to more then likely purchase the Pragmatic Programmer Ruby book (The Red Pick Axe Book, which the 3rd version is due out in October). But from a novice programmer perspective, this is an amazing book and is always by my side.

I have dabbled in programming, but never really rolled up my sleeves to learn a language... until now. Both ruby and python seemed like great choices, and I looked for materials to play with them. Both offer some very nice features and the ability to get up and running with something useful and fun easily, yet offer plenty of room to grow. After a short evaluation period, I think I just like the "feel" of ruby better, but that's totally subjective. After settling on a language, I looked for a book.

I checked out Chris Pine's "Learn to Program", and of course _why's Poignant Guide to Ruby, and then this book. This one is, by a large margin, my favorite. Both Chris Pine's book and _why's guide have their moments, but in my opinion Cooper's book has a considerable edge in clarity and usefulness. It explains complex concepts in clear prose and then by example. I feel that I can tackle useful problems after having read the book. It seems to hit the sweet spot for being clear but not condescending, complex but not overwhelming. The examples are very applicable to many real-world problems.

This book is more of a tutorial than a reference, which is exactly what I needed as a new programmer. In addition to being a great ruby book, it's also one of the best "tech" books I've ever purchased. It's rare to see this level of quality in technical writing. I really hope Mr. Cooper continues to produce programming books.

I had heard quite a bit about Ruby, so I thought I would see what it had to offer. I went looking for an introductory book and found this one. I was hooked before the end of the first chapter. The author has an engaging writing style, and has done a great job of introducing the language and the community. The book is logically organized and presents the material in an easily comprehensible style. This is a great book for getting started with Ruby.

I've been in IT for over 25 years, and in that time I've read a lot of technical books. "File System Forensic Analysis" is not only the best book I have read on computer forensics, it's probably the best technical work in ANY field I've ever read. It's thoroughly researched, clearly written, and contains virtually no fluff. The numerous rave reviews it has received are well-deserved.

My only quibble is the short, but seemingly gratuitous section on hexadecimal and decimal arithmetic. If you're ready for this book, you'll already know this stuff. But, that's only a few pages in a book that's otherwise packed with real substance.

I can't say enough good things about this book and author. The material is beautifully laid out and the writing style is fluid and effortless. The author has a real talent for using metaphors and figures to illustrate elusive concepts.

All but the very rarest file systems are covered, and numerous 'screenshots' show how to use the Linux command prompt and get your hands dirty exploring disks on your own.

While this book is a gold standard for digital forensic examiners, it would also be valuable to the computer enthusiast who's interested in things such as what happens to their hard drive when they format it, exactly what happens during the boot process, etc.

I've had 3 courses in digital forensics, and this book gives an in-depth discussion of disk level concepts (HPA, FAT, MFT, etc) that were merely glossed over in my formal studies.

Great resource on file systems and file system data structures, although I wish it covered Apple's HFS+.

Thanks a lot, we are very happy to have this book in our library!

Great Book. Great job Brian. A must have in your bookshelf if you are serious about computer forensics.
It only lacks two things to be perfect: a reiserfs and a HFS+ sections.

Only an error. GPT partition schema isn't used only in big servers. New Intel Macintoshes use it by default for their boot drive.