Express Mode

Express Mode targets selected text containing non-English characters (e.g., Chinese). Rather than simple dictionary translation, it provides three progressively better English expression levels: Basic & Clear, More Natural, and Idiomatic. Each level is annotated with tone, formality, and appropriate use cases.

Trigger Condition

The selected text contains non-English characters. Press ⌘⇧D, and DevGlish automatically enters Express Mode.

Examples:
• "This plan isn't reliable" (Chinese input) → Three-tier English expressions
• "I can't fit it into my schedule this week" (Chinese input) → Three-tier English expressions
• "Need to refactor this code" (mixed Chinese-English) → Three-tier English expressions

Three-Tier English Expression Framework

Tier 1: Basic - Green Label

Direct translation; grammatically correct and easy to understand, but not very natural. Good for playing it safe and ensuring you’re understood.

Example 1:

Input: "This plan isn't reliable"
Basic: This solution is not reliable.

Analysis:
Tone: Neutral, direct
Formality: Medium-high
Risk: Somewhat stiff, may make you seem unsure

Example 2:

Input: "I can't fit it into my schedule this week"
Basic: I don't have availability this week.

Analysis:
Tone: Formal, written
Formality: High
Risk: Too formal, not suitable for casual team culture

Tier 2: Natural - Yellow Label

More natural expressions using common, authentic phrasing. Suitable for everyday work communication.

Example 1 (continued):

Input: "This plan isn't reliable"
Natural: I'm not sure this approach will work.

Analysis:
Tone: Cautious, open to discussion
Formality: Medium
Improvement: Uses "I'm not sure" instead of the blunt "not reliable," inviting discussion

Example 2 (continued):

Input: "I can't fit it into my schedule this week"
Natural: I'm pretty swamped this week.

Analysis:
Tone: Friendly, candid
Formality: Medium-low
Improvement: "swamped" is common team slang for being overwhelmed

Tier 3: Idiomatic - Blue Label

How a native English speaker would say it. Considers context, culture, and implied professional relationships.

Example 1 (continued):

Input: "This plan isn't reliable"
Idiomatic: I have some concerns about this approach. Have you considered [alternative]?

Analysis:
Tone: Constructive, collaborative
Formality: Medium
Advantage: Expresses doubt while showing willingness to collaborate, fitting code review culture

Example 2 (continued):

Input: "I can't fit it into my schedule this week"
Idiomatic: I'm at capacity this week, but I can [help next week / pair on this later].

Analysis:
Tone: Professional, setting boundaries yet reliable
Formality: Medium-high
Advantage: Clearly states your limitation while offering an alternative, demonstrating professionalism

Use Cases

Scenario 1: Code Review Comments

You want to leave a comment on a GitHub PR.
Your thought: "The error handling logic is too rudimentary"

Basic: The error handling logic is too simple.
Natural: The error handling could be more robust here.
Idiomatic: We might want to consider handling these edge cases more explicitly.
           What do you think about [specific scenario]?

Choice: Depends on team culture
• Strict team → Natural tier
• Discussion-oriented team → Idiomatic tier

Scenario 2: Slack Team Communication

You want to say before a sprint review: "I haven't finished this feature yet"

Basic: I haven't finished this feature yet.
Natural: I'm still working on this feature. Should have it done by [time].
Idiomatic: I'm on track to finish this by EOD, but I'll let you know if I hit any blockers.

Choice: On Slack, the idiomatic tier works best -- it shows you have a clear
time estimate and transparent communication

Scenario 3: Email or 1:1 Meeting

You want to tell your manager in English: "I want to take on this project"

Basic: I want to take on this project.
Natural: I'd be interested in working on this project.
Idiomatic: I'd love to take the lead on this project. I think it aligns well
           with my growth goals, and I'm confident I can deliver results.

Choice: Email → Idiomatic tier, showing career ambition and confidence

Scenario 4: Incident Response

A system outage occurs, and you need to report: "The situation is pretty bad"

Basic: The situation is bad.
Natural: We're experiencing a critical issue right now.
Idiomatic: We have a P1 incident affecting [system]. Engineering is
           investigating. I'll keep you updated every 15 minutes.

Choice: Idiomatic tier is essential -- professional, clear, fact-driven

Design Philosophy

:::tip Benefits of the Three-Tier Framework

1. Progressive learning: From “safe but stiff” to “idiomatic and natural,” gradually building English expression flexibility
2. Scenario awareness: The same idea is expressed entirely differently in code reviews, Slack, and emails
3. Cultural adaptation: Helps you understand “what’s the right way to speak” in Western development teams
4. Psychological safety: The Basic tier translation is always there, so you can boldly try more natural expressions :::

Pro Feature

:::caution Pro Limitation Express Mode is only available with a DevLingo Pro subscription. The Free plan includes the other 4 modes. :::

Express Mode is DevLingo’s differentiating feature, helping non-native English speakers not only “say it right” but “say it naturally.” Express your ideas with confidence in international teams.