Most guides say "just find a good first issue." That's like saying "just find a good stock" — technically true, completely unhelpful.

Here's what actually works:

1. Pick a tool you already use daily. VS Code extensions, CLI tools, frameworks — you already understand the UX, so you'll spot real bugs and improvements.

2. Read the CONTRIBUTING.md before touching code. Every project has different conventions. Some want issues before PRs. Some use specific commit formats. Save yourself a rejected PR.

3. Start with docs, not code. Typo fixes, outdated examples, missing API docs — maintainers love these because nobody else wants to do them. And you'll learn the codebase while fixing them.

4. Reproduce a bug before trying to fix it. If you can write a failing test case, you've already done 70% of the work. Maintainers will take you seriously instantly.

5. Don't ghost your PR. Respond to review comments within 48 hours. The fastest way to get merged is to be easy to work with.

I'm building OpenSourceWeekly to help junior devs navigate this stuff every week — project spotlights, contribution walkthroughs, and real talk about the OSS ecosystem. Free to join.