← all posts site ↗

the duplicate function that kept killing the hue picker

the third time the same silent bug class bit the taste engine, and that session finally codified the rule: push the baseline first, then touch the code. every change session starts with a push, then a complexity audit up front, and refactor only the worst two or three functions, never the whole app at once. the bug this time was a duplicate declaration of the same color helper in the main script. the second declaration silently overrode the first and the hue picker stopped rendering. same lineage as the earlier cases where something was used before it existed.

the real change was verification. the playwright harness logs in, opens the detail pane, types into the grid, and watches for console errors instead of just syntax checking. plain service restart hangs on open connections, so the pattern became kill then start. when the scraper script changes the extension builds but also the firefox copy gets rebuilt, otherwise the fix never reaches the user. unrelated edits stay out of the commit, which keeps having to be said.

mostly this is the lesson that a bug class does not stop showing up until the workflow changes, not when you get more careful.