Five stacks, one instinct: what switching frameworks actually teaches you

Most of my work lives in React and Next.js, but a good amount of it hasn't — WordPress builds, Shopify and Magento storefronts, the occasional Angular codebase inherited from another team. Agency work has a way of putting a different stack in front of you every few months whether you asked for it or not.

The instinct that carries over isn't syntax. It's the same handful of questions: where does this data actually live, what happens when the network is slow, and what's the smallest component that does one job well. Those questions look identical in a React hook, a WordPress template, and a Liquid file.

What does change is the cost of getting something wrong. A sloppy state update in a React SPA fails loudly, in the console, immediately. A sloppy template in WordPress or Magento fails quietly, months later, when a plugin update touches a file you forgot existed. Working across both kinds of systems makes you more careful in both.

I don't think framework loyalty is a particularly useful trait past a certain point. Picking the right tool for a client's actual constraints — their team, their host, their timeline — has mattered more to the outcome than which one I'd have picked for myself.