유대선
프로젝트로
·업데이트·1

Code walkthrough goes bilingual — and a sweep for the Korean-only stragglers

The owner's standing rule is that every Korean field needs an English twin. The code walkthrough was Korean-only, so generated an English version 1:1 for all 202 cards and rendered both. A field-by-field sweep then surfaced the remaining Korean-only content to fix next.

The owner's principle is simple and firm: anywhere there's Korean, there has to be English too. The line-by-line code walkthrough had shipped Korean-only, so it broke the rule. Generated codeExplainEn one-to-one for all 202 concept and AI cards — the same bullets in technical English — and the "코드 한 줄씩 설명 (EN/KO)" section now shows English on top with Korean beneath each bullet.

Then a field-by-field sweep to honor the rule fully, because new fields tend to ship Korean-only by default. The concept and AI decks are now fully bilingual (subtitle, raw English, explanation, failure modes, self-attack probes and their model answers, and now the code walkthrough all have both languages). What's still Korean-only and queued to fix: the Move Decks' trade-offs and applies-to notes, the system-design and LLD step-level tradeoff/solve notes, and the behavioral STAR breakdowns (which currently pair a Korean situation/task/action/result with a single English spoken version).

The takeaway: in a bilingual tool the audit is never one-and-done — every time content is generated, check whether it landed in both languages, because the default is one.