Somebody at Thursday game night, I think it was during a lull in Ark Nova while two people argued about a card interaction, asked how I got through Development as Freedom without wanting to throw it across the room, since a couple of us had tried and bailed. I said something glib about being used to boring paperwork, and then actually thought about it on the drive home and realized it wasn’t glib at all, it’s just true, and it’s the actual shape of my day job leaking into my reading life in a way I’d never examined.

Claims audit, at least the way I do it, means reading a chart note line by line against a billing code, looking for the one place they disagree. Most of the note is fine. Most of it is boilerplate, visit type, provider, standard language repeated across a hundred other charts that day. The job isn’t reading for enjoyment, obviously, it’s reading for the discrepancy, the one sentence that doesn’t match what got billed, and you develop this specific kind of patience for wading through repetitive material because you know the thing you’re looking for is probably going to show up eventually, and skimming risks missing it.

That is, it turns out, exactly the skill a book like Sen’s needs. He restates the same three or four points across two hundred pages, type A freedom versus type B versus type C, and I can see why people give up, because on the surface it reads like nothing new is happening for pages at a stretch. But I wasn’t reading it like a novel. I was reading it the way I read a chart, waiting for the discrepancy, the place where the restatement actually shifts the argument half a degree, and when I found it, the Adam Smith chapter, it felt exactly like catching a miscoded line. A small, specific, real payoff buried in a lot of necessary repetition.

I don’t think this makes me a better reader than anyone else, and I want to be careful not to claim that, because plenty of people who’d bounce off that book are sharper readers than I am in every other way. It’s just a different tool, sharpened somewhere I didn’t expect it to be useful. I catch a coding error by refusing to let my eyes glaze over paragraph four just because paragraphs one through three said nothing new. Turns out that same refusal works on Amartya Sen.

I still think an editor should have cut that book by a third. Being equipped to survive the padding isn’t the same as thinking the padding should exist.