Few worked examples, no answers in back
937538
While a good theoretical understanding can be obtained from this book, the lack of many worked problems in the book and the absence of any solutions in the back presents a real problem for any self-study. You must have a knowledgeable professor who can work out a lot of examples in class. Unfortunately I do not have a good professor, so I've had to pick up other texts to solve my difficulties. I'd avoid this book unless it's absolutely required for a class, and even then I would suggest taking very good notes in class to supplement the book.
1547618
Book Examples DO NOT WORK!!  Maybe Theory But BAD Examples.  I will be returning it.  I hope it was not a waste of money.
3568500
When I think of problem sets, I expect word problem information with SEVERAL questions dealing with the data.  There were NO word problems at all and very few problems given.  The author notes that this is a "work in progress," but with the lack of content it shouldn't even be for sale no matter how inexpensive.  Finish it, then sell it.  Also, the problems are entered in typewriter mode versus textbook mode.  It's hard to read and understand what is wanted until one deciphers the input mode.  My advice: write it professionally, name it correctly, and complete it before putting on the market.  I wished there would have been preview of the book to see what was in it before getting it.
3724704
The problem of this book is it doesn't give detailed information on how to implement X-Query on your computer.  When you have Windows Vista, eXist doesn't work.  Neither does WAMP.  And unless you have heavy duty experience with SQL Server, this book is useless.  The author of this book needs to include many more simple examples so that people like me can use the language.  I might figure out how to use this someday, but it will be a long time before I do.  That is so disappointing.
1158738
As a professional, proficient user of other leading sequencers (e.g., Pro Tools, Cakewalk Sonar, and Cubase), I was very disappointed with Stephen Bennett's book "Making Music With EMagic Logic Audio".
The great majority of the book consists of laundry lists that provide only short descriptions of what various toolbars and buttons do--descriptions that are already available in eMagic Logic Audio's manual. The book fails to give us specific examples and walk-throughs to teach the various functions that are available in Logic.
The only chapter that is somewhat useful is the chapter on 'setting up an environment' in Logic. It does provide a step-by-step guide to setting up a simple environment. Unfortunately, it doesn't go into greater detail and covers only a small fraction of Logic's functionality. If you have multiple MIDI instruments, MIDI, audio and soundcards, this book won't help you set them up.
The remaining chapters are even more superficial, and provide laundry lists of Logic's functionality. But again, no walk-throughs or specific examples. Key features like Logic's audio tools are not covered.
I cannot recommend the purchase of this book.
3896072
I know some Java, and am finding that the content of this book has numerous errors and points of confusion. I can make my way through the book pretty easily, but often find myself thinking that someone trying to learn the material would have issues. The examples are pretty weak. For someone with a Java background, more concise summaries of what's in the exam would be better reading. I skimmed "OCA Java SE 7 Programmer I Study Guide (Exam 1Z0-803) (Oracle Press)" and it seems much better organized. For example, that book includes a discussion of the importance of understanding the command line compiler; this book doesn't even include "compiler" or "classpath" in the index, though it does include "EJava() method", a reference to a trivial example method you'd never look up, and that turns out not to be listed on the first page referenced.
3901361
Very few examples for each concept learned.  If you want to do well - do all the practice problems at the end of the chapters.  ALL OF THEM and you might have a chance at learning something.
4180668
this book is written in a very confusing way.  both the sequence and the actual text is extremely poor.  things aren't explained well and other things are overly explained to the point of seeming more important than they are in real life retail buying.

my biggest complaint, however, is the fact that not all the answers are provided at the back of the book.  and alarmingly small number of answers are given so it's impossible to know whether you got the problems right.  furthermore, the case studies that would provide real life practice have no solutions or discussion points so they are kind of waste with no one to discuss them with and no answers/explanations of answers.
4403880
The code examples are not clearly differentiated from the explanatory text by color or font selection. Many, if not most, lines of those samples wrap, rendering any indentation useless. There are no page numbers, nor is there an index.

In general, the content lacks depth -- the samples are more mere demonstrations than anything resembling true applications. The advertised topics are included, but little depth is provided on any of them. Few , if any, nuances, exceptions, "gotchas", or the like are addressed. There are no links to supporting web information or code sample downloads.

Save your money and pass on this one. Much more complete and useful information on any of the included topics can be found elsewhere.
1426124
Chapter Exercises and Appendix Project cases are too many and poorly designed; ambiguous and at best, the examples are not congruent with related chapter exercises.  In short, much to my disappointment, most of the exercises and answers did very little in adding to my understanding and application of principles and practices of Project Management. At the expense of good instruction, the text is heavily invested in review and exercise questions than illustrative step by step instructions on how to master for example, project task input, scheduling and designing charts.
2154389
Like I said, the back of the book has some great tables (although they could use some organizing). The rest of the book is pretty bad. The review problems ask you to do things the book itself never mentions. Lots of material my professor even said isn't even in the book, but it requires you to know how to do it anyway. The example problems are seldom helpful, because it skips too many steps. I think the author assumes too much about what a beginning design student knows. It goes from Step A to Step P, all the intermediate steps you have to figure out yourself. I don't recommend any professor to torture their students with this book. Get a better one.
4233468
I was excited to find this book because of these quotations from the book's back cover:

"[fully covers] system on a chip," "Bluetooth because it addresses reality," "comprehensive guide to overall SOC verification,"  and

"authors... leave no stone unturned in this comprehensive overview of [chip verification] tools and methodologies."

"Analog engineers have been using [SPICE] for analog simulation for over 30 years..."

Given the above comments, I had hoped that it had some analog verification info.  It turns out to have no significant coverage of analog. It claims to, as in DAC verification, but the verification of the trivial DAC is virtually analog-less.  And even the digital system on a chip verification coverage seems rushed.

I am an analog chip designer with 24 years experience, a good part of that time spent verifying my analog and mixed-signal designs.  This book has a single 24 page chapter on analog, "Analog/Mixed-Signal Simulation," which taught me nothing.  The chapter lists and defines the standard specialized nomenclature of the analog verification software, gives an example simple VerilogA behavioral model for a crude resistor-transresistor DAC, and gives a crude behavioral test example.  I think that most all stones are left unturned for analog or mixed-signal chip verification.  The authors mention SPICE, spectre, and Cadence Analog Design Environment only.  I just finished a 37000 transistor analog & mixed-signal chip verification, and this book mentioned none of the tools and methods that I used, which included Mentor's Modeltech Modelsim and Synopsys's Saber, digital and analog coupled together.  The examples are of value in giving existing digital chip verification experts an example of how to get started with a crude VerilogA behavioural modeling of analog blocks to be fit into a digital chip verification flow.

I thank the authors for their book in this area with little publisher coverage.
548777
I'm a student, so I cannot offer comparison between this author's tome of Statistical Methods and other similar works. I can offer how FRUSTRATING that number of bad answers in the student manual (odds) are. How you can try to work through problems in which the data promised is nowhere to be found (I'm talking to you Ex11.12.dat and all your compadres!). Chapter 7 has several flat out wrong workings to problems. Set me back HOURS AND HOURS trying to work those out and being confused in trying to LEARN from the worked examples. The editors of this book should hang their heads in shame. Expensive book, someone's success in a course, and big errors. Also what appears to be rushed mismatched re-arrangements from the last edition. I'm still looking for a table in chapter 3 or 4...here table...here table...

I actually HIRED a tutor to help me with problems I had worked correctly, but couldn't reconcile with the book...

Beware - if you don't have solid support from your university's professor or a stat's lab...be prepared to google, get supplemental material, and feel confused.

And lesser - follow some problems through so we can compare and learn how to build a complete example from the data. This happens for a section or two, but more would be great. Also, don't offer us massively hard examples (even supplemental) and tell us to hum through what we don't understand...show us relevant problems and make it clear what we should understand based on learnings from the text and what we shouldn't.
4107728
At first, the book looks great with a lot of examples, but the tecniques the author uses are not for visual basic 6.0 , but for 5.0, (DAO instead of ADO) he never touches the data enviriomet wizard and you still have a lot  of questions after you read it, I guess that is why it is only for  beginners, Right.
3952184
I wanted to like this book.  I really need a good Web OS book with examples.

It is very hard to find what you are looking for in this book. The index is not very comprehensive.

Examples/ I was trying to find examples of a dialog box and a timer.  There is no reference to either in the index. And since you can't download a copy as a pdf, you can't search the text of the  book.

There may be examples of what you need in the book but how to find.....
3062971
Great examples, but a limited explanation of how to get them. I need the steps laid out for me. More detail please.
520115
I found this book quite disappointing, mostly because the example scripts that he uses are so simplistic as to be nonsensical.

Rather than each example building on the previous examples, to allow the user to create something which actually works at the end of the book, we are left with a series of short "hello world" examples. Here is one script taken from the book:

switch (navigator.appName) {
  case "Netscape" : window.alert("Firefox/Netscape is cool."); break;
  case "Microsoft Internet Explorer" : window.alert("Internet Explorer is cool."); break;
  case "Opera" : window.alert("Opera is cool."); break;
  default : window.alert("What browser is this?");
}

In another similarly inane example, he demonstrates the BREAK command by having us write a 1-to-10 loop, and quit when we get to 5. Why would you do that? Neither example is actually useful, and there are far better ways to accomplish the same thing in Javascript.

I get that he's demonstrating how each command works, but there are much better ways to do this, namely using real-world examples. I found that even when I already understood the topic, his descriptions and lame example scripts could be confusing.

This is a real pity, as the book is otherwise very well laid out, with most chapters building logically upon the preceding chapters, and the style is easy to follow. Unfortunately I personally would not recommend this book due to the lameness of the example scripts.