Practitioners Books

Women's health is not my area but this book gives me a quick review and provides peritent information on health history, preventive care, ect... It's a good reference to have and fits in your pocket.
thanks

Lots of good information. Not something I could use, however, I asked for a refund.

We love these books at our clinic because they are so brief and easy to read. We had to return the Transfusion book however because it was geared more towards running a blood bank. It did not have enough information for us that was geared towards our technicians for educational purposes.

This book is a excellent tool to everyone who needs learn the basic steps to proceed a blood transfusion, from collection to infusion, of easy way.

Very useful lecture. As a psychotherapist I am now more confident with situations, where I dont know what to do, what to say. I leave space and somehow answers come...It works. On the other hand I see, that there is no need to mistify such people as Tolle ( somehow superficial knowledge about analytical therapies). Anyway: great wisdom, new aproach, fresh look, "evidence based" work.

Matjaz Lesjak MD

This set of CD's would be more suited as a DVD. There are several long pauses, mostly in the first and last CD. Since the listener cannot see Tolle's "presence" we are sometimes not sure what is happening.
This set is worthwhile, but I would recommend "Through the Open Door" as Eckhart's best CD.

This is one of the best practical books out there on how to adhere to accountability in clinical practice. Becoming a true scientist-practitioner is not just a pipe dream although many people would have you believe this. It astonishes me how adamant many mental health practitioners are these days about the "impossibility" of mixing empirical approaches with clinical practice in a balanced, responsible way, especially people who have never tried to do so or know very little about how to achieve this type of synthesis in the first place.

Having studied experimental research designs for the past 6 years and numerous topics dedicated to the subject, I have found this text to be the most convoluted and dense book on the subject of research yet. Rarely do the authors speak in a language that is accessible and meaningful to the general audiences of researchers and pre-researchers. Instead they are overly verbose and convoluted which makes searching for the key points and important concepts like fishing for a needle in a haystack. Here is an example sentence from page 202:

"The multiple baseline consists of a coordinated series of two or more replicated simple phase changes in several different data series arranged by person, behavior, time period, situation or any combination of these, in which the phase changes occur at different points in real time and after different first-phase lengths such that behavior changes are generally seen in interrupted series before phase changes are made in uninterrupted series."

A long, dense run-on sentence which does not succintly clarify the pointin a pithy or concise manner. Translation please! This book contains 386 pages of such text, and although there is valuable information within it, it is not user-friendly in the least.

If interested in research methodology and design, I would instead recommend Research Methods texts written by Zechmeister, Zechmeister, & Shaughnessy.

Very good book. I am enjoying reading it (not complete yet, it is really very big book). The topics are covered at length. Very good coverage of important concepts with amazing knack of not making the subject boring or dull. Very nice suggestions / references / advices for further study. A A very good read for software engineering professionals.

When your interest fall in software engineering, there are *lots* of books on the subject but only a few of them cover the principles in an almost exhaustive way. One of the main errors that authors do is having the claim that all about software engineering can be covered in a single book. And this book is no exception. When you're reading a textbook, this isn't always bad: one of the main purposes of a textbook is introducing the concepts gradually, without much details and in the clearest way possible. A student doesn't need to know all. He/she just need to understand the fundamentals of the discipline. So, while this book is intended for a professional audience, it is structured like a textbook. The problem here is that it gives probably too much informations for students and too few informations for professionals. It gives a nice introduction on the subject, explaining why the software is a product, its features, its lacks and its myths (very interesting). Problems start with chapter 2: the process. While something is covered about some development models like waterfall, win-win model, RAD, concurrent, etc., it lacks any detail needed to really understand these development models and bring them in practice. One of the things I hate the most about this book are repetitions: the author repeat the same concepts many times during the exposition and this can be irritating. It covers many subjects, like user interface construction, project planning, temporal planning, quality assurance in software development, software architectures, component based engineering, conceptual modeling, etc. Each chapter is a small introduction to these subjects but the book gives small or no details at all on how to use these concepts in practice. You won't find code here. You won't find design patterns, UML diagrams, state charts, refactoring methods. While this is not necessarily bad, it makes clear this book is better used as a textbook and not as a practical (for practitioners) manual to learn software engineering methodologies directly on the field. So, if you're interested in software engineering and you want a solid introduction to it, buy this book. If you're a professional who want a practical exposition of the discipline to apply concepts on real projects, skip this book. I give it 3 stars because explanations are good and the book is well written but the title is a bit misleading: professionals generally needs other kinds of books.

First, if you're looking for a book on managing software projects, this is not it. It is a very difficult subject to learn from a book. In fact, large organizations typically have their own project management practices, and have classes to teach their PM's.

Project Management is difficult to learn on your own, and is a hard topic to cover academically. This book can be used in others ways. For example, as a reference for experienced PM's; it can confirm notions of practices, or be reference for very narrow topics, as software estimations.

Some of the articles are old, and may be out of date, and may be used anecdotally.

This book contains facsimiles of articles ranging from HBR to the highly technical, and a broad range of topics from personnel, to organization, to management, to technical. I found it interesting, but not very useful in terms of practice.

I am using this book for a Master's course. The book is a bit different from most books as it consists of a collection of articles.

This is an excellent book and is being used as the standard for candidates for the diploma in dental homeopathy of the faculty of homeopathy in London. There is an excellent chapter on Mercury fillings and many dentists and patients will find it not only useful for dental homeopathic treatment but also for a good basis for general homeopathic conditions. As vice - chairman of the British Homeopathic Dental Association , I can highly reccommend this book to all interested in oral and dental health

This book was a great disappointment. Too much of it is devoted to general homeopathy and not specifically targetted to dental. What was there for dental was rather disappointing too. For example, for teeth clenching or grinding, he says to buy another book on Bach Flower Remedies.

Sadly, this book is similar to most on venture capital in that it is based on interviews of VCs. The weakness behind this approach is that it provides unorganized content that lacks depth and utility. In short, while it doesprovide some important insight, these insights are neither unique or critical and can be found in other books that provide a much better resource to the entrepreneur.

Finally! A practical, hands-on guide to raising venture capital. This step-by-step handbook gives an entrepreneur a clear, real-world roadmap to the fundraising process. I only wish I had a book like this when I started my company.

This book will bring you up to speed on all the buzz words for all the methodologies, but thats the extent of the book.

This book covers very little of actually process, how to analyze and existing process, how to setup a new process or improve a process. It actually does a very poor job of explaining what sofrware engineering is all about and leaves you feeling that is about writing documents, not about creating reliable, verifiable software.

I used this book in my Grad class and I'm still confused. I don't know what to make of this book. On the one hand, I think the author tries to cover most of the important topics, but on the other, the book falls short in intellectual substance.

Problems at the end of each chapter are very time consuming, and in some cases cannot be answered at all. This makes me wonder if the author can answer any of those tough questions that he wants you to ponder.

If you're looking for a good SE textbook, don't buy this one. You will regret it!

There is nothing much in this text that's closely related to what the author is asking you to consider. His book is based on fluff, and lacks the important stuff; just a bunch of snippets.

You will get an "F".

This is by far the worst textbook I have ever read, and isn't worth $128 dollars.

Thanks for nothing Roger, but you deserve at least 1 star!

This is a good book. I have several editions of this book, including a very early one. In my view, in looking for a thorough perspective of software engineering, there are two major routes: McConnell/Weigers series or one of the comprehensive volumes by Pressman or Sommerville. McConnell's books (Code Complete, Rapid Software Development, and Software Estimation) and Weigers (Software Requirements) are each highly detailed. Hence, four-plus books. Pressman encapsulates (sic) the whole shebang into one big comprehensive volume. Not as detailed as those Microsoft Press authors, but that's not a drawback. If you've been practicing for a long time and you're the project manager, sometimes a substantive overview is what you need, not minute details. You're not living in the deep details anyway, your engineers are. Plus, the coverage of the more advanced development technologies, like formal methods, are very good and not included in the Microsoft Press books. Bottom line: if you're a technology director or project manager and want the big picture (in one place), get Pressman. If you're a systems analyst or software engineer and want the larger view, get McConnell and Weigers. (I have not read the Sommerville text, but from the table of contents there's a chapter on security which the other books only cover lightly.)

I had the 4th edition of the book back in college. When I started studying for the CSDP (Certified Software Development Professional) Exam, I ordered the 6th edition. The 6th edition is a huge improvement over the 4th.

This book covers just about everything you need to know on the subject of software engineering. Great book, great reading. Applying the concepts on the job will help out tremendously in your career.

I'm not a student. I am software development manager and have over 20 years of real-world experience developing sophisticated banking and financial applications. I have one of the original first addition books, and I have to say that this book was critical to my learning software engineering principles. The criticism of this book are unfounded in my opinion. This book contains the critical elements to implement SE principles.

The complaints seem to be from students and they seem to think it is a poor text book. Well, that's probably a good sign, as good text books are usually worthless for real world examples, and books that give you worthwhile information aren't usually good text books.

If you look through all the 5 star reviews, they are from Software Engineers working in the field. If you look at all the 1 star reviews, they are all from students who, frankly don't know what really is important and what isn't when it comes to developing quality software. (I know I didn't when i was a student). That alone gives speaks volumes about the book.

Some said that Code Complete is a better book. Where do you think the authors of Code Complete got their material? This book is first published 15 years before Code Complete. Code Complete is a good book, but doesn't explain the "why" of things, whereas this book does. Studying this book will give you the "why" on certain principles so you can enact them to whatever situation you are in. It is not an "ABC" book on how to do "XYZ."

The theories and examples on the programmer productivity were very valuable to me, and I have saved me countless hours and money on developers time because I learned how to maximize programmer productivity. This book is the framework on how to development high-quality software. I can speak from experience that the software I've been respopnsible for developing, using the priniciples I learned from this book, has been excellent. The software failure rates I have experienced are far lower than industry averages. I have some applications that have run for many years without any software failures. It can be done, but this doesn't garantee your success. This book shows you the blueprint. You still need experienced developers to be able to create high-quality code, but only by following the principles laid out in the book.

Perhaps if all you students had to see all the poorly written software in use in the world, you would appreciate this book more. This book is well worth it the price. If you plan on having anything to do with software development, keep this book, and don't sell back to a book store. I ordered the latest version and read it, and Pressman has done a good job in keeping up with the latest in software engineering. With out a doubt, the book is worth the price. My copy has paid for itself many times over.

Is there a list available with all the errors in the book? Does anyone know where to get it?

Accessible to practitioners but occasionally superficial with some flaws in structure and content real options.

Be warned! This is a "partial" work.
Mr. Copeland's work is great and insightful (once you download 26 pages of errata and keep it close by). He starts off with NPV and builds up to "rainbow" options. The detail is comprehensive and the chapter end questions are challenging. And this is my beef. You have to pay The Monitor Group an additional $US 30.00 for the solutions to the problems. This is not what I would call "a parishioners guide" but another example of an American corporate rip-off!.

Due to the fact that the errata was the longest I have come across, that the editing was generally so poor, and the solutions are an additional charge, I feel that Texere owes me a complete parishioners guide to real options. By using Real option analysis or NPV, the additional costs in time and money can not justify an investment in this book. A real sunk cost for me.

Mr. Copeland, do not let your name go on such a poorly finished product again.

Content : A
The book enables the reader to understand the world of real options without having to take a course on stochastic calculus, which is good because otherwise Real Options would be too hard to sell to management. The book is rich on examples and presents the building blocks of almost every combination imaginable. More case studies though would have been a big plus.

Presentation : F
You absolutely should not read the book without first [knowing] the corrections.... There are so many errors everywhere - in formulas, calculations and text (a total of 177 for 350 pages of relevant content !!) - that I could only shake my head in disbelief. Quite obviously, nobody has made even a half-baked attempt to proof-read the book.

The phrase, "stochastic differential equations" may not trip off your tongue and you may not initially see the joy of learning that replicating portfolio value = mV + B. Yet Tom Copeland and Vladimir Antikarov guarantee that their book is a practical, everyman's guide to the sometimes serious math world of Real Options Analysis (ROA). Thanks to the availability of personal computers and modeling software, everyone can now use ROA. Before PCs, only doctoral students of finance or economics would have been safe attempting it. Sure, ROA is harder than the traditional valuation methods or Net Present Value (NPV), but real options allow you to understand the full value of an asset by taking into account the factors of flexibility, risk and uncertainty. Company case models, the theory behind ROA and equations are all showcased in the book. This can be a challenging text, but we from getAbstract strongly recommend it to all CFOs and anyone charged with evaluating business strategies.