TBH one of my bigger fears around AI is that it will lock in the median of today’s practices and quietly turn it into tomorrow’s “best practice.” When a model is trained on the whole internet, it doesn’t learn the right way. It learns what’s most common, and the most common code and architecture patterns out there are…mixed at best. The model’s incentives reward likely and familiar, not better or novel, so it becomes a kind of gravity well that pulls teams back toward whatever already dominates the training mix. And then there’s the feedback loop: AI-generated output gets shipped, copied into docs, pasted into blogs, merged into repos, and fed back into the next generation of training. That doesn’t just preserve the mess, it can compound it, creating a self-reinforcing layer of confidently explained mediocrity. The scariest part is that real progress often starts out-of-distribution. New paradigms, emerging best practices, and the hard-won lessons from great teams are underrepresented, so they get drowned out by the volume of the average or even the sub-par. If AI becomes the default author/reviewer/teacher, we might get faster at producing more of what we already do and slower at evolving what “good” looks like. If we’re not careful, we’ll end up with an industry that can autocomplete the past perfectly while struggling to invent the future.

I heard some folks missed my recent Web Component Engineering course sale, so I’m running one more: ✅ 25% off w/ code GOODTIDINGS25 ✅ Through the 1st week of 2026 Web Components, DOM APIs, modern CSS, a11y, forms, design systems, tools, and more! bluespire.com/course/web-com…

I applaud Remix 3 for swinging the spotlight back to the Web Platform. If last week’s reveal showed anything, it’s how defaults, docs, and incentives can fence off core browser knowledge. Framework-first norms didn’t mean to, but they *did* turn basics into trivia. So, the surprise around things like CustomEvent or listening on a parent to handle child interactions tells a story: the community has been standing next to power it wasn't taught to use. Facts: * CustomEvent has been baseline across modern browsers since 2015 (~10 years). * Event delegation (via bubbling/capturing) is part of the DOM event model standardized in 2000 and used since the late ’90s (~25+ years). This isn’t an anti-framework post; it’s anti-amnesia. Reach for what ships in the box: addEventListener + delegation, CustomEvent, FormData, URLSearchParams,