When you've built a lot, don't just list it

I had a couple of dozen small tools to put on a page, and the obvious move was to list them. Name, one line, repeat. It would have been accurate and complete.

It would also have read as a brag sheet. A long flat list argues from quantity: look how much I made. On a page meant to show judgement, that's the weaker signal — a reader skims it and learns nothing about how I think.

So I dropped the flat list and grouped the tools by what they do. The ones that run the daily rhythm. The ones that take an idea apart. The panel that pressure-tests it. The layer that answers questions from my own material. Each group got a sentence on why it exists.

Same information, but now the structure carries the meaning. You can see the shape of the operation rather than its size, and the count becomes almost incidental. What's left is the impression I actually wanted: narrow tools, each with one job, organised around problems and built on purpose.

Grouping forces a decision a list lets you dodge — what is this for, and what does it belong next to. That decision is the part worth showing. The inventory is only the evidence underneath it.