Do I need to create an account?
No. All articles are free and available without signing up. Create an account only if you want to use the admin to write or edit content.
The JavaScript questions developers usually fail
Built for developers who want to stop failing the same questions
FAANG · Startups · Product companies
The stuff that actually trips people up
Closures, event loop, this, async, coercion—we focus on the JavaScript questions that come up again and again and that developers often get wrong. No fluff, just the gotchas and how to nail them.
- Questions developers commonly miss
- Syntax-highlighted code snippets
- Short, scannable explanations
The tricky parts, explained
Each article breaks down why the question is hard and how to answer it.
How it works
Three steps to stop failing the same JS questions.
Step 1
Browse
Find questions by topic—the ones people usually get wrong.
Step 2
Read & understand
See the explanation and why the correct answer is correct.
Step 3
Nail it next time
Walk into your interview knowing the gotchas.
Why this blog?
Focused on the JS questions that actually trip developers up.
The tricky topics
Only what interviewers ask and candidates miss.
Code snippets
Highlighted so you can read and copy.
Quick to scan
Get to the point—no long intros.
Clear explanations
Why the answer is what it is.
Latest questions & deep dives
New articles on the JS gotchas developers usually fail.
How to get previous value in useEffect in React
React functional components do not expose previous values directly within useEffect. To compare current and prior values, developers should persist values between renders using useRef. This approach enables precise change detection, efficient side-effect control, and predictable component behavior.
Feb 21, 2026
"These are exactly the kinds of questions I used to bomb—closures, event loop, weird
thisbehavior. Finally a place that just explains the gotchas."
Frequently asked questions
What level are the questions?
From fundamentals (types, closures, this) to intermediate topics (async, DOM, modules)—the ones that trip up mid-level and senior developers in frontend and full-stack interviews.
Can I suggest a topic?
Right now the content is curated by the maintainers. If you have a topic you'd like to see, check the repo or reach out via the project's contact channel.
How are code snippets shown?
Syntax-highlighted for readability. Copy and use them in your own environment if you like.
Ready to stop missing the same JS gotchas?
Head to the blog and pick your first article.
See the questions