A UX decision I got wrong on the first try
The add-to-playlist action matched its sibling gesture on the same card - and fought the rest of the app. Picking the wrong reference point for "consistent."
Notes on the software, games, and music coming out of Imperfect Systems.
RSS feedThe add-to-playlist action matched its sibling gesture on the same card - and fought the rest of the app. Picking the wrong reference point for "consistent."
A dead symlink target, a fix already queued by automation, and docs describing components that don't exist - three sources of truth, same lesson each time.
"We have backups" and "we have backups that work" are different claims. A file-level restore, a query against the restored data, and a stray copy cleaned up along the way.
axe-core over the existing component-test harness, scoped to actual WCAG rules - and an honest accounting of what a jsdom gate structurally cannot catch.
Uncommenting three Rails SSL flags took ten minutes. Reading the framework source and testing two plausible but wrong review findings took the rest of the day.
A perf batch with an easy half (prerender, PNG optimization) and a silent failure: an SVG favicon whose external image reference browsers drop without a word.
A failed artist fetch never counted as checked, so one bad artist re-selected itself forever - and the fix tripped a second guard only a multi-round test could catch.
Adding astro check and Prettier before every deploy, a type error the sibling site had already solved, and a manual build trigger with no concept of a dry run.
Three audit items that each turned into something: a half-fixed claim, a quietly dead password reset, and a staging email that would have linked to production.
Six known drift items on the list, two more found by actually running the documented commands, and a rename fix that project memory made narrower than find-replace.
Page 7 of 14