The framework fatigue angle in this thread is real. I spent years maintaining legacy JS and CSS codebases, watching the ecosystem reinvent the same dropdown menu in Backbone, then Angular, then React, then Vue. What I didn't expect is that all that time understanding the actual DOM, specificity rules, and browser quirks would become useful again — when Claude goes sideways on an old codebase, the underlying mental model is what lets you catch it. Vibe-coding isn't replacing that knowledge, it's finally giving it a place to move fast.