John Books

Monitor's creator was a Swedish engineering prodigy named John Ericsson who had supervised 400 men as a canal engineer by age 16. For an 1829 railroad design competition built a steam locomotive that established a land speed record by covering a measured mile in 57 seconds (63 mph). But the contest sponsors changed the rules to defeat foreigner Ericsson and his attempts to provide innovate designs to the Royal Navy were also rejected. In frustration Ericsson emigrated to the United States and in 1837 invented the first practical screw propeller to drive steamships through the water.

In 1861 Union intelligence indicated the Confederates were rebuilding the scuttled former Union warship USS Merrimac as a heavily armed ironclad. If that ship (rechristened CSS Virginia but generally called simply "Merrimac"), broke the blockade of Hampton Roads then US coastal cities, including Washington, DC, would be vulnerable to attack. The Union needed an ironclad quickly, and Ericsson already had a plan!

Monitor's keel was laid in Brooklyn, NY on October 25, 1861, and Ericsson and his numerous subcontractors worked 108 days and nights until on February 9, 1862 USS Monitor was turned over to the Navy. Exactly one month later Monitor faced Merrimac at Hampton Roads. Objectively the battle was a tactical draw, but strategic victory went to the Union. The Union blockade was preserved, the Confederates remained bottled up and Britain and France, who were leaning toward supporting the South, decided to remain officially neutral.

This book tells the story of the design, construction, combat history, demise and legacy of USS Monitor in a well-written narrative format. It provides enough details for general readers interested in naval, engineering and civil war history. It may be too general for the serious buff, but I recommend it as an amazing tale to everyone else who wants to know more about this important historical event.

There are some small reproductions of period etchings and photos and a good map of the Hampton Roads battle area. The only thing missing are good schematics of Monitor's interior design.

So if you want to know where stay along I-94 near Billings, or what size trailer can be accommodated at Hebgen Lake Campground, this is not your book. But you really want to get to know the state and its people, the Johaneks will take you there. All in all, it's an engagingly-written, idiosyncratic, informative and altogether charming book.

Finally we may play with the "building blocks of matter" we've been hearing so much about. Here is an instruction manual, detailing the Elements, and their Interactions, while at the same time suggesting possible Design Models for construcion.

Curious about the subject?
Start with Drexler's Engines of Creation, instead. Maybe some other collections of theoretical applications to whet your appetite. Come back to this when you begin to see a bigger picture.

Know some, want to know more?
Definately read. But be warned, it is quite techincal when it is not being necessarily vague. This is a halmark. The basis of this book was Drexler's thesis for his doctorate in Molecular Nanotechnology, the first awarded (MIT 1991, I believe).

Serious about the topic?
You already have access to a copy...or should.

You might very well be able to download significant portions from Foresight's website (it's an org.anization, not a com.mercial); but I would suggest supporting them with at least the price of the book. They seem to be committed to developing this Potential responsibly.

Your book is an excellent guide. Thank you for inviting me to the field of nanotechnology.

Sincerely,

Kenneth L. Buckingham, Founder Tiny Technology, Inc.

I agree with the book that the .NET Framework is mostly targeted at business developers and the Internet for B2B and B2C applications, as well as internal Enterprise applications. Having said that, I have found the .NET framework lacking, and as the author points out, most likely due to how young it is in comparison to the Win32 API.

This book will get you up and running with making those Win32 API calls when you can't find that same functionality duplicated in the .NET Framework. There isn't much documentation on this subject matter on MSDN or the web (searching on Google), so this is pretty much it. The author did a great job, however, at times, the examples were a little light or topics weren't explained as thoroughly as they should have been. For example, the author will tell you what data type he used in place of a native Win32 data type, but doesn't clearly explain his reasoning for the choice. But other than that small complaint, this book is a must have for any .NET developer.