← 英語セッション一覧
EN Day 01b 4/5

Self-introduction (Day 1 continuation — Phase 3 resumption through Phase 6)

2026-03-20

Day 01 Session Log (continued)

Date: 2026-03-20 Theme: Self-introduction (Day 1 continuation — Phase 3 resumption through Phase 6) Time: Evening session

Phase 3: Collocation Drill (resumed from 3/5)

Collocation 3: clarify requirements Scenario: Spec is vague — what do you say to your tech lead?

“That task That spec is vague. Could you clarify requirements more?” → Try: “This spec is a bit vague. Could you clarify the requirements?”

Collocation 4: share context Scenario: A new teammate just joined mid-sprint.

“I thought you joined our team in the mid sprint? Let’s let me share our product’s context. To you.” → Try: “You just joined us mid-sprint, right? Let me share some context about our product so you can get up to speed quickly.”

💡 Phrase: “get up to speed” — standard expression for onboarding new teammates

Collocation 5: discuss trade-offs Scenario: Team is choosing between two database architectures.

“Your database architecture would be would have has to fight one. It’s differentiating concern separating concerning concerns in terms of separating concerns to database architectures, would be nice, but the contrast in contrast is that makes architecture more complicated. So I want to we we should figure out some trade offs” → Try: “We have two database architecture options to consider. Separating concerns across databases would be clean, but the trade-off is added complexity. We should discuss the trade-offs before making a decision.”

Phase 4: Discussion Drill (15 min)

Claude plays Alex, senior engineer in London.

Context:

“I implemented add and delete features for the admin screen.”

Issue:

“The problem is that deleting a custom node breaks existing tenants using it.”

Evidence:

“For instance, if we delete a distributed customer node, the tenants currently using it will have their customer nodes broken.”

Alex: “What’s the trade-off there?”

Proposal:

“My proposal is to replace hard delete with an ‘unpublished’ status.”

Alex: “What’s the trade-off there?”

Trade-off:

“The trade-off is that we’d need to add a new status column and run a migration file.”

Alex: “What’s the next step?”

Next step:

“I’ll consult with our lead engineer to check if the migration trade-off is acceptable.”

Alex: “Sounds good — loop me in after you’ve checked with them.”

Coach feedback:

Phase 5: Pronunciation-guided Speaking (10 min)

Topic: Describe the OAuth feature you’re building.

What user said (typed):

“First things first. I implemented OAuth 2.0 to my AI agent features. If we add it, it provides AI agents the ability to reach outside of our product. We require authentication to get some data from Gmail or Google Drive. We have to authenticate and authorize acceptable scopes to our product. It was built because the product wants to integrate with Microsoft — to analyze what contents are included in the mail and publish to Teams chat. The challenge is not the coding but the incremental flow in terms of Microsoft. There is a concept called admin consent flow which requires individual tenants to allow and have some controls.”

Cleaned-up version:

“First things first — I implemented OAuth 2.0 for our AI agent features. It allows our AI agents to reach outside our product. For example, we need to authenticate and authorize acceptable scopes to access Gmail or Google Drive. I built this because the product team wants to integrate with Microsoft — specifically to analyze email contents and publish them to Teams chat. The challenge isn’t the coding itself, but the incremental flow in Microsoft’s system. There’s a concept called ‘admin consent flow,’ which requires individual tenants to explicitly grant permission.”

Pronunciation notes:

"authenticate" → /ɔːˈθen.tɪ.keɪt/
💡 British tip: stress on 2nd syllable — AUTH-en-ti-KATE. 4 syllables.

"authorize" → /ˈɔː.θər.aɪz/
💡 British tip: British spelling is "authorise" — same pronunciation.

"OAuth" → /ˈəʊ.ɔːθ/
💡 British tip: "OH-auth" — the O is a long vowel.

Phase 6: 5-sentence Writing + Review

Scenario: Slack message to European team explaining OAuth feature and admin consent challenge.

User’s sentences:

  1. “It integrates with Google, Microsoft, Box, So our products will be able to reach their ops.”
  2. “In the security prospect for security perspective, It applies authorization flow with PIC code.”
  3. “It prevents Evil users from exploiting the security code.”
  4. “For the admin consent challenge, Microsoft makes users this button.”
  5. “Because that consent pro only requires Only On device. Developers.”

Corrected versions:

  1. “It integrates with Google, Microsoft, and Box, so our product can access their APIs.”
  2. “From a security perspective, it applies an authorization flow with PKCE.”
  3. “It prevents malicious users from exploiting the authorization code.”
  4. “For admin consent, Microsoft requires tenant admins to click an approval button.”
  5. “This is because admin consent can only be granted by tenant administrators, not individual users.”

💡 Pronunciation note: “PKCE” → /ˈpɪk.si/ 💡 British tip: say “pixie” — widely used among engineers on both sides of the Atlantic.

Score

Total: 4/5

明日繰り返すフレーズ

“It prevents malicious users from exploiting the authorization code.”

Say this aloud 3 times just before you sleep — it helps lock it in.