Mentoring

The projects on this site are the teaching material. Mentoring here is modelled on how Codrlabs builds its own products: what users expect, the constraints the products run under, and the standard of review they get. The review of your pull requests is the lesson.

What you get

A pull request read properly. Not a rubber stamp and not a drive-by “LGTM”. Reviews say why, and point at the specific line.
The reasoning, not just the verdict. When a change is rejected, the tradeoff that killed it gets written down — usually in the repository’s own docs, so the next person finds it.
Production constraints. The technical ones come with the code: accessibility rules, browser behaviour, third-party API limits. The product ones — what users expect, how feedback arrives — are drawn from Codrlabs’ own apps.

What is expected of you

Pick something small first. A first PR that touches one file gets merged. A first PR that redesigns a subsystem usually does not.
Say what you tried. “I expected X, got Y” is worth more than a screenshot of an error.
Take the review as information. Changes get requested on almost every PR, including from maintainers. It is not a grade.
Use AI to understand, not to skip the work. Getting stuck is where the learning happens. See While you’re learning.

What this is not

Not a paid position, and not a promise of one.
Not a bootcamp with a completion certificate.
Not a queue with an SLA — this is unpaid work on both sides, so reviews come when they come.

Where to start

Contributing has the mechanics. The active project is Vizably.