The U.S. Navy has long been a favorite subject for yr (justifiably) humble svt, long before he became your svt, quite long before.
The elemental battles of men against the implacably overwhelming forces of nature, while simultaneously battling to the death a human enemy, has always captured the imagination.
Lord Nelson at Trafalgar; Monitor going where no ship had gone before (thus tweaking our simultaneous lifelong interest in the history of technology ); Morison’s epic of the U.S. Navy in the four years of its Second World War: all these read as a kid, reread as an adult, and by the by, picked up by my older son, perhaps pointing him toward his own Navy career.
Now, that’s a cautionary tale! Parents! Be careful what reading material you leave around for your kids to find! Or, maybe, turn off the TV and read a book or two — you are influential beyond your ken.
Faithful reader might recall a couple of recent posts with the Navy as the theme (here and here).
In these unfortunate times of general governmental ineptitude, cultivated by an administration that consistently over-controls what should be left alone (found any weapons of mass destruction in Iraq yet?), and leaves alone too many negligible details (such as: armor for Humvee personnel carriers!), why should the Navy be left out?
Lesson on How Not to Build a Navy Ship
By PHILIP TAUBMAN | Published: April 25, 2008
With the crack of a Champagne bottle against its bow, the newly minted Navy warship, bedecked with bunting, slid sideways into the Menominee River in Wisconsin with a titanic splash.
Moments before the launching on Sept. 23, 2006, Adm. Mike Mullen, the chief of naval operations, told the festive crowd of shipbuilders, politicians and Navy brass assembled at the Marinette Marine shipyard, “Just a little more than three years ago, she was just an idea; now Freedom stands before us.”