
Hot reload not working in Vite or Next: three common causes — the bundler can't see files (WSL, Docker), import letter case, and state resets. How to fix each.
A state machine in plain words: why three flags — isLoading, isError and data — give you eight states instead of four, and how a single status fixes it.
useState vs useRef in React: which one triggers a re-render, when you see the new value, and where to keep a timer id. A simple rule for which to pick.

Why your website video doesn't autoplay: sound, playsinline on iPhone, and React dropping the muted attribute. How to check each cause and fix it.

What a closure is in plain words: a function that remembers the variables from where it was born. And why it makes a React timer show 1 forever.

What is short-circuit evaluation (&& and ||), in plain words: why the second half may never run, and where a lone zero in your React UI comes from.

What is a linked list, in plain words: a chain where each item only knows the next one. Where it lives in React hooks and in your Git history.

How to detect a click outside and close a menu or modal: a ready React hook, a no-code popover, and three bugs — from text selection to a stuck toggle button.

A tuple, explained simply: a fixed-length array where each position has its own meaning and type. Why useState is a tuple and where TypeScript won't protect you.

Input loses focus after every letter? Three causes in React and plain JS: a component inside a component, a shifting key, and innerHTML — and how to fix them.

Why localStorage loses data after a reload: your code overwrites it, a different port, an object saved without JSON.stringify, the browser wiping it. Fixes.

Timer ticking faster and faster, refusing to stop, or stuck at 1? Three real causes of a broken setInterval — how to check each one and how to fix it.

A click or key press fires twice, or even more? Three real causes of an event firing twice in JavaScript and React — and how to check and fix each one.

What a pure function is in programming, in plain words: same input, same output, no side effects. Why it matters in React and in tests, with examples.

An infinite loop: the tab froze, the fan is screaming, the server gets thousands of requests. Three real causes — from React useEffect to while — how to check and fix.

Client-side routing changes the page address without asking the server. How it works under the hood, and the four things the browser no longer does for you.

How to store filters, sort order and the active tab in the page address: six steps with URLSearchParams, pushState vs. replaceState, and ready-to-use code.

Hydration is the moment JavaScript wires itself into the HTML the server already sent. Here's where the dead window and mismatch errors come from.

You called setState and the screen didn't re-render. Three real causes: mutating an array, state as a snapshot, and shallow copies — plus how to fix each.

Next.js or Vite: the difference isn't React, it's whether you need a server. Compared on SEO, link previews, hosting and learning curve — with a verdict.

Next.js vs React — which should a beginner pick? They're not rivals: Next.js is built on React. A comparison table and a clear verdict on where to start.

Not everyone needs React. For a landing page or blog, plain HTML is lighter and faster; React pays off when the interface is live. We compare and call it straight.

React is a library where you describe how the screen should look, and it redraws it for you. In plain words: components, state, and the one trick that changes everything.