PS The author also writes a restaurant review column called 'Cheap Eats' for the SF Bay Guardian.
This book shows how a few big companies control the distribution of grain throughout the world. In so doing they are not prone to accept "aging receivables" from dictators, tin-pot or otherwise. Every political leader must understand the importance of grain or face a coup. Of course, one can find those who have lasted longer than others, but only at the cost of so weakening their state that it ultimately crumbles from internal implosion.
Read this book to understand history and more importantly the origen of our food supply and how it reaches our table.
Now I understand the real power behind families such as Cargil and ADM's Andreas.
List price: $39.95 (that's 30% off!)
are great experiences, and others are nightmares. Overall this book
was a pretty good experience, although there was a major bump in the
road (and a couple of minor ones). In the chapter summary below I will
go into a little more detail on the positive and negative points.
Chapter Summary:
Chapter 1: Overview of Object Oriented Programming
This chapter starts with a very brief overview of the history of OOP.
Brief is good. It also has brief definitions of OOP characteristics;
Objects, Abstraction, Encapsulation, Polymorphism, Inheritance, and
Aggregation. It ends with a blurb about the history of VB.
Chapter 2: Designing OOP Solutions: Identifying the Class Structure &
Chapter 3: Designing OOP Solutions: Modeling the Object Interaction
These chapters go into UML and things like Use Cases, Class Diagrams,
Sequence Diagrams, Collaboration Diagrams, and Activity diagrams. This
seemed exciting to me because I never really get into anything like
this on the job, and I wanted to know a little more about it. Well,
while interesting this ended up being a bump in the road for me.
The Author says to either do the exercises with a UML Modeler you can
download from the net, or creating the diagram by hand. I wanted
to try the tool he used in the examples so I downloaded it. At this
point just let me say that you should be prepared to spend a lot of
time figuring out the tool if you decide to try it. It is not easy.
The directions for doing the exercises don't quite flow with actually
using the tool either. The author does state that it is pretty tricky
to use, but I really feel that the directions for these exercises
should have been better. I managed to get through some of the examples
in chapters 2 and 3 after a couple of hours.
Chapter 4: Designing OOP Solutions: A Case Study
This chapter talks about the process by which one would design an OOP
solution with a case study. The Author goes into good detail about the
actual steps needed, and does a good job explaining the methodology by
which this is accomplished. He also gives some good advice on how to
avoid some of the more common pitfalls of designing an OOP solution.
Chapter 5: Introducing VB .NET
This chapter gives an overview of VB.Net as well as the .Net
Framework. After the overview it gives you a hands on tour of the
Visual Studio .Net IDE. Of course, you will need to have the IDE to do
the tour. This tour shows you many of the screens, option settings,
and menus of Visual Studio .Net. The second exercise shows you the
debugging features of VS .Net. At his point you will need files that
you can download from the Apress web site. I may have missed it, but I
never saw any mention that downloading files was needed for the
exercises. It certainly was not at the beginning of this exercise, and I
think their should be some kind of direction about it present.
Chapter 6: Creating Classes
This chapter is all about classes. How to restrict them, access to
them, creating methods, overloading methods, using constructors to
name some topics. This chapter too has exercises you complete with VS
.Net. They all seemed to work fine for me, and were very easy to
follow.
Chapter 7: Creating Class Hierarchies &
Chapter 8: Implementing Object Collaboration
These chapters discuss things like inheritance, polymorphism,
interfaces, delegation, error handling, shared properties and methods
to new a few. These two chapters also have multiple hands-on
activities so you can continue to learn how to operate VS .Net as well
as learn more concepts of OOP. These activities are well documented,
and I had no problems completing them all without incident.
Chapter 9: OSO Application Revisited: Implementing the Business Logic
This chapter helps bring together all the ideas you were introduced to
in chapter 4. From there it goes into data access by talking about
stored procedures, ADO.net, sqlclient namespace, and many other
details. In order to do the examples you will have to have SQL Server.
Chapter 10: Developing Windows Applications
This is a fun chapter that talks about windows forms, event handlers,
dialog boxes and different types of bound controls. This chapter is
full of hands on activities that are well done.
Chapter 11: Developing Web Applications
This long chapter deals with web forms, server controls, server
control inheritance, server-side event processing, ASP.net, state, and
many other things. It is all about designing an application for the
web. The activities are easy to follow, and work.
Chapter 12: Wrapping Up and Reviewing
A quick summation of what the book covers and some tips on where to
focus next.
Appendix A: Fundamental Programming Concepts
This appendix is basically a primer for beginning programmers.
Appendix B: Exception Handling in VB .NET
A quick 4-page explanation of how exceptions are handled in VB.Net
After finishing this book I had a hard time deciding what grade to
give it. I ended up giving it a 7 out of 10. The many problems I had
with the UML activities using the UML modeler were just too painful
and frustrating to give it higher than a 7.
I will admit that the rest of the book was great and would be very
useful to a beginner trying to become more familiar with VB.Net and
VS.net. The VS.net activities were flawless, and gave good hands-on
experience that beginners would love. The UML material was actually
good as well, but the problems with the modeling tool activities
really influenced my final judging of the book.
In summation, this book is without doubt a beginner's book. Do not buy
this if you already basically familiar with VS .net or UML. If you are a
beginner and do the UML activities with pen and paper I believe it will
be a great learning experience.
The book gives a nice overall background of OOP then shows how to implment it (on a very basic level) in VB.NET.
I highly recommend this book for VB programmers who have never incorporated OOP in their programs.
I give the book four stars because it does what it sets out to do. It's arranged in an orderly fashion, the chapters cover one thing at a time before moving on, there are quizzes at the end of each chapter to make sure you are getting it. But... I bought the book hoping it would inspire me to delve into some areas I'm weak on and I just can't see it doing that. Plus, it seems a common misconception that all you have to do is learn everything in this book or others like it and you will be the next Charlie Parker. Wrong! Jazz is and always was an imitative art. The theory is used to explain the art but the art didn't come out of the theory. Many of the innovators of jazz did not know half of what's in this book. They learned by listening, assimilating and building upon what came before them. I know 5 times as much about the theory of jazz than my father, yet he can improvise beautiful solos and I run up and down scales.
If you need this book as a reference, fine... plop your money down. I bet it stays on your shelf unless you really need it. But, if you want to improvise , go instead and buy Milt Jackson's CD "Opus De Jazz." You'll learn more from the first song than you can from this or any other book. Plus you'll enjoy it a whole lot more.
The Jazz Language is to the jazz improvisor and writer as the dictionary is to the novelist: one would not allege that Steinbeck learned to write or was inspired to write by a thorough reading of Noah Webster.
But as a jazz theory text, The Jazz Language is as complete a resource as will be found for the modern jazz musician.
Up until recently, this was the GREATEST and practically only Jazz Theory book of its type. Concise... written in plain and simple English. Overwhelmed by that college music theory course..? this book was the tool to get you through. Its still just as great, though Mark Levine now has his flashy (and much bulkier) Jazz Theory Book.
What still makes this book stand out is the fact that it covers all the basics, upfront and in plain English. It doesn't delve into stylistics and performance like Mark Levine's book, but will give you a bird's a view of "Jazz Improv and Music Theory 101". If you need a crash course, this book still reigns supreme, and even alongside The Jazz Theory Book, I'd have to say, its a great starting point, and a must have for teachers.
Other recomended readings would be Jimmy Amadea's Harmonic Foundations for Jazz and Pop Music and definitely those Aebersold tapes and play-a-longs !
The hero Vlado Petric has the absurd position of being a homicide investigator in a city where death and lawlessness have become the norm. While investigating the killing of a high-ranking official, he struggles against warlord-like black marketeers, renegade generals, ethnic prejudices and the overall dysfunction of his besieged city. It's a fascinating setting for a mystery, and Fesperman uses it well to spin an intrguing tale.
On the downside, the plot is a little too linear, but Fesperman more than makes up for this with a great lead character and evocative prose. And aside from the mystery, we get a worm's-eye, human view of the confusing Bosnian Civil War, which Fesperman covered as a correspondent for the Baltimore Sun.
"Lie in the Dark" is as grim and bleak as noir gets, so any fan of the genre will be sure to enjoy it. Hopefully Fesperman will use this setting again for his next novel.
Petric's assignment to investigate the death of a high police official is meant as proof to the local U.N. officials that the city is still functioning. The well-marked trail -- that the official was on the take and was killed when he demanded too much money -- was meant to lead to a quick report and possibly the arrest of some unfortunate. But they didn't reckon on Sarajevo's last honest detective. Petric's investigation leads him deep into the black market economy where cigarettes function as currency, gasoline is sold in glass liter bottles and where men are not above putting the hurt on police officers asking too many questions.
"Lie in the Dark" is a strong mystery debut by Baltimore Sun journalist Dan Fesperman that rediscovers the morally shaky worlds of Graham Greene and John le Carre on the bomb-shattered streets of Sarajevo. Fesperman covered the war and writes about life in Sarajevo with the confidence and knowledge of a native. But he does more than report on what he saw. "Lie" is a beautifully written, sad elegy to a city in agony, and Petric emerges from the pages as a whole man, with his strong curiosity, an aching need for his family, and imbued with the very real fear that one misstep, either on Sniper Alley or while questioning a witness, could lead to an unmarked grave on a soccer field.
This book is the equivalant of playing Russian Roulette with a "Full Clip".
DS tells it like it is. Straight from the heart.
**True to the Game, as long as blood is blue in my vein**
ND ------> Comin soon...