Finding answers
How to search effectively when you're stuck
⏱ Est. ~5 min
01 · Read
Nobody tells beginners this: no engineer memorizes everything. Not even close.
A senior engineer with 20 years of experience still looks things up every day. They search for syntax they forgot, error messages they haven't seen, techniques they haven't used in a while.
The difference between junior and senior isn't what they memorize — it's how fast they find answers. Searching is a real skill. Let's sharpen it.
Key points
- Read the error message first — copy the exact text
- Search with context: 'express cannot GET /api/users', not 'my server isn't working'
- Include the tech: 'javascript filter array by property'
- Check the date: prefer results from the last 2-3 years
- Official docs first: MDN for JavaScript, the Express docs for Express
02 · Step-through
Stack Overflow is one of the most useful resources for engineers. Here's how to read it effectively, instead of just copy-pasting the first answer.
1. Check the votes
More votes = more community trust. A 500-vote answer has been validated by hundreds of engineers. A 2-vote answer might work but hasn't been widely tested.
2. Read the accepted answer first
The green checkmark means the person who asked confirmed it works. Start there, but don't stop there — sometimes there are newer, better answers below.
3. Read the comments
Comments below an answer often have important corrections, edge cases, or updates. "This doesn't work in version 5 anymore" or "you also need to add X" — these details can save you hours of confusion.
4. Don't just copy-paste
Understand the solution before using it. Adapt it to your code. Blindly pasting code you don't understand is how you fix an old bug and introduce a new one at the same time. Spend 30 seconds understanding why the solution works.
03 · Read
Beyond Stack Overflow, here's the hierarchy of places to find answers, from most reliable to least:
1. Official documentation (MDN, Express docs, Node.js docs) — written by the people who built it 2. Stack Overflow — voted, community-validated answers 3. GitHub Issues — especially for library-specific bugs 4. Blog posts and tutorials — good for walkthroughs, but check the date 5. Claude — great for explanations and personalized help with your specific code
04 · Fill in the blank
When searching for help, copy the exact _____ message into your search.
05 · Quiz
What's the best way to search for a JavaScript error?
- Search 'my code is broken please help'
- Search 'how to code JavaScript'
- Search the exact error message text
- Search 'best JavaScript tutorial'
Other lessons in this chapter
⚠ The full interactive experience needs JavaScript. Please enable it and reload.
※ This is an independent Traditional Chinese teaching project — not an official Anthropic product. Claude™ is a trademark of Anthropic, PBC.