When is it not appropriate to create a kata translation? #3452
-
|
There are quite many katas out there that are not translated into TypeScript yet, and I would like more of them translated into TypeScript. I know that language, and I can translate katas (that I can solve) into it. The question might seem a bit stupid, but: are there such conditions, except for very bad katas or those already having pending translations (for the language I want to translate into), or those specific to just one language, that make it not a good idea to suggest a translation? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
It's usually not a good idea to translate a kata when the core idea doesn't really transfer to the target language. Typical examples are katas that exist to teach quirks of a specific type system, manual big-integer arithmetic in languages that already have native bigints, or other language-specific mechanics where the learning goal disappears in TypeScript. In practice, the bigger issue isn't creating translations but getting them approved. The review process is slow, so choosing the right kata matters. Translating a well-written kata greatly increases the chances of approval. Newer katas tend to be cleaner, and it helps to read the Discourse first to spot known issues or ambiguities. The translation should also follow current TS conventions rather than copying older patterns. Old katas can still be translated, but they're often inconsistent across languages, and it's not always clear which version should be treated as the reference. In those cases, it's better to either not translate until specs get unified across languages, or, eventually, follow the intended problem rather than blindly mirroring another language. If the source language has a known bug or questionable behavior, it's better to report that and either wait or make sure the TS translation isn't affected by the same mistake. If you're unsure, the |
Beta Was this translation helpful? Give feedback.
It's usually not a good idea to translate a kata when the core idea doesn't really transfer to the target language. Typical examples are katas that exist to teach quirks of a specific type system, manual big-integer arithmetic in languages that already have native bigints, or other language-specific mechanics where the learning goal disappears in TypeScript.
In practice, the bigger issue isn't creating translations but getting them approved. The review process is slow, so choosing the right kata matters. Translating a well-written kata greatly increases the chances of approval. Newer katas tend to be cleaner, and it helps to read the Discourse first to spot known issues or ambiguities. Th…