Telecom Crash Course (McGraw-Hill Telecom Portable Consultant) [Paperback]

I purchased this book mostly to learn about telephony. I already know a lot about data networking, and I wanted to expand my knowledge of other aspects of telecom and optical WAN technologies like SONET and SDH. I knew I was in for trouble after reading about 50 pages. Have you ever read a technical book where you had a really hard time absorbing the info, even when you re-read the same paragraphs over and over again? Well, chances are it's not your fault, it's the author's! I can say this for sure about this book, b/c it described stuff that I already know about, and after reading it, I was more confused than before!

Part of the problem is the author's complete lack of organizational logic. On page 2, he describes all of the "techno-jargon" that permeates the telecom industry, and "often gets in the way of the relatively straightforward task of learning how all this stuff actually works". I totally agree, jargon should not obfuscate. BUT, if you're going to point out this common pitfall, you best avoid it yourself, and Shepard does not! He's all over the board, dropping terms and concepts with little or no explanation. About 10 pages in, it's already a muddled mess.

The mess gets worse. He discusses all of these different approaches to multiplexing, but doesn't take the time to explain what the basic process of multiplexing is all about until page 200! Throughout the entire book, he constantly refers to switching versus routing, but he doesn't explain the basic processes until the final 2 pages! These are just a couple examples that stuck out in my mind.

To be sure, there is some useful information to be gleaned here, but it's hard to sort out from all the "noise". Shepard gets into way too much detail on certain subjects and not enough on others, without any discernable logic. For example, he spends several pages discussing how fiber cables are manufactured, but spends less than one page discussing the basic processes of routing and switching. However, given the topic of the book, isn't the latter subject a lot more applicable? As far as I know, telecom professionals don't need to make the actual fiber cables.

This book is too technical for someone who doesn't know anything about telecom, and it's not practical enough for someone who knows a lot. If you're in between like me, you stand to gain a decent high-level overview of the industry, but the details are murky at best.

I won't say this book is worthless, because he does have a marketer's flair for making business sense of technology and predicting trends, and there is probably enough material here to fill a few good magazine articles. One of them, on the psychology of computer hacking (inserted in the middle of a discussion of the OSI protocol stack), unfortunately has nothing to do with telecom. Also, the mini-Esperanto/English dictionary is entertaining but probably should have been left for the author's web site. I mean, I agree that's funny, but there are those of us who paid for a book on telecom.