4 exercises — British irony and understatement, internal banter vs. client-facing tone, safe self-deprecating humour, and hyperbole in written code review comments.
0 / 4 completed
1 / 4
During a demo, a British engineer's feature breaks live in front of the client. He says, deadpan: "Well, that's going swimmingly." Several non-native English colleagues on the call look confused, and one later asks in Slack: "Is the feature actually working now? He said it was going well?" What went wrong?
Irony and understatement as a specific British humour pattern:
"Going swimmingly" said flatly right after a visible failure is a classic British ironic understatement — the humour comes from saying the literal opposite of reality in a completely neutral tone, trusting the listener to catch the mismatch between words and context.
Why this is genuinely hard for non-native or high-context-neutral listeners: • There is no lexical marker of irony — no "just kidding," no exclamation, no obvious joke structure • Tone is flat, not exaggerated, which is exactly what makes it "dry" — but also exactly what makes it hard to detect for someone parsing English literally • Taking it at face value is not a language failure — it is the logical reading of the sentence in isolation
What this means for client-facing English: Understatement humour is genuinely risky in mixed-audience settings, including with clients who may not share the cultural reference. A colleague who is unsure should feel comfortable to just ask directly and immediately: "Sorry, just to confirm the current status — is the feature working now or not?" This is a completely professional, appropriate question, not a sign of weak English.
For the speaker's side: In genuinely high-stakes, mixed-culture, or client-facing moments, it is often safer to follow understatement humour with a literal clarification: "Well, that's going swimmingly [laughs] — but seriously, we've found the bug and I'll have a fix within the hour."
Vocabulary: • irony — saying the opposite of what is literally meant, for effect • understatement — describing something as less significant than it is • deadpan — delivered in a flat, serious tone despite being a joke • self-deprecating — humour that makes fun of oneself
2 / 4
In a Slack channel, an American engineer jokes about a competitor's product being "held together with duct tape and hope." A Japanese client, cc'd on the thread for visibility, reads it and later privately raises a concern that the vendor team seems unprofessional. What is the most useful lesson here?
Audience-shifting: internal banter vs. client-visible communication:
The core issue is not that the joke was inherently offensive — it is that the audience shifted without the tone shifting with it. Competitor banter, casual mockery, and informal jabs are extremely common in internal engineering channels across many cultures, including within many Japanese engineering teams internally. The friction came from that same tone appearing in front of an external client, particularly one from a business culture (common in Japan and many East Asian and some European corporate contexts) where written communication with outside parties defaults to a more formal, reserved register regardless of how informal internal culture might be.
Why this is an easy, high-frequency mistake: Slack, email cc's, and shared threads blur the line between "internal, safe-to-joke" and "external, professional register expected" much more easily than a physical meeting room would. A joke typed for a teammate can be read by someone it was never intended for.
Practical guardrails: • Treat any thread with an external participant, even just cc'd for visibility, as client-facing by default • Keep competitor commentary, especially informal mockery, out of any mixed-audience channel entirely • If in doubt about a channel's audience, default to the more formal register — it is very rarely actively wrong to be a bit more neutral, but a misjudged joke can be hard to undo
Vocabulary: • register — the level of formality of language used in a given context • banter — playful, teasing conversation, often among peers • audience-shifting — a change in who can see or hear a message • cc'd — carbon-copied on an email or thread, included for visibility
3 / 4
A new hire from Germany is worried about "getting humour wrong" in English-speaking meetings and decides never to attempt jokes at work. A mentor advises: "You don't need to force jokes — but there is a category of humour that is almost always safe in professional English." What is the mentor most likely describing?
Self-deprecating humour as the "safest" category:
Across nearly all professional English-speaking contexts and most cultures represented in global tech teams, mild self-deprecating humour — gently poking fun at your own small mistakes, quirks, or learning curve — is the lowest-risk form of workplace humour for a non-native speaker to attempt.
Why it is comparatively safe: • It targets no one else, so there is no risk of embarrassing or offending a colleague • It requires no specialised cultural or idiomatic knowledge to land — the humour is in the situation, not in wordplay or reference • It signals humility and approachability, qualities valued in most professional cultures, rather than superiority or mockery • Even if the joke does not fully "land," the worst outcome is usually a polite smile rather than genuine offence
What to still avoid, even here: • Self-deprecation about something that could undermine real professional credibility ("I have no idea what I'm doing" repeated too often can be taken literally by some audiences) • Using it as a substitute for taking ownership of an actual mistake that needs a real fix, not just a joke
Riskier categories to generally avoid at work, especially early in a new team or client relationship: • Sarcasm directed at a colleague's work or decisions • Idiom-heavy or pun-based wordplay, which non-native listeners may miss entirely • Political, religious, or otherwise controversial topics • Irony/understatement without a clear literal follow-up (see the "going swimmingly" pattern)
Vocabulary: • self-deprecating — humour that gently mocks oneself • land (a joke) — for a joke to succeed and be understood as intended • approachability — being easy and comfortable to talk to • credibility — being seen as trustworthy and competent
4 / 4
In a code review, a US engineer writes: "lol this function name is a war crime, please rename 😂." A colleague from a more formal corporate background finds this comment unprofessional, even though the underlying feedback (rename the function) is reasonable. How should the team think about this?
Hyperbolic humour in written code review comments:
Exaggerated, joking language ("this is a war crime," "this code made me cry," "whoever wrote this owes me a coffee") is common in some engineering cultures, particularly US-influenced startup culture, and is usually intended affectionately rather than literally. But in written, permanent, cross-cultural contexts like a code review comment, several things compound the risk:
• The joke is stored and searchable forever, unlike a spoken aside • It can be read by people outside the original context — new hires, other teams, auditors • Non-native English readers may take hyperbole ("war crime") more literally than intended, or find violent/extreme metaphors for minor issues genuinely jarring regardless of fluency • It mixes the actual technical feedback (the function name is unclear) with an unnecessary emotional flourish that adds no informational value
The core principle: separate substance from style The technical point — "rename this function, the current name doesn't describe what it does" — is completely valid and worth raising clearly. The joke adds personality but also adds risk, and contributes nothing to what the reader actually needs to act on.
Practical guidance for written, permanent, or cross-cultural-visible feedback: • Keep the humour optional and low-stakes (see self-deprecating humour), not aimed at someone else's work • Avoid violent, extreme, or hyperbolic metaphors even in jest — "war crime," "murdered," "disaster" can read very differently out of tone and context • When in doubt, write the plain, professional version — it costs almost nothing and removes the risk entirely
Vocabulary: • hyperbole — deliberate exaggeration for effect • flourish — an extra stylistic touch, not strictly necessary • substance vs. style — the actual content of feedback vs. how it is phrased • permanent record — written communication that persists and can be read later, out of its original context
What does the "Humour in Professional English" exercise practise?
Practice recognising when humour works and when it misfires in cross-cultural professional English — irony, banter across audiences, safe self-deprecation, and written humour risk. 4 exercises.
How many questions are in this exercise?
This exercise has 4 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Cross-Cultural Communication category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Humour in Professional English" part of a larger series?
Yes — it's one exercise in the Cross-Cultural Communication category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Cross-Cultural Communication category page for related exercises, or browse the main Exercises hub for other IT English topics.