Pages

January 3, 2015

A Win-Win for Gun Control

Let's start with a few facts and figures. According to GunPolicy.org, the total number of rifles, shotguns and pistols in the United States is between 270,000,000 and 300,000,000. That's enough to outfit every man, woman and child with some sort of weapon. Of course, not every household has a weapon. A CNN article on guns reports that gun ownership, like wealth, is highly concentrated, with about 20 percent of gun owners possessing 65 percent of all guns. Still, one out of every three households has a firearm of some kind.

With that many floating around, it's obvious that the manufacture of firearms is big business. ATF reports that in 2012, there were over 8 million rifles, shotguns, and pistols manufactured in the United States. Of these, a bit less than 300,00 were exported. In that same year, the United States imported 4.8 million firearms. In 2013, that figure went up to 5.5 million firearms imported. (I found it interesting that Austria is our largest external supplier of handguns, with Germany a very distant second.) What that comes down to is that in a given year, we add well over 10 million firearms to the national arsenal.

Okay, so we know there is already an abundance of firearms in the United States, somewhere near enough to outfit every living person in this country with a weapon. In 2012, we manufactured 8 million more, and as if that wasn't enough, we imported another 5 million. With deaths from firearms making the news every day -- in 2011, 32,000 people died from firearms; another 81,000 were injured ... we're Number One!  -- a lot of folks who think there are way too many handguns in this country are searching for a solution that doesn't violate the Second Amendment. Here's my win-win suggestion for gun control: Buy America. That's right, ban the import of firearms. If that's too much for you to swallow, than limit the importation ban to handguns.

With that simple step we accomplish two things. First, we create more jobs here at home because for damn sure, the demand for firearms won't abate overnight, so domestic production will have to ramp up to fill in the gap. Second, we take one small step towards reducing the influx of weapons. We don't need to import firearms. As I said, it's a win-win. Sure, there may be some high-end rifles that are truly for sports or hunting, but handguns ... I don't think so. As Jack Nicholson said in As Good As It Gets, "Sell crazy someplace else, we're all stocked up here."


December 31, 2014

Boss Man

I'm typing this on a Bluetooth keyboard that is linked to my tablet. The whole kit and caboodle easily fits inside a place mat on my kitchen table. That's a far cry from the first automated typing system I used.

This  was back in 1970 when I had just gotten out of the Army. I decided to remain in DC rather than move back to Boston mostly because I already had a job guaranteed me at the U.S Department of Agriculture, plus there was a recession on. So resigning myself to a life of mere money-making, I returned to USDA and settled in at my old agency, The Agricultural Stabilization and Conservation Service, a bureaucratic behemoth that ran all the farm subsidy programs.

I was put into a section that was responsible for issuing internal procedures, a massive library of manuals that filled an entire wall of book cases. This was an era still dominated by paper. An army of clerk-typists churned out ream after ream of paper drafts using electric typewriters, which at that time were the ultimate in electronic sophistication.

But just as the invention of the typewriter wiped out the copyist profession, so too were regular typists about to find themselves on the cutting edge of job extinction. These were the early days of office automation. The newest wrinkle was the word processing center. There were only a handful in the entire Federal government: two were in USDA, and for some reason, I was put in charge of one of them, most likely because no one else was willing to do it.

We used IBM MT/ST's, large rectangular boxes packed with vacuum tubes that were connected to specially-fitted IBM Selectric typewriters. Documents were encoded on magnetic tape about an inch wide. (You could actually see the magnetic coding of each letter on the tape, that's how big these things were.) The idea was you could revise segments of a document without having to retype the entire document. Since our issuances were redrafted many times, it seemed like a word processing center would make things more efficient.

My staff consisted of four black ladies, most of them a bit older than me, most of them reentering the work place after having had children. This was my first time supervising anyone, much less a group of women. The times they were a changing, and black power and women's rights were at the forefront of social change, and there I was, stuck in the middle of it all.

I learned a lot about supervising in the year or so I ran my little unit. As time passed, some of the ladies left for other work, others were promoted within my larger unit, and some were asked to leave. My greatest satisfaction came from recognizing talented people and getting them into better positions where they could advance and build a true career. I made some friendships that lasted my entire career at USDA.

Eventually, I was given a chance to join the regular staff. I spent the next several years editing issuances. Trust me when I tell you that pride of authorship could easily be the eighth deadly sin. Over the years, I learned what it takes to be a professional, to be able to do decent work even on the days you didn't feel like doing anything. I also learned that work should never be more important than the people doing the work.

For the rest of my time at USDA, writing and office automation would be the two abiding  elements of my work. I was lucky enough to ride the wave of personal computers and the Internet into a full-time job as a computer specialist, web designer, and programmer. Writing was an integral part of building web sites, as was the willingness to tear things apart and rework them endlessly until it was as close to just right as you could get it, something I learned in my years as an editor.

If you had asked me as a young man what I would do for my life's work, nothing of what I actually ended up doing would have made the list. No way would I have seen myself as a supervisor or an editor or a computer type. I just went with what I had at the time. I never said "no" when asked if I wanted to try something. But I always found a way to carve out a space at work that was my own, a space where I could take a chance on something new, where I could try something different and prove to myself and to others that I could get it done and that it was worth doing. For me, that's about as good as it gets.


December 21, 2014

Rush to Judgment

The Kennedy assassination is perhaps the most studied moment in modern history. The Warren Commission took nearly a thousand pages to arrive at conclusions that were immediately contested. The Zapruder tape has been dissected frame by frame. The events of that day have been painstakingly recreated many times. No event has been examined in more detail, and yet I doubt that anyone would say that the truth is fully known.

The Greek dramatist Aeschylus wrote that in war, truth is the first casualty. I would argue that the truth of anything is impossible to know, a truism we ignore at our own peril. Nowhere is this more evident than in the recent events in Ferguson and New York, events that more and more seem to have played a part in yesterday's killing of two NYPD patrolmen in Brooklyn.

The specific circumstances of Ferguson and New York have been gone over and over. Like the Kennedy assassination, there were many eyewitness accounts and videos of the events as they unfolded. Yet, after all the testimony both oral and visual, what do we really know? Two black men were involved in physical confrontations with white police officers (although in New York, the on-scene supervisor was not white). Both black men resisted arrest. In both cases, the policemen involved reacted with what turned out to be deadly force. Two men ended up dead in circumstances that no one thinks should have had that outcome. The debate goes on as to who was most responsible for what happened, who could have or should have shown more restraint.

If either side had reacted differently, perhaps we wouldn't be where we are today, dealing with another tragedy. A young man decided to kill the things he hated -- an ex-girlfriend, two cops and finally, himself. The debate will rage over what role the overheated rhetoric stemming from protests in Ferguson and New York played in motivating his actions. We may never know for sure. Clearly, this guy had a lot of problems we have yet to fully understand.

That won't stop the endless speculation on CNN and social media, or in the comments sections of online articles. It's funny how we always are told not to trust the media. But here's the thing: in today's world of Twitter and Facebook, we the people are the media. So, yeah, don't trust the media. Always keep in mind another truism: believe half of what you see and none of what you hear. How often do we need to see initial impressions turned on their head by later insights to remember not to rush to judgment?

We can never know the totality of events surrounding a moment in history, even when we watch events unfold on video. We can never know what was going on in someones head, what totality of life experiences influenced what they were thinking and feeling during a crisis. The truth of anything is impossible to know.

December 15, 2014

Midrash

There's a reason why the Pharisees get such bad press in the Gospels. They were the Christians' chief challengers in the struggle for the hearts and minds of the Jews in the immediate aftermath of the Second Destruction of the Temple by the Romans in 70AD. In fact, the Pharisees believed in the primacy of the Golden Rule and placed the highest value on compassion when seeking guidance from scripture. But every story needs a villain, and the Christians conveniently chose their arch-rivals to fill the bill.

As a way of coping with the loss of the Second Temple, the Pharisees continued and expanded a Jewish tradition of looking for new meanings in texts that might help explain what had just happened, a process called midrash. In applying midrash to texts, one skipped past the literal meaning of the words in search of new meanings, new interpretations that would have relevance to present day issues. In her book, "The Bible: A Biography," Karen Armstrong writes: "The goal was never simply to clarify an obscure passage but to address the burning issues of the day."

This wasn't something the Pharisees invented. The idea of reshaping the texts in the Torah to make them more relevant to contemporary audiences had been going on for centuries; nor were the Pharisees the only ones to look for new meaning in old texts. The new kids on the block, the Christians, also undertook to re-examine the Old Testament to find ways in which it presaged the coming of Christ. So yeah, a great deal of effort was expended on rewriting the Bible to fashion a narrative that would explain what was going on, be it the destruction of the Temple or the arrival of a messiah.

There is no better time of the year than Christmas to contemplate the harsh reality that writers don't let the facts get in the way of a good story. The only verifiable fact is that Christ was indeed born. Pretty much everything else we think of when we think of the Nativity -- the manger, the wise men, the virgin birth -- were written into the plot to create links back to the Old Testament in order to bolster the case for Christ as the messiah whose coming had been foretold.

And yet we cling stubbornly to the myth. Why is that? Maybe for the same reason that Hollywood continues to make movies about Moses, a figure who never existed. We need a narrative that explains the ups and downs of life, that connects us to those who went before us, that gives us hope, that somehow makes sense out a world that very often makes no sense at all. Certainly, there is more comfort to be found in the image of the baby Jesus in the arms of his mother than in the enigma that surrounds the riddle of quantum physics. A theory of everything is all well and good, but it doesn't comfort us when we grieve.

We are only human. We still need our gods. We still need our myths. The day that changes is the day we are no longer human. Some might welcome that day. Some might argue that day is much closer than we like to think, that we are well on the way to engineering our successor species. Will our replacements share a creation myth? Will they long for a redeemer, the great programmer in the sky? Or will they sleep a dreamless sleep and awaken to a world governed by algorithms? I for one am glad I won't be around to find out.

November 11, 2014

Flop

So I'm reading this book about Vietnam. Mostly photos, some narrative. The kind of book you flip through without spending a lot of time reading the text. Until you get to page 106. There you find a photo of a letter written by Jim Hart, who was assigned to the 12th Security Police Squad at the Phu Cat Air Base. He was in the Sentry Dog Section. With his partner Flop, Hart patrolled the perimeter of the Air Base. Like all such teams, they grew very close. Inevitably, there came the day when Hart would leave Vietnam. Hart describes the moment he said good-bye to Flop in a letter he left at the Wall:
I didn't want to leave you behind in Vietnam but I had no choice. I told you where I was going and I know you understood. I know you wanted to go home with me, please forgive me. I thought you'd be coming home someday. Had I had any idea the military had no intention of bring you home I never would have left you. The way you looked into my eyes; I really believe you were reading my mind. Coming home was great, but knowing you were still over there bothered me a lot. All these years, I never knew what had happened to you and there was never anyone to talk to who would truly understand what I was going through.
Anyone who has ever owned a dog knows exactly what Hart is talking about when he says Flop understood that he was being left behind by his master. You've seen that look in a dog's eyes when you are leaving, and you've seen the joy they experience at the moment of reunion. To know that moment will never come, to know there will never be that reunion, to know that you are leaving behind a partner who day after day, month after month, gave you total loyalty, total love ... Jesus Christ, how do you deal with it?

If there was ever a more gut-wrenching description of the cost extracted by a war, I haven't come across it. I read the descriptions of My Lai in that same book and was largely unmoved. Maybe unmoved is the wrong word. My Lai is something I don't dwell on, because you have to be willing to ask yourself if on that day, having gone through what the soldiers of Company C had gone through in the days and weeks leading up to the tragedy ... you have to be willing to ask yourself if you would have stood up or stood by. Anyone who says they have the answer to that question just doesn't get it.

If you are wondering what happened to Flop, what it was that Jim Hart found out, well, it's just what you might think if you imagined the worst possible outcome. Left behind by his master, Flop went from handler to handler, each of whom went home and left Flop behind. Finally, Flop had had enough and refused to work with anyone else. The Air Force put him down.

On this Veterans Day, if you want to think about war and what it does to the people who are caught up in it, then the story of Flop is as good a place as any to start. You come to understand that the war never ends. You leave it behind, but it comes home with you, a feeling of unfinished business that hangs over you for decades. No matter what you did, whether you were a grunt or a cook or a boy with a dog, so much is given, so much is left behind, so many wounds to the heart, wounds too painful to talk about even if you could find someone to talk to. We ask too much. Always, we ask too much.

Flop with Jim Hart
 The book is "Not Yet At Ease: Photographs Of America's Continuing Engagement With The Vietnam War," written by David Chananie.

October 11, 2014

Fifty Years After

An article published today in the New York Times takes a look at the controversy surrounding the effort by the Pentagon to stage a 50th Anniversary Commemoration of the Vietnam War. Which raises an interesting question. How do you commemorate a war that was a mistake, a war whose soldiers were branded as drug-addled losers and baby-killers, a war that was detested by a significant percentage of the population, a war that began with a lie and ended in defeat and chaotic retreat? Somehow, a pat on the back and a "thank you for your service" doesn't seem to cut it.

For that matter, whose war will we commemorate? Is it about the men and women who fought in it, the politicians and generals who got us into it and kept us in it, or the men and women who tried to get us out of it? That debate remains robust, judging by the comments that accompanied the article in the Times.

Most of the attention has focused on the web site, in particular an Interactive Timeline that purports to show the key events of the war. The gist of the objections is that the web site is just another attempt by the Pentagon to write a history of the Vietnam War that glosses over unpleasant events such as the massacre at My Lai and underplays what many people see as critical elements of the story, most especially the scope and impact of protests against the war.

There is some meat in the web site, especially the part called Primary Documents, a work in progress that includes many valuable source documents, including extracts from the Pentagon Papers and key diplomatic reports. Anyone seriously interested in learning the history of the Vietnam War should start there. Personally, I found the Interactive Timeline to be a failed effort, at least in this iteration. It's hard to say this without sounding disrespectful, but the decision to include the citations for every Congressional Medal of Honor winner in the timeline seriously disrupts the flow. Better there should be a separate area that lists all the CMH winners, with links to each citation from the related battle or action in the Interactive Timeline. Equally baffling is the lack of links from the Interactive Timeline to the Primary Documents area.

All that is beside the point. The Vietnam War has always been about more than the war and those who fought it. It was also about the changing times during which the war was waged and the changing attitudes of the American people towards their government. A social revolution became a political revolution as opponents of the war took to the streets to protest our involvement in Indochina. No history of the Vietnam War is complete without that chapter, and therein lies the difficulty with a Pentagon-sponsored history. Even fifty years later, it is clearly hard for the military to give anything more than lip service to a movement that at the time was seen by them as giving aid and comfort to the enemy.

For me, the reasoning behind the program --"to thank and honor veterans of the Vietnam War ... for their service and sacrifice on behalf of the United States and to thank and honor the families of these veterans" -- rings hollow. I'm sorry, but the brutal reality is that the hardest part of being in the Vietnam War was coming home. There was no grateful nation, there were no parades, no flag-waving greeters at the airports. Instead, we Vietnam veterans returned to a decades-long shunning by our peers and by many who served before us. We were the perpetrators of  horrors witnessed night after night, year after year, in the Living Room War. It was there we suffered our greatest defeat.

I had a chat recently with a Korean War vet. I said to him that they were the truly forgotten vets, which he agreed with completely. But all the while I was thinking that there's worse things than being forgotten. If we must somehow commemorate the Vietnam War, then let us do so by facing unflinchingly the hard facts about how we got into the mess, and how we got out of it, and what lessons we learned and have already forgotten. Nothing less will properly do justice to the millions caught up in the war, no matter what side they were on.

October 5, 2014

October Surprise

On October 5, 1968, I left the U.S. of A and headed west -- far west, all the way to where it turns into the Far East -- to begin my tour of duty in Vietnam. In the years after I came home, I would have this vague sense of unease around October, as if I couldn't quite find my bearings or keep focused on things. The shrinks have a name for this: anniversary syndrome. If you think about it, I'll bet you could rustle one up as well.

I am unaffected by it, for the most part. The flame of memory has long ago dampened to a mere flicker. A life has unfolded during the decades after my war ended. Each year pushes the memories further into the vault. But they never quite go away. Somewhere in the deepest part of my brain, nestled among some gnarly old neurons, they wait patiently for their moment to arise.

This year, many things have conspired me to get me thinking about that time in my life. An old friend from college comes for a visit and we go to see the Vietnam Wall. A guy I knew in the 1st Infantry Division gets back in touch after 45 years. Another guy I never met gives me a book about Vietnam. All of a sudden, I'm knee-deep in Big Muddy again, metaphorically speaking, of course.

So maybe it's no surprise that while I was cutting the grass I got to thinking about this guy I knew when I was working at USDA. Vietnam vets rarely talked to anyone about their time in country, and that included other vets. But K. and I worked together and soon enough discovered the big elephant in the room that we both shared living space with.

We would talk, K. and I, or rather he would talk and I would mostly listen.  I had a tour of duty; he fought in a war. My memories were of long shifts in the Tactical Operations Center listening to the war over the radio, spiced with nightly rocket and mortar attacks. His memories were of kicking his way into hooches, M-16 locked and loaded, a shotgun slung over his shoulder, a pistol tucked in his belt, and a knife stashed where he could quickly retrieve it. When he talked of those times, he would get that faraway look in his eyes -- not quite the 1000-yard stare, but close enough to it.

One day he came back from lunch and rushed into my office looking especially wild-eyed. He had been minding his own business when an old lady had her purse snatched. K. chased after the mugger, tackled him to the ground, and proceeded to beat and kick him to within an inch of his life. The cops had to pull him off. I think he was shocked at his own actions, and maybe a little bit scared by it. I tried to talk him through it, but we both knew it wasn't good.

The fact that his personal life was a mess didn't help. He was in a marriage that was doomed by his PTSD, and it didn't help that he was a good looking guy, the kind of guy who drew looks from the girls when he walked into a room. It was such an ego-boost for me when one of them would sidle up to me and want to know who that guy was. Yeah, thanks for asking.

Eventually, things fell apart and K. left town for a new job and a new woman. I never saw or heard from him again. I hope he found a way to live a reasonably normal life, although truth be told, K. always struck me as one of those people destined to live outside the bounds of normal. Then again, I doubt that any returning vet has much luck in finding normal any time soon.

I consider myself to be one of those lucky ones. I have incorporated the good, the bad, and the ugly into a workable 2.0 version of me. It's all good now, except maybe on a crisp October day when the wind blows from the west, the leaves rustle in the trees, and time sends a shiver rolling down my spine and I am that young kid waiting to leave on a jet plane, not  knowing when I'll be back again.