World 12: Career Quest

Team etiquette

You will learn: small PRs and kind reviews that teams love.

The problem

Your teammate’s pull request changes 2,000 lines in 40 files. The reviewers sigh. Which PR gets a careful review sooner?

Watch

Tap the changes that belong in a different PR.

0 of 2 found

One PR, one purpose. A small PR is quick to read and easy to approve. Split the rest out.

Try it

Review the code, never the person. Is each review comment kind and useful?

Swipe right for good, left for needs work. Or use the buttons.

1 / 6

"Nice fix! Could we call this saveDraft? It says what it does."

Predict

A reviewer asks you to rename a function. You disagree. What is the best reply?

Check

Good teammates make work easy for others. Sort each habit.

Drag a card into a box. Or tap the card, then tap the box.

You did it!

You can now send small PRs and give kind, useful reviews.

Go deeper (optional)

Not ready yet? Open a draft PR (World 5). Some teams start review comments with a label, like suggestion: or question:. This style is called Conventional Comments. A nit: label tells the author the comment is small and optional. See “Kind, useful code review” in World 5.