[Proposal] Korean Translation of Mojo GPU Puzzles

GPU Programming
, ,
1

I’m really into puzzles.modular.com and have made a few contributions to the repo. I pitched this idea to @Ehsan and he encouraged me to share it with the community, so here it is!

I’m planning to translate the puzzles into Korean and wanted to share my plan.

Why Korean translation?

Mojo/MAX is still under the radar in Korea, but there’s growing government-backed AI investment here. When people start discovering what MAX can do, they’ll look for resources. And honestly, even developers who can read English (like me) often understand things faster in their native language.

On a personal note, this is also about my own growth. Going through each puzzle carefully and translating it is one of the best ways to really learn the material and build deeper expertise.

My plan

Quality & Maintenance

  • Terminology guide for consistency
  • GitHub Issues for community feedback
  • Sync with release tags
  • Blog series alongside to drive traffic back to the official puzzles

I translated MIT’s Missing Semester into Korean before, but didn’t keep it updated - still bugs me. This time I want to stay in sync with upstream changes properly.

Timeline

  • Start with Part I to nail down the workflow
  • Cover all parts currently available
  • 1-2 days per puzzle, approximately 2 months to finish

If this goes well, I’d love to tackle llm.modular.com next.

Repository

My initial thought is to use a separate repository to keep the Korean version cleanly separated from the original. But if anyone has a better approach, I’d love to hear it. I want to gather everyone’s input and go with whatever direction makes the most sense.

Updates

I’ll post progress updates in this thread. Feedback, suggestions, or questions are always welcome.

4 Likes
2

You will undoubtedly learn more as you translate the ideas. If/when fellow Koreans turn to you for clarification, that will also help sharpen your understanding. Whenever you do something a second or third time, you start to see things you didn’t the first time around. Sounds like a wonderful plan.

I like that you’ve scoped it specifically to GPU puzzles. There’s a lot of content at Modular and even taking on a single part of mojo or MAX could be overwhelming.

2 Likes
3

Thanks! I feel lucky that puzzles happen to be both what I’m most interested in and a scope I can actually finish. It is way better than being too ambitious and never crossing the finish line. :smile:

1 Like
4

That’s a great proposal :heart_eyes: ! Looking forward to it. Please send PRs when ready.

2 Likes
5

Thanks :heart_eyes: ! Just to clarify @Ehsan:

  1. Should I send a PR to add a link to the Korean repo in the README once it’s ready?
  2. Or would you prefer the translation to live inside the main repo itself (like a book/ko/ folder)?

Either works for me — just want to make sure I’m heading in the right direction. :smile:

6

Update: Early Progress & Workflow

Quick update on how things are going

Translation approach

Using an LLM for the first pass. Then I read the original to understand it properly, and go through the translated version sentence by sentence. AI gets a lot right, but there’s always mistranslations or meaning that’s slightly off, those I fix by myself.

Why LLM? Honestly, the puzzles are massive and I didn’t trust myself to stay consistent from start to finish. So, I feed it previous translations as reference and keep a glossary file to make sure terminology doesn’t drift.

Tracking sync status

Simple approach. I track main commit vs translated main commit. If they’re different, then time to translate.

Progress

Done puzzles 1–8. These were familiar from last year so they went fast.

1 Like
7

Would be great to have it alongside the English version in the main repo :folded_hands:

1 Like