transition

Afghanistan Post Mortem: Readjustment takes time

Stress over time: Fantasy

Stress over time: Fantasy

About three-quarters through the deployment, I could physically feel that my patience, or rather, my ability to be patient, had severely diminished. I found myself getting easily frustrated with things that I would have been able to manage much better earlier in the deployment. My patience had been eroded, but I was cognizant of it, and because I was aware of it, I was able to manage my own impatience (eh, some of the time).

Speaking with other leaders about this, they reported a similar phenomenon. The challenges of leadership coupled with the stress of deployment had chipped away at their mental stores.

And the deployment went on, and then we went home.

Despite the constant drum-beat during re-integration training that war has a significant effect on the psyche, the thought that “everything will be better when we get home” still lingers. While it’s true that the immediate danger is gone, the phsyiological changes that occured and led to our being easily frustrated probably takes time to reset. It’s hard to imagine that the cumulative effect of nine months of deployed life (coupled with the tough training that preceded it) is wiped away simply by crossing enough time-zones and setting feet down on American soil.

Stress over time: Reality

Stress over time: Reality

update

Afghanistan Post-Mortem: The End of War

Well, that’s it.

Having arrived safely in America a few days ago, my deployment to Afghanistan is officially over.

I didn’t really spend much time or energy writing about Afghanistan or the experience of leading a platoon through the end of war for a bunch of reasons I’ll get to in a minute. Still, coming home from war is significant and it feels appropriate to try to try to wrap it up here with some kind of reflection.

For all the fun I had throwing around the ‘end of war’ adage in the lead up to the deployment, the war has not ended and goes on (and on). I suppose I had a slight expectation of learning something unique or new in the same way that I did through participating in the actual physical invasion of Iraq in 2003. That is, learning something about War or the nature of war.

Well, so far, I’ve got nothing.

Without question I learned plenty – being at work for nine months straight has its advantages. I learned about leadership, discipline, morale, personnel management, training, and mission command. I’ve also exponentially increased my technical skills at things like battle tracking, reporting, and building PowerPoint slides – not joking, I’ve gotten pretty good.

I was also fortunate to see how the way we fight has changed, especially when compared to how we did it just ten years ago. For a time, I led a fleet of MRAPs, the final evolutionary form of the doorless humvees we used to zoom around Baghdad in 2003. Getting out the gate in 2014/2015 requires a whole lot more than just sending a head count to the CP before SP.

Seeing things from an officer’s perspective gave me a deeper appreciation for the planning process, and the pressures that come from higher. What would have made me grumble and grunt as a young sergeant was now more fully understood as a lieutenant. I was able to see myself in both sets of shoes, as the leader with the information and the soldier without. I tried my best to close the distance between the two, with mixed results.

I was able to observe the absolute infestation of technology in the way we do work. Afghanistan is often derided as being backwards or “in the stone age,” but one of the first things new leaders do in country is get a cell phone. If so inclined, you can pop a local SIM card into your smartphone and sign up for a data plan, with pretty reliable 3G coverage. Not a day needs to go by without checking Facebook from your mobile device.

And the absurdity of war, in all of its colors, was still there.

This was quite possibly my longest stretch of time in the military where I’ve gone without eating a single MRE out of necessity. As best as I can remember, I ate only one MRE during the entire deployment, and it was for the novelty of it (it was a cold-weather MRE).

Yes, I learned a lot. And I came out of the experience better for it.

But to say that I’ve learned something deeper, some universal truth, would be a lie. It was war, as it was before.

This was my first deployment to Afghanistan, and having only deployed to Iraq before, this felt something akin to adopting a teenager just before he graduates high school. I cared, and wanted to help, but my individual contribution to the overall effort felt mostly insignificant – the hard work was done by others before me.

Some of the NCOs in my unit who had been to Afghanistan before commented on how much quieter the FOBs seemed. Where they were once bustling micro-cities, today they seemed more like ghost towns, Walmart parking lots on an early Sunday morning.

Frustratingly, success at the platoon level was extremely hard to measure. I’m remiss to say that it was a success because everyone came back safely, as many do, because while that’s a good thing, if going to war only to protect yourself is the goal, then maybe we need a better reason to go in the first place.

So far, the best I’ve come up with in describing success is through the metaphor of a relay race: we ran for nine months without ever really knowing if we should be sprinting or pacing ourselves, and then handed off the baton to the next guy before jogging off the track, panting. We have no idea how long the race is or if we’re winning, but we hope that it will eventually end, and at a minimum, we hope that our single lap around the track will not be looked back on as the lap that cost us the race.

As to why I didn’t write more about the deployment – I’ve never really used this blog as a journal or a kind of record of what I’m doing, with the exception of the occasional significant update. Honestly, it would probably have been a lot more interesting if I did keep a day-by-day blog. I know I would have enjoyed reading about what the end of the Afghanistan war looked like from the point of view of a small unit leader on the ground.

That kind of writng contains too many pitfalls, though. As other young lieutenant’s have learned, beyond OPSEC concerns, there are challenges to writing about the current goings-on in your unit, and those challenges are heightened when deployed, as a friend of mine learned when he was chided by his command for writing a gentle piece for the New York Times’ At War blog while still deployed.

I posted a couple of cryptic pieces through the deployment to try to cast a shade as to what was going on, but they went mostly unnoticed. I did keep a log of things that I thought would be interesting to write about eventually, and now that I’m home, I’ll get to them.

Having done this before, and being very aware of the way that war doesn’t end neatly or conveniently at the very point that the soldier returns home, I’m mindful that in time, some greater meaning or idea may come to me. I’m still very much in the honeymoon phase of redeployment, teetering between the joy of reliable hot water and plentiful alcohol and the bitter understanding that the strangers around me don’t know or care about what I have just done.

Walking into a coffee shop I frequent over the weekend, the owner greeted me by name and took my order, indifferent to the fact that he had not seen me for nine months and this was the first time I had stepped into his shop since last summer. He acted normal, and in kind, I acted normal. I bought my coffee and left like I had dozens of times before. Nothing changed. No excited “welcome home” or probing questions.

Honestly, it was refreshing, in a way. I just wanted my coffee, and I didn’t really want to stand around and try to wrap up “what it was like” in a sentence or two.

I drove home, confused. Did he not realize I had been gone? He knew I was deploying – I even had my wife send me coffee beans from that very shop. Maybe, I thought as I pulled into my driveway, he was doing me a favor, helping me along to get “back to normal.”

The episode reminded of the ending of American Psycho (the movie), where Patrick Bateman, having just admitted his crimes to his lawyer who dismisses them as a joke, sits in front of a sign that reads “This Is Not An Exit” and stares blankly, understanding that his confession has meant nothing, he has achieved no catharsis from his crimes.

It has been a long and short nine months. In a strange way, the whole thing kind of feels like I just stepped through a portal at the end of season 4 of Game of Thrones and came out at the other end just in time for season 5.

I’m looking forward to leave.

language

Grunt Lingo: Chow

IMG_4989

Waiting around is just part of being in the Army. And when the only thing you’re waiting on is an arbitrary date and a wake up, life tends to revolve around chow. “Chow” is the military’s catch-all term for food. You’re never going to breakfast, lunch, or dinner; you’re going to “chow.”

I hate chow.

Or rather, I hate the term “chow.”

I heard it on my first day in the Army, bitter Drill Sergeants at 30th AG telling us they’d get us “through chow” as soon we got off the bus. I understood that they meant we’d be eating, but I had only ever heard the word chow spoken in reference to dog food.

The sign above the door clearly read “Dining Facility” but the Drill Sergeant insisted on calling it the “chow hall.”

Years would pass, and I’d eat chow every day, telling others I was going to chow. At worst, I’d insist to my wife that we “grab some chow” before beginning the day’s adventures on a vacation.

There is something about the ultra-utilitarian nature of the word, stripping food down to its most basic element, nourishment, that makes it so unappealing. Despite its poor reputation, military food can be quite good at times, and by calling it chow, it somehow manifests itself in my mind as slop or gruel to be shoveled onto a flimsy tray before spilling over onto my hand and the floor.

It’s a term I’ve never heard people outside of the military use, yet it persists within and outside of the military among veterans with a strangle-hold unparalleled compared to other military terms, like “squared-away” or “latrine.” When I was attending college with other veterans, we’d grab each other up – some of us separated from the service by over a decade – to go down to the halal cart on the corner to grab “chow.”

Its pervasiveness is absolute, and I don’t know its history or when it started, though I’d guess that it goes back to at least the Vietnam era, where we get a lot of our best terminology.

language

10 Days and a Wake Up

VietnamScrawled on the inside doors of latrines were dozens of instances of one singular phrase: “63 days and a wake up.”

10 days and a wake up.

36 days and a wake up.

If deployed, 414 days and a wake up.

Initially, I remember being very confused by the term, because I rarely heard it spoken, I only read about it in bathroom stalls, porta-johns, in wooden shacks at the rifle range, and in soldiers’ wall lockers. Wherever I found it, the phrase sat their, etched with the kind of certainty and legendary wisdom that colors most military language that keeps outsiders at bay.

Eventually, other new soldiers began using the phrase themselves and I wondered how they were clued in on what it means, exactly, themselves. I figured that most new recruits were just as clueless about the intricacies of military culture as I was, and the first place they encountered the phrase must have been in the bathroom as well.

This is a recurring theme of military service – wondering if everyone else knows what’s going on (they don’t).

The phrase is a way for soldiers to count down the days left of a tour, whether it be combat or training. If a soldier has 22 days left before the end, and he is leaving on the 22nd day, he has 21 days and a wake up. I always figured instituting the “wake up” was a way of making the event seem shorter, even if only by a single day. It’s also true that on the “final” day of a rigorous training school or deployment, the excitement of it ending is enough to erase the day’s monotony and pain.

A few cursory searches of the term suggests it originated in Vietnam. I don’t know how prevalent the phrase is today, but I still hear it thrown around every now and then, so it’s still alive.

army myths

Army Myths: Unhook your chest strap and you get 10% more inflation

6a00d8341bfadb53ef01156f8e863d970c

Before a jump, paratroopers spend a lot of time waiting around. The airborne timeline is notorious for having you show up at 0300 for a 2359 time on target, and most of the time inbetween is spent bullshitting with the guys next to you.

Invariably, talk will turn to how much jumping sucks, and how to make it suck less.

A myth that I heard over and over from “senior” E4s and junior NCOs was that if you unhooked the chest buckle of the T-10D parachute during your descent, your canopy would get a little extra inflation. On more than one occasion I heard that it would give you 10% “more lift.”

I remember being skeptical upon hearing this at first. I understood the theory, that by unhooking the chest buckle it would theoretically allow the risers to expand out more, thus allowing the canopy to also expand, letting in more air and slowing the descent.

I dismissed their claims, and they dismissed my dismissals as naive.

The only way I’d know for sure, they said, was to try it out myself.

New paratroopers are unlikely to risk touching any of their equipment during descent out of fear – better to just ride it all in than to touch something you shouldn’t touch and risk a gory way to die.

After making a certain number of jumps and feeling confident that I kind of knew what I was doing, I decided to finally test the claim for myself. During a “hollywood” (no equipment, day time) jump on a pleasant day, I unhooked my chest strap during my descent to see if it would do anything.

It didn’t.

I
fell to Earth, at more or less the same speed as I was before I unhooked the buckle.

Airborne.