The first thing the garment image shows is not a slogan. It is a rectangle: a black-and-white speckled field, a dark binding strip down the left edge, and a white ruled label headed COMPOSITION. Inside that label, where a student would write a name and subject, there is an outlined ghost and a pumpkin. The notebook cover is printed on the shirt, not attached to it. That distinction matters more than it first appears, because the design is not asking you to read a sentence. It is asking you to recognize a form. Most novelty shirts in the teacher-Halloween genre…

The first thing you notice is how little there is to notice. On the dark shirt, centered, sits a very small lowercase meh. — four letters and a period, set in a modest sans-serif, occupying a patch of fabric roughly the size of a thumbprint. No animal. No flag. No slogan in a distressed typewriter font. The garment preview shows the word floating in the middle of the chest, and the period is doing more work than the letters are. That period is the whole argument. Without it, meh is a noise — a shrug rendered in text, the verbal…

The first thing the shirt does is borrow a grammar you already obey. NOT FRIENDLY sits in heavy warning-sign lettering, the kind that usually precedes a hazard. Beneath or beside it, a yellow caution triangle frames a hand with a diagonal slash through it. DO NOT TOUCH finishes the sentence in the same blunt register. The palette is industrial: yellow, black, the visual vocabulary of a wet floor or a high-voltage cabinet. Nothing about the composition is cute. That is the point. We spend most of our working lives inside systems that use exactly this language to prevent harm. A…

Editorial note: This publication and Quirky Cotton Collective share an owner. This is not an independent review. The shirt does not spell the sentence. That is the first thing to notice, and it is the thing most people miss. Across the chest, four tiles in the visual grammar of the periodic table: 53 I, 74 W, 22 Ti, 16 S. Read the symbols in sequence and you get I W Ti S. Read the atomic numbers and you get 53, 74, 22, 16. Neither sequence is the phrase printed above the tiles. The phrase is I WEAR THIS SHIRT PERIODICALLY,…

Editorial note: This publication and Quirky Cotton Collective share an owner. The artwork is a closed loop of text and soil. LET’S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW runs around the perimeter, and inside that ring sit four smiling root vegetables — a carrot, a radish, a beet, and an onion — each drawn with its roots visible in the dirt. The roots are not decorative. They are the part of the drawing that does the argument. LET'S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW ┌─────────────────────────────────────────────────────┐ │ │ │ \o/ \o/ \o/ \o/ │ │…

Editorial note: This publication and Quirky Cotton Collective share an owner. The banner is the first thing you see, and it is almost aggressively plain. A white rounded rectangle, the kind of shape a phone throws up when a camera catches something it thinks you should know about. A small bell icon sits at the left edge. The text reads, in ordinary sentence case: There is motion at your front door. Below the banner, inside a circular frame, a green-tinted view shows an orange tabby pressed so close to the lens that its face fills the whole aperture — wide…

Every organization has two classification schemes. One is written down somewhere — a taxonomy, a records schedule, a governance policy. The other is the folder tree. The folder tree is the one people actually search against, and it was never designed. It accreted. This article is about reading that accreted structure as evidence. Not as a standard-compliant artifact, not as a records schedule, and not as something to migrate. The folder tree is a concept scheme in the descriptive sense: it has labels, near-synonyms, code-like segments, and links (or missing links) to the formal schemes it is supposed to serve.…

Editorial note: This publication and Quirky Cotton Collective share an owner, so this is not an independent review. The garment preview shows one word and one mark: meh. — large, bold, lowercase, white, set on a dark shirt. No animal illustration. No secondary slogan. No decorative frame. The period is the part I keep returning to. Without it, the shirt reads as a mood. With it, the shirt reads as a verdict. That distinction matters more than it first appears, and it is the argument of this column: the period converts a feeling into a boundary. A mood is something…

“Search is broken” is almost never a search problem. It is an indexing problem that search is faithfully reporting. The crawl log — the record of what the indexer attempted to read, parse, and admit into the index — has an error column, and that column is the closest thing an enterprise knowledge system has to a truthful account of why users cannot find things. The error column is not a list of search bugs. It is a list of structural information failures that were present before anyone typed a query. This article is about reading that column diagnostically: what…

Most enterprise libraries do not fail because someone deleted the wrong field. They fail because nobody ever asked which fields were doing work. A SharePoint document library accumulates columns the way a shared drive accumulates folders: one request at a time, each reasonable in isolation, none reviewed as a set. Ten years later the form has sixty fields, the search index has forty of them, and the retention schedule references three. This is a diagnostic problem before it is a design problem. Before you remove a column, you need evidence about which columns are populated, which are queried, and which…

You know the document exists. You watched the program manager upload it in March. You type the project code into SharePoint search and get nothing — then browse to the library, scroll, and find it sitting there as Final_v3_PROJ-7720.docx. The search didn’t fail. The naming convention did, and it failed quietly, one file at a time, for three years. We call this condition governance-by-naming: the structural substitution of a filename convention for an actual metadata layer. It is one of the most common failure modes we see in enterprise and public-sector knowledge systems, and one of the least diagnosed, because…

An enterprise knowledge management system is any platform an organization uses to store, describe, and retrieve its working knowledge: SharePoint sites, Teams channels, OneDrive folders, Confluence spaces, OpenText repositories, an Elasticsearch or Solr index sitting in front of all of them, or a public-sector data portal built on CKAN or Socrata. Failure in these systems rarely looks like an outage. It looks like a person who knows a document exists, has every right to read it, and still cannot find it in the time they are willing to spend. I review these systems for a living, and I have stopped…