Sea Stories: Nicknames Are Bad
After 24 years of naval service, I feel comfortable providing an addendum to the standard Laws of the Navy; Excepting aviators, it is nearly always a bad sign if your boss has a nickname. Smokin Joe. Iron Mike. Cut-Me-Own-Throat Dibbler. If assigned to a ship with one of these bastards in charge, you are well and truly screwed. While our pilots get cute “call signs” e.g., Maverick or Walleye, assigned during their training process, black shoe officers will only receive a nickname in the course of a lengthy career of memorable behavior, such as certifiable insanity, slave-driving brutality, or spectacular hair-trigger temper.
Don’t get me wrong: These guys are almost always supremely competent and highly effective in the right circumstances. Frequently they are assigned to a specific unit because of their reputation, perhaps as a “fixer” for a ship or command experiencing a particularly troubling problem. I have worked for several nicknames. In the late 1990’s, I was in a squadron of destroyers and frigates lead by Commodore Smokin’ Joe.
Smokin Joe was a bit of an anomaly: unfailingly polite, relentlessly calm, unflappable. I can recall no instance in which he raised his voice or cursed any sailor. He was an intellectual, brilliant, highly educated, and in continual need of a haircut. He was possessed of a work ethic like I have never seen. He had the energy of three men, all of it directed exclusively into his job. And as a matter of deeply held faith, Smokin’ Joe believed that everyone else in his sphere of influence should as well. He worked constantly, and so did his staff. He had no known outside activities. Even while in port, a light week at the office included 80 hours with some of it on Sunday. Out of desperation, a group of junior officers seeking to distract him bought him a puppy. It ended up back at the pound within a week. When we heard he had married, we assumed it must have been an arranged marriage or perhaps a mail order; we could see no way in which he had time for courtship.
His direct staff, a dozen or so officers and chiefs, were continually at the edge of exhaustion. We lucky ones, merely stationed on one of his ships and thus protected by the sovereignty of our Captains and a couple of layers of command, both pitied and hated them. The Commodore’s remorseless pursuit of squadron perfection came at us via these staffers. Their interference with our daily routine was constant and aggressive. During the standard in port workday, we fielded a continual stream of queries, “requests” for information, direction on specific issues, interrogatives as to when they might expect the next update, and firm “recommendations” on appropriate courses for any and all planned activity. After standard working hours, this continued unabated into the night, forcing the 24-hour rotating duty section to respond as best they could or stiff-arm if possible. God, how we cursed them. The Commodore himself was so damn likeable; we directed much of our irritation towards his minions. They were not “The Staff,” or “the DesRon” (Destroyer Squadron), they were “The Fucking Staff.” And they were on the phone. Again. It became normal. And we were the best damn squadron in the Navy. We just didn’t realize it.
When he left, the officer wardrooms of four navy ships breathed a collective sigh of relief. Finally, we could operate like a normal squadron. We could run our ships and departments, rather than the Commodore trying to do it by proxy. We were happy as clams. At first.
It started with little things; queries to DesRon went unanswered. The Staff seemed unaware of significant events happening on our ships despite standard reporting. Long term multi-ship planning slacked off. And almost without even realizing it, certainly without recognizing the absurdity of it, we caught ourselves noting aloud that “This wouldn’t have happened under Smokin’ Joe.” Against all odds, we missed our old staff. We missed their near infallibility, their supreme competence, their constant push for better and more.
Things didn’t work out too well for Smokin’ Joe. He only made three stars, and now has to work with these blokes. But at least he got to command some ships for a while.
Ha! Great stuff.
I can only imagine what pure hell a man of those qualities must endure, given the organizational culture of his new workplace.
Comment by Rojas — 3/7/2008 @ 11:15 pm
I have told several colleagues, anyone who would listen in fact: Even knowing little about his policy positions, I can think of no man I have ever known more suited for Congress. He is brilliant, unflappable, and driven. Pennsylvania is lucky to have him, and not just because he sent Weldon packing. But I pity his staff. I suspect their turnover rate is quite high.
Comment by Jack — 3/8/2008 @ 12:02 am
Fantastically told.
Comment by Cameron — 3/8/2008 @ 3:42 am
Thanks Cameron. I have a couple more like this in the hopper, but none involve anyone quite as famous as Smokin’ Joe Sestak.
Comment by Jack — 3/8/2008 @ 11:05 pm
Your post today inspired me to re-read this one. There’s a marvelous gem in the Wikipedia article of Smokin’ Joe.
The article from which that is derived from states the same thing and is called “Rep. Sestak’s staffers keep jumping ship”.
Awesome.
Comment by Cameron — 4/17/2009 @ 9:18 pm
Rojas and Jack’s comments in particular will be bronzed soon.
The man may soon be locked in the biggest race in the country. The grumblings in PA and the liberal blogosphere in general lead me to believe they’re ready to rally (and fund) an ABS candidate, and that any day now that dam’s going to burst, and Smokin’ Joe is right there ready to ride the wave. If it were just some congressmen I might say it was too long a shot. But given the comments here, I’d be scared shitless if that was the guy on my tail (he also ran a hell of a race in 2008).
Comment by Brad — 5/6/2009 @ 7:58 pm
Heh…in the interval between initially reading this post and Brad’s latest comment, I have read the requisite novels to catch the Pratchett reference. :)
Comment by Rojas — 5/6/2009 @ 11:41 pm
Jack, I was in the same squadron at the same time… Where we on the same ship?
Carney OPS
Comment by CarneyOPS — 1/20/2010 @ 12:47 am
Yes we were. Feel free to shoot me an email at the site’s contact address, and I will reply with my personal email.
- Jack
Comment by Jack — 1/20/2010 @ 12:44 pm
Senator Sestak, soon?
Comment by Adam — 5/19/2010 @ 10:49 am
I spent a cruise with Commodore Sestack and RMDL Mullen on the USS GEORGE WASHINGTON. I was on the Battle Group staff so Sestack worked for Mullen. Never have I seen a sorrier officer. He took the SWO community eats their young to a new level. In reality as the SCC he had no job, had constant oversight from the staff in TFCC (two frames forward) and provided nothing to the situational awareness of the Battle group. He did however work his staff to exhaustion to feed his overblown sense of self importance. He added nothing.
Comment by 68RS — 5/20/2010 @ 8:04 pm
I was also on that GWBG deployment, and I respectfully disagree with nearly every word you have said, with the exception of the “he worked his staff quite hard” theme. Which sounds naughty. But I will leave it as written.
Comment by Jack — 5/21/2010 @ 8:46 pm