About Alex Drost

I work in middle-market investment banking and advisory as a Vice President at Cascade Partners, in Detroit. I am a CPA, licensed in Michigan. Before that I took a BBA in Accounting and Finance at Northwood University, and later an M.S.F. in Corporate Finance at Walsh College.

That background explains a lot about what is on this shelf. Deal work is professional pattern-matching: you spend your days looking at businesses that resemble other businesses, and the useful instinct is not recall but recognition — noticing that the thing in front of you rhymes with something you have seen before. Reading turned out to be the same exercise run at a larger scale, so I started treating it that way on purpose.

What this site is

This is a public catalog of what I have read — 330 books, nearly all nonfiction, each with a short summary, a few core ideas, and a set of hand-made links to other books on the shelf. There are 1,037 of those links. None of them were generated by similarity scoring. Each one is a note that two books are arguing with each other, or that one is the prequel to another, or that a claim made confidently in one gets dismantled in the next.

The catalog leans heavily toward politics, power, history, and the institutions that hold both. That is not a curated posture; it is just what the record says when you write it all down. The shelf also does not carry ratings, and never will. A five-star scale flattens the only interesting question — what did this change — into a number, and I would rather write the sentence.

Elsewhere

I serve on the board of the Association for Corporate Growth, and I am a recipient of the MICPA Emerging Leader award. I hosted the Branch Out Podcast for more than 100 episodes; the archive is still up, though the show is no longer in production.

How this shelf gets built

Books enter through Goodreads, which remains the system of record for what I have actually finished. From there each one is enriched — summary, core ideas, themes, tags, connections — and the finished record publishes to this site. Nothing here is written by a recommendation engine, and nothing publishes until I have looked at it.

If a book on this shelf sends you somewhere I have not been, there is a "Recommend a book" link on the home page — the shelf gets a lot of its best entries that way.

Why I track the connections between books

I have kept a reading list for years, and for most of that time it did what reading lists do, which is very little. It recorded titles and dates. It was a receipt. When someone asked what I had been reading, I could tell them the last three books, and when someone asked what I had learned, I could usually manage one idea per book, badly.

The problem was not memory. The problem was that the list had no shape. A list is a sequence, and a sequence implies only one relationship between any two items: which came first. That is the least interesting thing about two books.

The moment the list stopped working

I read Dark Money and then, about a year later, The Power Worshippers. Separately, they are two competent books about two different subjects — the financing of the American right, and the rise of religious nationalism. Read within a year of each other, they are obviously the same book approached from opposite ends. One follows the money into the institutions; the other follows the belief into the same institutions and finds the money already there.

My reading list recorded them eleven months apart, with about ninety unrelated titles between them. It had captured the two least important facts about that pair: when I read them, and in what order.

That is when I started keeping the connections instead.

What a connection actually is

Every book in this catalog carries a small set of explicit links to other books on the shelf. There are 1,037 of them across 330 books. They are made by hand, one at a time, and they mean something specific — not "these are both about finance," which is what a tag is for, but something closer to an argument:

• This is the prequel. Chip War explains the supply chain that Apple in China then shows a single company getting captured by.
• This one refutes that one. Two books can be well-reported, well-argued, and mutually exclusive. The link is the useful artifact; the disagreement is the content.
• Same mechanism, different domain. Empire of Pain and Bad Blood are not about the same industry. They are about the same failure of institutional nerve, and reading them together makes the pattern legible in a way neither does alone.
• This is what happened next. Books written five years apart about the same institution, where the later one is unintentionally a report card on the earlier one's predictions.

Tags cannot do this. A tag is a bucket, and buckets are symmetric and shallow — everything in `politics` is equally in `politics`. A connection is directional and specific. It says this book, because of this claim, points at that one.

What changes when you keep them

Three things, and only one of them was expected.

The expected one: recall improves. Not because the summaries help — they help a little — but because retrieving a book by its neighbors is far easier than retrieving it by title. I cannot always name the book about the collapse of Washington Mutual. I can always get to it from the 2008 cluster.

The unexpected one: the connections make the gaps visible. When a book arrives and has nowhere to attach, that is information. It usually means one of two things — either I have wandered into a subject with no foothold on the shelf, which is worth knowing, or the book is thinner than it looked and does not actually engage with anything. Books that connect to nothing are, in my experience, disproportionately books that said nothing.

The third: it kills the completion instinct. A list rewards finishing, which quietly encourages you to finish books that are not worth finishing. A connection graph rewards engagement, and a book you abandoned at page sixty having taken one real idea from it can still be a productive node. The scoreboard changes, and the reading changes with it.

The rules I hold to

No ratings. There is no star rating anywhere in this system and there never will be. Rating a book asks "how good was it," which is a question about the book. The question worth asking is "what did it change," which is a question about me, and it does not compress to a number.

The connection has to be specific. If I cannot say in one sentence why two books are linked, they are not linked. Vague adjacency is what tags are for. The moment "these are sort of related" becomes an acceptable reason, the graph fills with noise and stops meaning anything.

Roughly six links per book. More than that and everything connects to everything, which is the same as nothing connecting to anything. Right now a good number of books on this shelf exceed that, and pruning them back is real outstanding work rather than a finished discipline.

Asymmetry is allowed. If A points at B, B does not have to point back. Sometimes a later book genuinely comments on an earlier one and the earlier one has nothing to say in return. About seventy-five of the pairs here are one-way and that is deliberate. Both pages show the link; only one of them claims it.

What it is not

This is not a system for reading more. I read roughly the same number of books before and after. It is not a productivity method, and the overhead is real — fifteen or twenty minutes per book, which over a few hundred books is a meaningful number of evenings.

It is also not a recommendation engine. Nothing here is scored, ranked, or inferred. If two books are linked it is because a person sat down and decided they were.

What it is, is a way of making a private habit legible — to me first, and then to anyone else who finds it useful. Most of what I know about how power and money actually work, I know from these books, and I would rather show the wiring than the list.

Two places to start: the standout reads, which is the short version, and the connection map, which is the whole thing at once and is best approached as a picture rather than a document.