Skip to main content

Double book review: Fiasco and A History of Iraq

Summary: These two excellent works complement each other nicely to give an overview of Iraq with a focus on the recent war.

Up today: Fiasco, by Thomas Ricks, and A History of Iraq, by Charles Tripp.

I'll start with the former. Fiasco's main strength is that it is an extremely detailed and well-written account of just what happened to bring the US to war and how the occupation was carried out. The 2003-2004 period is most damning. It was as if Sun Tzu, Clausewitz, Napoleon, Lord Nelson, and Eisenhower had been set on a panel with the express purpose of designing a strategy to fail as utterly as any in history. The unbelievable stupidity and incompetence of the high command, both military and civilian, is distinguished from the performance of the actual soldiers, which mostly seemed haplessly unprepared for the conflict they were dumped into, but tried to make the best of an impossible situation. Later, after some shakeups at the top command, techniques that were at least in the same galaxy as sanity were implemented with some positive effect.

However, I struggled with the book's essential sympathy for the nation building project. Ricks details the more successful efforts of leaders like David Petraeus and H.R. McMaster, who were able to understand and implement better tactics for fighting an insurgency and building a country. I summed it up in my own mind as 2/5ths Marine Corps, 1/5th Army Corps of Engineers, and 2/5ths Peace Corps. This and the catastrophic yet easily avoidable mistakes at the beginning of the war combine to make an account that in many respects doesn't discredit the doctrine of pre-emption (indeed, Ricks explicitly states he could still support such a policy in the right circumstances), but rather tries to salvage it. I have to grudgingly admit that Ricks' account convinced me that such things are possible in theory, but he doesn't really grapple head-on with the policy issues raised by the doctrine of pre-emption.

Tripp's book, on the other hand, gives that broader perspective. It is a serious academic work, a kind of shallow overview for the nonspecialist or historian looking for a place to start deep research. It's a bit of a slog at times, but worth it for the overarching narratives that were driving a lot of what happened during the US invasion that Ricks, buried deep in the details, misses. Iraq's initial boundaries, a relic of the collapse of the Ottoman empire based entirely on political convenience, are described in the context of the British colonial action after WWI. The long history of monarchy and of increasingly violent coups by military leaders is followed, logically ending with the ruthless Saddam Hussein. The American occupation is given the same kind of treatment as every other Iraq regime, and tied into the narrative threads of the previous history, something the Ricks does not do.

Comments

Popular posts from this blog

Why Did Reality Winner Leak to the Intercept?

So Reality Winner, former NSA contractor, is in federal prison for leaking classified information — for five years and three months, the longest sentence of any whistleblower in history. She gave documents on how Russia had attempted to hack vendors of election machinery and software to The Intercept , which completely bungled basic security procedures (according to a recent New York Times piece from Ben Smith, the main fault lay with Matthew Cole and Richard Esposito ), leading to her capture within hours. Winner recently contracted COVID-19 in prison, and is reportedly suffering some lingering aftereffects. Glenn Greenwald has been furiously denying that he had anything at all to do with the Winner clusterfuck, and I recently got in an argument with him about it on Twitter. I read a New York story about Winner, which clearly implies that she was listening to the Intercepted podcast of March 22, 2017 , where Greenwald and Jeremy Scahill expressed skepticism about Russia actually b

Varanus albigularis albigularis

That is the Latin name for the white-throated monitor lizard , a large reptile native to southern Africa that can grow up to two meters long (see pictures of one at the Oakland Zoo here ). In Setswana, it's called a "gopane." I saw one of these in my village yesterday on the way back from my run. Some kids from school found it in the riverbed and tortured it to death, stabbing out its eyes, cutting off its tail, and gutting it which finally killed it. It seemed to be a female as there were a bunch of round white things I can only imagine were eggs amongst the guts. I only arrived after it was already dead, but they described what had happened with much hilarity and re-enactment. When I asked why they killed it, they said it was because it would eat their chickens and eggs, which is probably true, and because it sucks blood from people, which is completely ridiculous. It might bite a person, but not unless threatened. It seems roughly the same as killing wolves that

The Conversational Downsides of Twitter's Structure

Over the past couple years, as I've had a steady writing job and ascended from "utter nobody" to "D-list pundit," I find it harder and harder to have discussions online. Twitter is the only social network I like and where I talk to people the most, but as your number of followers increases, the user experience becomes steadily more hostile to conversation. Here's my theory as to why this happens. First is Twitter's powerful tendency to create cliques and groupthink. Back in forum and blog comment section days, people would more often hang out in places where a certain interest or baseline understanding could be assumed. (Now, there were often epic fights, cliques, and gratuitous cruelty on forums too, particularly the joke or insult variety, but in my experience it was also much easier to just have a reasonable conversation.) On Twitter, people rather naturally form those same communities of like interest, but are trapped in the same space with differe