I'd like to say you could do worse than to buy this book . . . the truth is it'd be hard to find one worse than this self tutorial travesty. In truth no book would be a better way to learn C than having this one. Mr. Corriveau has numerous programming language errors within the first 80 pages that make it impossible to run most (if not all) of his 'samples' as they are. His lecture note style organization would be difficult to follow even if the book had had a proof reading before it was released to publications. His near 800 page book is 900 lbs worth of frustration. It took an experienced C programmer to clean-up and rewrite Mr. Corriveau's sloppily written 'sample code'. In his book he states that C programming isn't for everyone . . . well certainly not the way he approaches teaching it. To sum up, it'd be challenging to find a book equally poorly written let alone one even worse.

My introduction to this book was initiated as a Information Technology Student at DeVry Institute of Technology in Dallas, Texas. While the book does present a very detailed introduction into the C programming language (including a host of examples and exercises), I feel it lacks clarity as well as structure. There are many examples that are simply "incorrect" in this book. Also, I feel the author could have done a much better job in explaining "the right way to code" instead of focusing so much on debugging techniques. Overall, I think this book is quite exhaustive, yet it does present the novice with a host of examples and exercises in C programming.

While I would agree with the previous review on it's various errors in code, I found that correcting these errors were fairly straight foward. The author presented the subject matter in a clear and consise manner and in addition added sections called "Common Errors & Traps", which I found to be be extremely helpful. The author also discusses the importance of presenting a clear and readable code. I would have liked an appendix including containing a sampling of answers to the questions posed in the book. Taken as whole, the author provided the information in an understandable format.

I don't understand why my instructor chooses this book for 3 quarters continously. This book gives you nothing. I have a feeling like the author doesn't know anything, so he uses lots of words to describe some thing that are soo obvious. With other difficult concepts, he doesn't say anything, or just a few words. Some one compared this book with Lev Landau's one. Please give me a break. Lev Landau is a great physicist, while this guy is nothing at all. I still wonder why this kind of textbook is still around. I feel frustrated with this book. My conclusion is: if you really understand physics, this book is not for you. This book is only for kids. I hope that some one could pass my message to the authors, and hope that they could write better books in the future.

This book is very bad. It includes lots of false physics theories which are just copied from other textbooks. It looks as though the authors do not have a good understanding of this subject. It hardly includes any proofs for most of their assertions. This was the first physics textbook I ever bought and I have worked hard to prove many of their theories wrong, to later find out that they are not the correct theories that more advanced textbooks teach in the first place. I seriously do not recommend this book for anybody who has a love for physics and truth. But of course, most other college level textbooks such as this one are pretty much the same. But this sort of introduction to physics is definitely not necessary for a clear understanding. I suggest you skip straight to the next level. By getting books by Griffiths or Kleppner. But if you insist on getting an introduction of this sort to physics, then it is still a good tool for the general topics discussed at college level physics.

In all fairness to the book, it's not as bad as I made it out to be below. It is a little upsetting to be given tons of equations without any proofs. But the proofs really are beyond the scope of the book. I've looked at other books of the same level since I wrote the original review, and this one has turned out to be better than all the others. The book would've been better if they mentioned a few extra things like how its treatment of electricity and magnetism should be taken as only working in an absolute frame, and is only an approximation to the full treatment.

All in all, this book covers so many topics, that no matter what physics you are doing in the future, you'll always be able to find some information in here that won't be mentioned in your other book.

It covers everything you need to know for a first mechanics course, a course in waves and modern physics, a first course in electricity and magnetism, plus a lot more that is never touched in class. Calculus is not needed for the mechanics course, but it is used in the book. If you know calculus, then you'll benefit. If you don't, you can skip the "calculus equations", and the rest of the mechanics part of the book will still all be comprehensible.

Jordan Maxwell and his colleagues Paul Tice & Alan Snow are inspired by the late C19 diffusionist writer Gerald Massey, who believed he could trace all religions back to a small number of linked cults (stellar, lunar, solar). Massey was enthused by the then quite recent decipherment of the Egyptian hieroglyphs, and merged the genuine knowledge that was emerging from Egypt with the early modern fantasies - now largely debunked - about Egyptian mystery religions of vast antiquity. Maxwell et al. themselves focus mainly on the religious issues in the usual historical revisionist manner, finding a huge number of possible links but arguing persuasively for very few. They also draw from a three-volume work published around 1940, apparently anonymously. This book has the overall title Priesthood Of The Ills and contains a large amount of non-standard philology, adduced as support for these diffusionist theories of religion. This linguistic material cannot be taken seriously: it is on the level of Guido von List's absurd philology and similar British Israelite proposals. But Maxwell et al. believe that there is a Language Conspiracy, which involves (a) keeping humanity divided by forcing many mutually unintelligible languages on us and (b) blocking us from discovering the original ('true') meanings of words. This suggests that all changes in the meanings of words are somehow illegitimate, which of course is false; but Maxwell et al. hold that the meanings of some of the key words in ancient languages were very different indeed from those of the English words normally used to translate them. This has been concealed by the forces of Evil. These 'true' meanings are implicated in huge numbers of unrecognised links between languages; but focusing on pronunciation rather than spelling will apparently do the trick: you can then hear which words are really connected, because they sound similar! (Two hundred years of historical linguistic scholarship is simply ignored.) Then you can appreciate the 'true' form of Christianity and its links with earlier religions. Maxwell et al. also make a few other unintentionally entertaining statements about language matters. If these ideas are to hold up, it must be on grounds other than linguistic!

This book is a nice read and thankfully not too overwhelmingly exhaustive. That is not to say however that it is not chopped full of presentable information. As far as whether the information J. Maxwell and his colleagues present is credible and I cannot vouch for. In other words, I don't have the credentials, but I will say that I was deeply intrigued the the relgio-cultural parallels that J. Maxwell and his contributors suggested. It is truly an incredible read! Whether the information is true or just plain bunk the reader who considers purchasing this book will be glad to know that the book is a quick read. It takes no time at all to read because the info presented is concise.

If you are into this sort of thing, trust me, you'll love this book! I enjoyed the fact that we learn about things that we generally take for granted, without knowing their origin or meaning. A brilliant and fascinating expedition into the far reaches of religious thought.

Mijksenaar provides some interesting ideas but not much depth. Very disappointing.

... it's more of a pamphlet. Mijksenaar provides some nice examples and interesting ideas, but I wanted much more. Once can read this "book" in less than an hour.

This small, profusely illustrated book is, well, a personal manifesto against bad informational design. Mijksenaar does not take prisoners: his case studies (of bad design) include glitches by some of the most prominent dutch designers. Healthy, very healthy. There are some surprises, especially if your infodesign paradigm is the London underground map. The book is also a paradox, though, in that it is itself badly designed. By that I don't mean the shape, color, printing, which are pretty, but its logical content structure, which is confusing. Because it is more of a (needed) rant against bad info design, I call it a manifesto. It is an optimistic manifesto, and Visual Function is well worth reading, if only because US designers would profit from getting to know their their dutch counterparts better.

I was somewhat surprised that any publisher would consider this text a guide. Basically, it is formatted like a dictionary with various business-related vocabulary listings and their definitions. Usage applies to the spelling and capitalization of the listings. My expectations were that this book was similar to a Chicago Manual of Style within a business writing context that includes recently created words germane to the business world. Unfortunately, it isn't useful in this regard. For example, if you want to find out how to use colloquial business language such as "leverageable", you probably won't have much luck with this text as such words appear to be absent.

...

Lastly, the organization leaves something to be desired as the usage topics such as Abbreviations are mixed in with the vocabulary entries, which essentially is the entire book. I really see very little value in acquiring this book...

If you want to know the meaning of derivative claims, leveraged buyout, offshore buying units or Brady bonds, this is the book for you.

If you need to know the definition or usage of the words Amish, tort, girl or the location of Exxon, then, by all means buy this book.

But I don't know why anyone would want to spend $30 (the standard price) for this book, put together by the Wall Street Journal's Paul R. Martin, because it is uneven, moving from the obvious (the word girl, for example), offering up tidbits of definitions of rather well-known words (the Amish) and the obscure (offshore buying units.) It is a book of multiple purposes or no clear purpose at all to the public.

Internal stylebooks sometimes suffer from a fuzziness growing out of dual purposes, meant to fix the same errors that crop up regularly, to define the words most troublesome for that publication, to provide consistency in usage and presentation. Sometimes they are little more than a compilation of the memos issued by a copy desk or news editor, reminding people about the correct names of companies or the policies on datelines, or to remind editors on acceptable headline practices.

Other times, stylebooks grow out of a sense of mission to guard the language from silliness and doublespeak while allowing the language to grow, as English does.

What I didn't find in this book was the Journal's obvious ability to teach, as demonstrated in some other WSJ guides. While a stylebook doesn't have to take education as a mission, once it goes public, the educational component would seem to be essential.

Why else would anyone not worried about whether to capitalize executive director buy this book? As an internal publication, the stylebook is useful. It sets standards and clearly tackles problem words, I'm sure fed by repeated misuses of certain words or facts by its own staff. I'd be willing to bet that the items on defuse/diffuse, or bizarre/bazaar, for example, are included because someone(s) on the staff has demonstrated confusion on their proper usage.

This is no knock on the obvious effort that went into putting this book together. Virtually every editor I know flees in terror at the prospect of having to produce a stylebook for the company. But once it went public, it needed some more thought. I'd recommend this book to anyone who likes to collect style and language manuals, or people who need more sources of information on certain business terms. But I wouldn't rush out to buy this as a first choice on either language or business.

As its title says, this book is The Wall Street Journal's *style* guide and, to a lesser extent, a usage guide. A style guide is something specific to the book-magazine-newspaper publishing world: a volume that tells the writers and editors for a given publisher how they should handle certain recurring situations. ("Style" in this context refers to the mechanics of prose composition, not to a writer's individuality of expression.) Any style guide's main purposes are to promote consistency and to save the time that would otherwise be wasted in continually rethinking issues that the house has already decided. Whether the guide also promotes "good usage" in the sense of Strunk & White or Fowler is almost irrelevant. A style guide is thus a series of more or less arbitrary decrees from the boss -- don't use a serial comma, don't put a comma before "Inc.," capitalize "The" in "The Wall Street Journal," etc. It's not the job of the typical style guide to explain why one usage is preferred over another or to give its user choices; rather, its job is to set forth the rules followed by a given publisher.

The Wall Street Journal Guide to Business Style and Usage is exactly what its title suggests and a bit more. It tells you how The Wall Street Journal has answered the questions that, experience has shown, arise when writing about business. It doesn't debate the wisdom of hyphenating fractions, for example, but simply tells you, "This is how we do it at WSJ."

In addition, it contains helpful definitions of business terms and (much less frequently) of grammatical terms. But, if you want a business dictionary or grammar book, then this should not be your first choice. You should buy this book if you write, or edit writing, about business, and you want to know how the world's foremost business publication handles the same problems you face.

This is a very comprehensive textbook of the subject. It deals with just about every aspect of the AIS realm. It is, however, a very dull book. There isn't much illustrating, no color, and absolutely no life beyond the black and white wasteland of its pages.

Everything you need is in here, but the book truly is boring as dirt. If you need it for a class, fine. But do not buy it if you just want something to read.

I had anxiously awaited receiving "Another Time, Another World: Coney Island Memories", and I am bitterly disappointed. It is a "vanity press" style of publication, nothing more than a photocopy on quality paper with a generic hard cover. Illustrations are few and far between and are copies of copies. The text is primarily a transcript of an interview about what it was like to work at Coney Island. For $45.00 I was expecting a well-done book portraying the history of Coney Island. Instead it is a grouping of interviews and a few newspaper photocopies. This is one example where I would never have bought the book had I seen it in person.

This book is for readers who have a serious interest in Coney Island history. It contains telling interviews with Coney insiders who describe in great detail how Coney Island was run during the final days of Steeplechase Park, the last of the great Victorian amusement parks. The author's father managed the park, and his story is informative and poignant and reveals the real reason for the the decline of Coney Island. If you are looking for a thoughtful history, and not just pretty pictures, then this is the book to read.

No es lo que esperaba, no es un libro en donde le enseñan a como configurar una Red, mas que todo solo son aspectos generales para alguien que quiere apreder como instalar Redes no se lo recomiendo.

Como profesor considero que es un libro muy útil y didáctico para los estudiantes. El hecho de que es visual permite que el estudiante no se aburra con tanto texto y pueda asimilar el material más rápidamente.

This guy is out of his mind. A very frustrating read which makes U.S Army technical manuals seem fascinating. Mr. Whisenand is an obvious scholar, but I fear his "book of lists" does not translate all that well to actual human beings. In addition, I found the section on "community oriented policing" especially overblown. He fails to consider the prosecutorial implications of stating that "long and detailed reports are turnoffs to many people" (page 331, paragraph 1), they're turnoffs to defense attornies too!
Again, an extremely intelligent man and dilligent social scientist, but this book is horrible.

This book is entirly overwritten. It is very listy, for example, It tells you that there is 6 characteristics of a well written report. Then in the very next line he tells of the 6 different types of reports. Then he goes further to break down each type of report and explain what they are and why they are used. The ideas are notable. However the book's content is poorly written and is more for the overall manager not specific to police services. And yes, one needs to do the job before one can write about it.

The ideas are worthwhile, but the book is long winded and wordy. One example is the author takes 5 pages to tell you, "you have to know who you are before you can leed anyone else". What the word "goal" means and how to form one, takes another chapter. In defense of the Author (it's obvious he has never done the job), for a social scientist living in an Ivory Tower, he has a decent handle on the theory behind interaction in a Police Department. The 15 ideas are all common sense (something world seems to be in short supply of today) and would do wonders if a department ever implimented them.

I bought this book with the impression that it would be a good book for system administration of a generalized UNIX system. I knew that it would not cover every scenario for every flavor of UNIX, but it should at least be a great foundation.

The title is quite misleading. "Bible" implies that this is an authoritative and complete tome on UNIX issues. It is definitely neither of these. The cover even says it is 100% accurate and "what you need". Perhaps if one was looking for general guidelines, this would be true, but then the book's title would still be misleading.

This book is by no means an exhaustive work on even the generalized issues. One case in point is the section on system security. It goes into great depth on describing one scenario where a hacker broke into a system and mucked around. It gives log listings, printouts, and descriptions of what was going on - in this specific scenario. This is all well and good, but it only goes far enough to show one single possibility.

The authors are adept at making sweeping generalizations without too much elaboration. They pull in one or two very specific examples on certain topics, and then move on. This is just enough to make the reader hungry for more, but never delivering.

The CDs that come with this book have an old, light copy of Slackware. Sure, it's a system that will work, but an update would be of much more use.

What the book tends to avoid, and this is in my opinion the biggest problem I've encountered, is elaboration as to the differences between the different flavors of UNIX -- Solaris, AIX, HP-UX, Linux, BDS, IRIX, etc. It's all generalizations. Perhaps this makes the book more helpful to some people, by giving the bare necessities. But, that does not make it "what you need" as the cover says.

Granted, this book is not a complete waste. There are some interesting sections that give nice discussion, such as organization of file systems and so forth. But these pockets of usefulness do not make up for the rest of the problems.

There are better UNIX tomes out there, even available for download. Check those out before you seriously consider buying this book.

This book starts off with an advanced discussion of the basics of a Unix filesystem. It moves on to breifly cover shell scripts, networking, PPP, and administration. The ONLY subject this book covers in any extent is system administration, and if that's your topic of choice, you'd be best to look in more specific books.

The main problem with this book is its not specific enough or easy enough for a new reader, and its too simplistic and, again, not specific enough for an advanced reader. The only type of reader who might get good information out of it is a broad-spectrum intermediate reader.

In general, I would reccomend that anyone looking for a good *nix book look elsewhere.

The book does a good job of introducing the main UNIX concepts such as filesystems, shells, processes, inodes, etc. It also covers TCP/IP basics, network security, a little bit of everything. The book's focus is mainly on system administration (although an introduction to shell script programming is given), so if you are looking for programming information, you won't find much here. And if you are looking for advanced topics, you would likely be better off getting a specialized book on whatever subject you are looking for: on many subjects the coverage in this book ends just "when it gets interesting".