What Dexter Filkins Actually Got Right About These Wars
Most war books try to cover everything. The Forever War By Dexter Filkins does the opposite. It zeroes in on specific corridors of conflict — a patrol route in southern Afghanistan, a backroom in Baghdad, a military base that shifts function every few years — and stays there long enough to show how things actually erode over time. That's the main thing to understand before you pick it up. Filkins was embedded with U.S. forces and embedded with various Afghan and Iraqi factions during the 2000s. The book is structured as a series of linked pieces rather than a single continuous narrative, which sounds disjointed but is actually the whole point. These wars don't have neat arcs. He lets them breathe across twelve to fourteen years of reporting, showing you the drift instead of a climax. I've read a lot of military history from this period. What separates this from the rest is the patience. He doesn't rush to conclusions about who's winning or losing. He watches the same places repeat the same failures. That's more useful than any tactical breakdown I've seen from people who were actually there.
If you want the actual text, it's available through standard channels — Penguin Press published it, and you'll find it on Amazon, Barnes & Noble, and most major retailers. There isn't an official free PDF that I'd recommend. The used book market has it cheap, which is often the better route anyway.
What most people miss about the reporting
Here's something that won't show up in any summary: Filkins gives equal narrative weight to the Afghan warlords and the American officers trying to manage them. That balance is deliberate and mostly absent from other accounts of this period. You get the sense of two parallel governments operating in the same spaces, neither acknowledging the other, both failing in different ways. Another thing that's easy to overlook is how much the book documents the failure of institution-building. Not the grand strategic failure that gets discussed in policy circles, but the daily friction — the moment when a $2 million school closes because nobody knows how to pay the heating bill, or when a district council dissolves over a dispute about a parking lot. That level of detail is what makes the later chapters land harder than the earlier ones.
Get the Full Details
Where it falls apart
I need to be honest about the limitations. The piece-by-piece structure means you lose momentum if you're looking for a clean through-line. Some readers find themselves flipping around trying to reassemble the timeline, which is fair. The book assumes you already have a working knowledge of the general sequence of events in Afghanistan and Iraq, and if you don't, you'll need to supplement it with something more chronological. There's also a blind spot regarding the drone program and the covert side of the war. Filkins covers the visible conflicts thoroughly, but the shadow infrastructure that developed alongside the conventional forces gets less attention than it deserves. If you're trying to understand the full picture of American military operations in that period, this book is necessary but insufficient on its own.
How I use it when people ask for recommendations
When someone tells me they want to understand the wars in Afghanistan and Iraq, I don't hand them this book first. I give them it second. Start with something like Tim O'Brien's A Thing That Happened for the human texture, or Michael Ignatieff's work on the broader strategic failure, then come back to Filkins for the ground-level continuity that most history books skip over entirely. The real value here is in the repetition. You keep seeing the same patterns across different years, different commands, different cities. That's not an accident in the writing. It's the book making its argument without ever stating one outright. You finish it knowing less about who won than you did going in, which is probably the most accurate takeaway available.
