5 exercises — learn when contractions are appropriate in Slack, error messages, code comments, pull requests, and technical documentation.
0 / 5 completed
1 / 5
A developer posts in a team Slack channel: "Hey, I've pushed the fix. It's on the feature branch — you'll need to pull and rebuild your containers." Which statement about the contractions is correct?
Contractions are entirely appropriate in Slack, Microsoft Teams, Discord, and other synchronous team chat tools. These are conversational, informal channels where matching spoken register builds rapport and reduces friction. Using full forms ("I have pushed", "It is on", "you will need") in chat reads as stiff and formal — potentially cold or even passive-aggressive to native English speakers. The "it's ambiguity" argument (Option D) is largely theoretical: context makes the meaning clear. Reserve full forms for formal writing: official documentation, security advisories, compliance reports, and company-wide announcements.
2 / 5
Which error message uses the most appropriate register for a production web application?
"We couldn't load this page" is the best choice: it uses a single, natural contraction ("couldn't") in a calm, helpful, and professional tone. Option A overdoes the reassurance ("Don't worry") and informality — the exclamation mark and "right now" sound flippant for an error state. Option B uses zero contractions, which makes it read as cold and bureaucratic — "Do not proceed" sounds like a warning sign. Option D ("Oops!", "We've lost this page") is too casual and "It doesn't exist anymore!" is slightly accusatory. Best error message practice: calm, actionable, one contraction level — neither overly cheerful nor robotic.
3 / 5
A developer is writing inline code comments for a shared codebase. Which comment style is most appropriate?
Both options A and B are used in professional codebases — the choice depends on team style. However, Option A is increasingly preferred in modern development culture: contractions in code comments create a natural conversational tone between developers and reduce reading friction. Major open-source projects (including parts of Node.js, React, and TypeScript) use contractions in comments. Option B is also valid, particularly in codebases with stricter style guides. Option C is too terse and loses explanatory context. Option D starts with "I've" — code comments should not be first-person ("I did X") as they become misleading after code ownership changes; prefer "Note:", imperatives, or third-person descriptions.
4 / 5
A developer is writing a pull request description for a feature branch targeting the main branch. Which opening is most appropriate?
PR descriptions occupy a middle register: more formal than chat, less formal than official documentation. Option B is ideal: third-person, no contractions, quantified outcome ("40%"), concise. It reads professionally and provides clear information for code reviewers and future `git log` readers. Option A (first-person, contractions, "You'll see") is too chatty for a PR — PRs are semi-permanent records read by many people, including future maintainers. Option C is a fragment-note, acceptable for WIP PRs but not final merges. Option D (no contractions, over-wordy) is unnecessarily formal. Rule: PR descriptions — no contractions, no first-person "I", quantify changes where possible.
5 / 5
Which sentence shows an appropriate difference in contraction use between a technical blog post and API reference documentation?
Option B correctly distinguishes the two registers. Technical blog posts are intentionally conversational — they address the reader directly ("You'll want to", "you're sending") and contractions create an engaging, approachable voice. API reference documentation, by contrast, is formal and imperative: it uses the second-person imperative without the informal "you'll want to" softener and avoids contractions for precision and translatability. API docs are consumed by developers worldwide (many reading in a second language) and often by automated tooling; formal, unambiguous prose serves that audience better. Option C reverses the registers — wrong. Option D reverses the contraction logic — wrong.