Stop Writing useEffect Wrong: The Mental Model That Changes Everything

Every React developer has been there. You write a useEffect , it seems to work, and then — chaos. Infinite loops, stale data, components behaving in ways you cannot explain. You copy a Stack Overflow fix, sprinkle in some eslint-disable comments, and move on. But the problem was never the code. It was the mental model. The Wrong Way to Think About useEffect Most developers learn useEffect as: "run this code when something changes." That framing sounds reasonable, but it leads you directly into trouble. When you think of useEffect as a lifecycle hook — something that fires after a render because you told it to — you start treating it like componentDidMount or componentDidUpdate . You reach for it to "sync" things, to "trigger" side effects, to "watch" for changes. That mental model is wrong. And it costs you weeks of debugging. The Right Mental Model: Synchronization Here is the shift that changes everything: useEffect is not about reacting to events. It is about synchronizing your comp