Part 11 of 13 · 1 min read
Quick notes
- A good first contribution is small, tested and linked to an issue: reproduce the problem, say you are working on it, make one change with a test that fails before and passes after, and respond to review quickly.
- Review cost is the currency. A minimal fix is easy to read; reformatting, renames and leftover debug prints bury it. Renames and reformatting are separate pull requests.
- Show that your test catches the bug: it must fail on main and pass on the branch. A correct fix with no test is unproven.
- Pick a project by evidence of use and activity, and know its licence, sign-off rules and policy on AI-assisted contributions before you open the pull request.
- Be explicit about AI assistance, understand every line you submit, and in an interview state precisely what you changed and learned without claiming ownership of the project.