I would not, however, recommend this book to a beginning developer unless he or she has a good foundation in object-oriented design and other core software development principles. It is by no means a primer, but rather is targeted at the intermediate to advanced developer who wants to excel in designing robust, reusable, and extensible classes for the .NET framework. Nor is it for one who simply wants a set of instructions on how to build an application in C#; rather, it is for the developer who wants to build the best applications because he or she has the best understanding of the effects of class design in the .NET CLR.
On a more granular level, the table of contents provides a sufficient look at what each chapter covers, and each chapter delivers on what the TOC promsies, and more in some cases. Chapter One takes an in-depth look at reference and value types and, augmented by Chapter Three's discussion of method parameters, arms the developer with the knowledge needed to make the right choices between the two by providing a solid understanding of how they are handled by the CLR. Chapter Five is another essential read, covering object lifecycle and a few design patterns.
Most of the chapters offer practical advice on best practices in bulleted format to encapsulate some common-sense deductions from the data covered in the chapter. And there are a few gotchas that this book can help you avoid, such as how the compiler handles constants (you'll have to read it to find out).
There are only two things I'd criticize about this book. First, even though some of the topics covered are complex, I tend to think that it could have been considerably more readable in places, particularly Chapter Seven that deals with inheritance and polymorphism. Of course, part of the problem is that those topics cannot properly be covered in so short a space--they deserve (and have) book-length treatment. The second detraction is that Chapter Eight, while providing useful information, is somewhat off-topic, treating namespaces, assemblies, and documentation, which are only peripherally related to effective class design and are covered in several other books as well as the MSDN documentation.
In short, this book is definitely worth the {money} that it costs . It is not an easy read and should only be taken up by developers interested in knowing more than the minimum required to build an application. One of the things I love about this book is its focused approach and, consequently, its readable length of only 347 pages. Most books that are longer, that is most developer books, are full of too many code examples and too much re-coverage of topics that other books have already covered. This is a notable exception. I highly recommend it to intermediate to advanced developers.
Chapter 1 is at [...]
"C# is Microsoft's new object-oriented language, specifically designed to take full advantage of the .NET type system. At the heart of .NET programming in C# is the task of building classes. All C# code participates in the .NET type system, because all code is contained in classes and other types which participate in the class hierarchy of the .NET framework. This book is a guide to help you design these classes effectively, by looking at what control we have over our classes, and how C# turns our class definitions into executable code.
"Ask anyone: designing effective classes that you don't have to revisit and revise over and over again is an art. This Handbook aims to give you a deep understanding of the implications of every decision you can make in designing a class, so you are better equipped to take full advantage of C#'s power to create classes that are robust, flexible and reusable.
"This book assumes that you are already familiar with the syntax of C#. It assumes that you have already used it to write code and that you are familiar with your chosen development tools and know how to compile and run C# code. You should also be aware of .NET's basic object-oriented mechanisms. In this book, we'll lift the lid on the simple syntax and examine what it really does behind the scenes."
I'm not sure how the beginning student would find this book though, but I think I would've liked to have it when I first started out. Perhaps some pronunciation guides would help, but I really don't think that the lack thereof is particularly detrimental.
There are notes on the differences between "written" and "spoken" French. Overall, this is a great book. Easy to use. Even if you're a complete beginner, you shouldn't have a problem.
List price: $50.00 (that's 30% off!)
This is a great work, all the detailed knowledge about location of cities, shrines, roads, etc, etc., etc., that has been gathered about Roman and Greek sites has been put together in just one atlas. Even individual estates are placed on maps, when convenient.
Seamlessly, from one map to another you can trace any route, find any name, and look into the neighboring area.
The map by map directory provides further insight into the sources of information, variant ancient names and modern place names (if any),
Obviously there's no such a thing as a telescope/microscope. You have to know what you are looking for, because details can sometimes shield the big picture. You need to know the original spelling of a name, or some variant. This book is invaluable when looking for names and places that are nowhere else printed in a map, at least a map that covers an area that places them in context.
Now, what else could be useful?
Basically, I would have liked three things:
- an 'inverse' gazetteer or 'name dictionary'. Look for modern place names and find ancient equivalents.
To look for a modern name is difficult. The book is not intended for this. You have to use the search engine in Acrobat, which means that you have to be using a computer. And scroll though the results. There is no straightforward way. So, a 'Modern Names Gazetteer' with ancient equivalents is something I'd like to have. Could a database fulfill this purpose? PDF formats do not allow data management, but the editor must have the data. Someone will provide this.
- a different altitude color-coded scale
As for the altitude color-coded tints, to my taste, there is at least a brown shade too many. The tinted scale is such, that some maps look a little brownish, because everything above 1000 feet has that background color. Of course, there are contour lines, but you have to look at them and read the numbers. Coding is not very useful in such a situation. Printed names over brown background are not easily readable.
- a heavy paper o plastic loose-leaf with the Map Key
The Map Key appears only on map 1, on the reverse side of the page, a good idea since the maps are not clogged with repetitive information and space is used for the essential purpose. But then you have to return to it for a reference. Thence, either it will wear out or hopefully you will remember usual references. Not for the casual reader. I've already photocopied it.
Overall, an outstanding achievement. Four stars, could have been five if some of the above items had been included.
List price: $15.00 (that's 30% off!)
But if you have never before approached even the edge of those waters, this is the book with which you want to begin; the editing and arranging of the material, appropriately enough into seasonal sections, is even better than "Once More Around The Park's" had been. Don't let my harrumphing about over-repetition of some choice essays deter you (I certainly didn't let it keep me from adding this to my library). If you are a newcomer to Mr. Angell's virtuosity (and if you are a newcomer, you should probably ask yourself where you've been all your life), from the loveliest book of baseball letters of the year. Peter Golenbock, in his oral history of the Boston Red Sox, called Mr. Angell "baseball's Homer," but Golenbock has it backward. With apologies to no one, Homer shall have to settle for having been ancient Greece's Roger Angell.
The authors devote much of their study to a region they define as the Cotton South, wherein they see homogeneous development. They stress the fact that they are economists and not historians--political, social, and cultural history are beyond the scope of this book. While the authors may at times refer to economic effects of noneconomic forces, they make no attempt to do anything more than offer an economic interpretation of the post-emancipation South; that alone signifies their contribution to the historical field. In the end, they give their ideas as to the evolution of a Southern economy that exploited farmers--white and black--and allowed for little or no industrial development.
This book covers Leakey's finds and his interpretation of such finds. There is s small black and white glossy section that displays the lake and several ancestors (including Australopithecus.)
The table of contents is:
People of the Lake
A question of survival
In the Beginning
A New Perspective on Human origins
The Human Family Unearthed
Lessons from Bones and Stones
An Ancient way of life
The first Affluent society
The nature of Intelligence
The Origins of Language
Sex and the need for Women's Liberation
An End to the Hunting Hypothesis
As you can see this is not just a book about bones. He also quotes a lot of Freud. So I do not know why this book fell out of favor. However it makes for some good background reading.
List price: $24.95 (that's 30% off!)
Every job he's ever had is detailed. Kiel is long on money, negotiations, and the one that got away. He's short on real behind the scenes stuff, on personalities, and on pulling out the most interesting details. His lengthiest description in the section on The Spy Who Loved Me was of a restaurant he ate at, it read something like a list of food items, followed by "Yum." I kid you not.
Kiel is selling this book based on his Bond experience, which is emphasized in the title (the full title on the cover is: Making It BIG in the Movies: The Autobiography of Richard "Jaws" Kiel, James Bond's Biggest Enemy, the Man with the Steel Teeth"). However, the Bond movies are given no more attention than any of his other film experience, and in fact, are given less wordage than his failed attempt to get a kid's TV series off the ground. This strikes me as misleading almost to the point of dishonesty.
The book has some small interest, especially if you're interested in the details of negotiating with filmmakers and agents.
Ultimately, it is about Kiel's Christianity, and ends with a chapter apparently intended as missionary work. I don't have an objection to the man being religious, but again, it's not what I plunked my money down for.
Not recommended.
Apart from being down-to-earth, with its method of defining terms and concepts, it has an illustrative teaching pattern, which included a collection of problems and solutions.
Also, this book contains code recipes, which program developers could use to improve their understanding of the C#; and subsequently, their overall programming skills.
In summary, this handbook is a multi-purpose manual, which programmers should value for its complementary outlook.