Code RoomRedux to Zustand behavior
MediumPrep Room Coding #4240

Redux to Zustand behavior

Vibe & agenticCode quality & reviewMid–Senior~18 min

You're migrating a React app's global state from Redux to a lighter store like Zustand, letting an AI agent rewrite the slices and connect components. The UI looks fine in dev. What subtle behavioral differences between the two should you specifically verify, and where will the agent most likely introduce a regression?

Implement
count_rerenders(subscriptions: list[str], updates: list[str]) → list[int]
Examples
in[["Cart:items|total","Header:userName","Debug:*"],["items=2","items=2","userName=Ada"]]out[1,1,2]
in[["Whole:*"],[]]out[0]
in[[],["a=1"]]out[]
What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.

0:00 of about 18 min

Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.