Learn to say popular code review tool names correctly.
0 / 5 completed
1 / 5
How is Gerrit (web-based code review tool for Git) correctly pronounced?
Gerrit is pronounced 'GEHR-it' — hard G, like the name 'Gerald' shortened, stress on GEHR. Don't say 'juh-RIT' with a soft J sound. In a technical interview: "Gerrit required every single commit to pass review before it could merge, which kept our history unusually clean."
2 / 5
How is Reviewable (code review tool for GitHub pull requests) correctly pronounced?
Reviewable is pronounced 'rih-VYOO-uh-bul' — exactly like the everyday adjective meaning 'able to be reviewed'. Stress on VYOO. Don't say 'REE-vyoo-uh-bul' with front stress. In a technical interview: "Reviewable tracked exactly which lines each reviewer had already seen, even across multiple rounds of pushes."
3 / 5
How is Graphite (stacked pull request and code review tool) correctly pronounced?
Graphite is pronounced 'GRAF-yt' — exactly like the pencil-lead mineral, long I at the end. Stress on GRAF. Don't say 'GRAF-it' with a short I. In a technical interview: "Graphite's stacked diffs let us split one large feature into small, independently reviewable pull requests."
4 / 5
How is CodeStream (in-IDE code discussion and review tool) correctly pronounced?
CodeStream is pronounced 'KOHD-streem' — 'code' (long O) plus 'stream' (long E). Stress on KOHD. Don't say 'KOD-streem' with a short O. In a technical interview: "CodeStream let reviewers leave comments directly in the editor, right next to the line they were discussing."
5 / 5
How is Danger JS (automated code review rules engine) correctly pronounced?
Danger JS is pronounced 'DAYN-jer jay-es' — exactly like the everyday word 'danger' plus J-S spelled out. Stress on DAYN. Don't say 'DAN-ger' with a short A. In a technical interview: "Danger JS automatically flagged any pull request that was missing a changelog entry, before a human reviewer even looked at it."