#useeffect
Yes using a fetch + setInterval with useEffect (and clear interval cleanup step) is probably the simplest thing that will work reliably.
November 17, 2026 at 10:59 AM
- Ban useEffect
- Ban 99% of explanatory comments (they just lead to workarounds)
- Create API's that hide complexity from agents

Full talk below. (2/2)
November 16, 2026 at 1:15 PM
useEffectをある数より減らそうとしたらuseCallbackが生えてきたからこの辺で止めるか
November 20, 2026 at 4:45 PM
SPFx + React 18: the dispose path still kills most solutions. Missing root.unmount + incomplete useEffect deps = zombie effects and rising memory. 🔧 Fix the ownership boundary before it reaches production. #SPFx #React18 #SharePoint
SPFx React 18 Dispose Failures: Why useEffect Cleanup Never Fires and the Memory Leaks That Follow
SPFx React 18 dispose failures leave useEffect cleanups unrun and create silent memory leaks. Learn why the framework owns the DOM container, how createRoot and onDispose must coordinate, and the exact patterns that stop stale closures and zombie effects after web-part removal or page navigation in modern SharePoint and Teams.
bdking71.wordpress.com
November 16, 2026 at 5:40 PM
We banned useEffect long before AI coding; we enforce it now. And agreed, trying to teach my coding agents nuance is like trying to teach my seven-month-old table manners.
.@poteto's talk at AIE Code is excellent.

If I had to pick one still from that felt genuinely original, it would be this one:

"nuance tends to lead to slop"

To increase quality, design API's and automated checks that remove the nuance from agents' decisions. (1/2)
November 16, 2026 at 10:01 PM
ReactのuseEffectはSwiftのdidSetみたいな?
November 9, 2026 at 11:43 AM
React 19.3's use(browser()) marks a component browser-only during SSR. No more mounted flags, no more hydration mismatches.

🔗 danholloran.me/posts/reacts...

#react #webdev
React's browser() API: Opt Out of SSR Without the Mounted-State Hack
React 19.3 adds use(browser()), a first-class way to mark a component browser-only during SSR, replacing typeof window checks and useEffect mounted flags.
danholloran.me
November 9, 2026 at 5:14 PM
zenn.dev/finatext/articles...
useEffect も switch も禁止する lint で、コーディングエージェントの書き方を縛る
useEffect も switch も禁止する lint で、コーディングエージェントの書き方を縛る
zenn.dev
November 4, 2026 at 9:38 PM
Copying props into local state inside useEffect forces React to render twice: once with stale state, and again after the effect fires. Compute derived values during render instead. Full breakdown in the reply 👇
November 4, 2026 at 5:15 PM
Most React tutorials still teach legacy patterns like chained useEffect hooks for derived state and manual form loading flags. In Course 6 of our Odin Project series, we rebuild with React 19 and TypeScript 👇
November 4, 2026 at 5:15 PM
I think React's dependency arrays are a bit misleading!

I've seen a lot of useMemo used just to keep objects stable for useEffect.

I prefer creating those objects inside the effect when possible. It's less code, and one less thing to keep track of!
November 5, 2026 at 4:43 PM
Most React tutorials still teach legacy useEffect waterfalls and untyped prop drilling. In Part 6 of our Odin Project series, we move to React 19 primitives, strict TypeScript contracts, and predictable state. Walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Using useEffect to sync props into local state or filter arrays causes double renders, UI flicker, and infinite loop bugs. Most of those effects belong in render logic or event handlers. Full walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Using useEffect to copy props into local state or filter arrays causes double renders, stale UI flashes, and infinite render loops. Most state sync effects belong directly in the render pass or event handlers. Full breakdown in the reply 👇
November 4, 2026 at 5:15 PM
Most React bugs come from treating useEffect like a state synchronizer. In Part 6 of our Odin Project course, we replace fragile effect chains with React 19 primitives, derived state, and strict TypeScript contracts. Walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Syncing props into local state with useEffect is one of the fastest ways to introduce double renders, UI flicker, and infinite dependency loops in React. Most of those effects should just be derived state during render. Full walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Most React bugs in production come from abusing useEffect to sync derived state and fighting loose TypeScript types. In Part 6 of our Odin Project series, we rebuild state architecture for React 19 from the ground up. Walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Most React tutorials still teach legacy useEffect chains and brittle prop drilling. In Part 6 of our Odin Project course, we rebuild the mental model around React 19 Actions, strict TypeScript state machines, and zero-boilerplate forms. Breakdown below 👇
November 4, 2026 at 5:15 PM
Syncing props into local state with useEffect is one of the most common React bugs in production. It triggers a stale initial render, a wasted second pass, and subtle UI flicker. Calculate derived state during render instead. Walkthrough in the reply 👇
November 4, 2026 at 5:15 PM
Watch the full Odin Project React lesson on replacing unnecessary useEffect calls: https://youtu.be/aiWk0TOwKLw

More courses and posts at https://codingcat.dev
November 4, 2026 at 5:15 PM
Watch Lesson 6 of our React course on avoiding useEffect traps: https://youtu.be/aiWk0TOwKLw

Explore more Courses and Blog Posts at https://codingcat.dev
November 4, 2026 at 5:27 PM
Watch the full walkthrough on eliminating unnecessary useEffect calls here: https://youtu.be/aiWk0TOwKLw

Explore more Courses, Podcasts, and Blog Posts on https://codingcat.dev
November 4, 2026 at 5:15 PM
Deleting a 25-line useEffect chain and replacing it with a single derived variable during render is still my favorite type of pull request review.
November 4, 2026 at 5:20 PM
Watch the full walkthrough on replacing brittle useEffect chains with derived state, keys, and event handlers: https://youtu.be/aiWk0TOwKLw

More courses and blog posts at: https://codingcat.dev
November 4, 2026 at 5:15 PM
Every React codebase I audit has at least three useEffect hooks just copying props into useState. Deleting them and calculating derived values inline during render is my favorite kind of PR.
November 4, 2026 at 5:20 PM