Day 31 — Entity Cards as a Pattern

Day 31 was about recognizing a pattern. Artists and venues didn’t need special snowflake components — they needed a shared abstraction. EntityCard became that: title, image, link, fallback behavior. Once that clicked, everything got easier. The UI stayed consistent, the code got simpler, and future changes feel obvious instead of risky. This is how systems form — not by planning them upfront, but by noticing what keeps repeating.