Day 01 Session Log
Date: 2026-03-19 Theme: Self-introduction Time: 21:00– (incomplete — stopped early due to time) Completed Phases: 1, 2, 3 (partial)
Phase 1: Warm-up (10 min)
Q1: What did you work on yesterday?
“It is no more task. As usual. That I tackled with Creating UI and UX component for atomine screen.”
✅ Try: “Nothing special, as usual. I tackled creating UI and UX components for the admin screen.”
- “It is no more task” → “Nothing special”
- “That I tackled with Creating” → “I tackled creating”
Q2: What are you focusing on today?
“Maybe debugging, debugging, with date admin screen creating. From common DV to individual tenant DB. I made make make sure whether the resources successfully distributed to individual tenant. Finery, I could distributed three resources with successfully.”
✅ Try: “Today I’m focusing on debugging while working on the admin screen. I’m migrating data from the common DB to individual tenant DBs. I needed to verify whether the resources were successfully distributed to each tenant — and finally, I managed to distribute three resources successfully.”
- “common DV” → “common DB”
- “I made make make sure” → “I needed to verify”
- “Finery” → “Finally”
- “I could distributed” → “I managed to distribute”
Q3: What’s one challenge you’re dealing with right now?
“How to trace inner event. Our product you did our product used Open telemetry and correcting territory library. Currently, some 100 events Hundred hundred events we captured. So successfully. But most critical trace data could not gathered. So I’m I’m struggled with gathering tracing dead into over a broader trace. Or OpenTermetry.”
✅ Try: “My current challenge is tracing inner events. Our product uses OpenTelemetry and its telemetry collection library. We’ve successfully captured around 100 events so far. However, the most critical trace data can’t be gathered. I’m struggling with collecting trace data across a broader distributed trace.”
- “correcting territory library” → “telemetry collection library”
- “could not gathered” → “can’t be gathered”
- “I’m struggled” → “I’m struggling”
- “tracing dead into” → “trace data”
💡 Pronunciation note: “telemetry” → /tɪˈlem.ɪ.tri/ 💡 British tip: stress on 2nd syllable — teh-LEMuh-tree. Don’t say “TELL-uh-meh-tree.”
Phase 2: Grammar Drill (10 min)
Patterns: I am ... / I work on ... / I want to ...
Pattern 1: I am …
-
“I am a back end engineer with four years of experience.” → Good! (minor: “back end” → “backend”)
-
“I am currently based in Japan.” → Good!
-
“I am passionate about this distributed…” (incomplete) → Try: “I am passionate about distributed systems and scalable architecture.”
Pattern 2: I work on …
-
“Welcome back end API is using TypeScript and NodeJS using a library called HONO.” (speech-to-text error) → Try: “I work on backend APIs using TypeScript and Node.js, with a framework called Hono.”
-
“I work on a multi tenant SaaS platform.” → Good! (minor: “multi-tenant” with hyphen)
-
“I work on performance improvements and system reliability.” → Good!
💡 Pronunciation note: “Hono” → /ˈhoʊ.noʊ/ 💡 British tip: treat it like the Japanese pronunciation — “HOH-no”, not “HON-oh”
Pattern 3: I want to …
-
“I want to give a job with over 7k euro as a software developer.” → Try: “I want to land a software engineering role in Europe with a salary of over €7k.”
- “give a job” → “land a role”
- “We” → “I”
-
“I want to Make friend with foreign foreign people.” → Try: “I want to build relationships with colleagues from diverse backgrounds.”
-
“I want to contribute to a product used by engineers across Europe, such as GitHub, AWS, and of of course, Google.” → Good structure! Minor: “of of” → “of”. Note: for European context, try Spotify or Zalando instead of US companies.
-
“I want to deepen my expertise in this distributed system.” → Try: “I want to deepen my expertise in distributed systems.”
- “this” → 不要
- “system” → “systems”
Phase 3: Collocation Drill (partial — 2/5 completed)
Collocation 1: build a feature Scenario: Your new European teammate asks what you’ve been building lately.
“I’m dirt to that. Feature with os. O a u t h” (speech-to-text error) → Try: “I’m currently building a feature for OAuth — handling authentication flows between the common DB and individual tenant DBs.”
Collocation 2: write clean code Scenario: A senior engineer says your PR is hard to follow.
“These blocks of code try to ex expand the New type. Type in. Then there are print there are room for writing more Korean code. I will try it.” → Try: “These blocks of code try to expand the new type definition. I agree there’s room to write cleaner code — I’ll refactor it.”
- “Korean code” → “clean code” (speech-to-text error)
- “I will try it” → “I’ll refactor it”
Collocations 3–5: Not completed (session ended early)
- clarify requirements
- share context
- discuss trade-offs
→ Resume from here in next session.
Phase 4–6: Not completed
Session ended after Phase 3 (partial) due to time.
Score
- I spoke for 90 seconds without stopping: 1
- I used 5 collocations: 0 (only 2/5 completed)
- I asked at least 1 question: 0
- I made at least 1 proposal: 0
- I said the next step clearly: 0
Total: 1/5 — partial session
明日繰り返すフレーズ
“I’m currently building a feature for OAuth, handling authentication flows between tenants.”
Notes for Next Session
- Resume Day 1 from Phase 3, Collocation 3 (clarify requirements)
- Or restart Day 1 as a full 1-hour session
- Key patterns to reinforce: “I managed to”, “can’t be gathered”, “I’m struggling with”