alt Hacker NewsAs a former freelance translator (1986 to 2005, Japanese to English), I have much sympathy for the writer. But I wouldn’t be so confident that AI cannot do professional-level translation.
She writes: “I adapt, I localize, and I find the best way to convey the original message so it makes sense and feels natural. I research terminology. I make sure it’s consistent throughout.”
I’m sure she has other important insights into what enables her to do her job well. The problem is whether or not such insights can be incorporated into an AI-driven translation system, too.
Since early this year, I have been experimenting with a variety of agentic systems for language-related tasks, including dictionary-writing, research on topics in the philosophy of language, essay-writing, and translation. Other than the dictionary [1], I am keeping the results private, so they haven’t been evaluated by others. But my personal assessment is that agentic systems given suitable high-level guidance can be very good at such tasks now.
If I were still freelancing and I had a large translation job to do for a client, here is the outline of the prompt I would give to Claude Fable to get it started:
“Use this private GitHub repository to build a system for translating [genre of text] from [Language1] to [Language2]. The directory samples/ contains examples of the type of document to be translated, high-quality human translations of those documents, and texts in [Language2] that are in writing styles that I believe to be appropriate for this genre of translation. The file guidelines.md contains my general instructions about the needs of my client and my preferences for how you should translate texts along various axes (natural vs. literal, informal vs. formal, preferred dialect in [Language2], consistency vs. variety in terminology translation, etc.). Begin building (1) a knowledge wiki for this project using Karpathy’s LLM-wiki framework and (2) a system inspired by Karpathy’s Autoresearch, AutoResearchClaw, etc. for testing and recursively improving both the functioning of the system and the quality of the translations. For the actual translation, editing, checking, etc., use not only your own ability and the knowledge assembled in (1) but also outsource such tasks to other frontier models through OpenRouter, and use adversarial evaluations among those models and yourself to check and recursively improve the system design, the prompt-writing for other models, and any translations created by the system. My OpenRouter API key is available in this environment. You may spend up to $xx per day in API calls until this project is ready to do real translations; before beginning a real job, give me an estimate for how much the API calls will cost for that job. The initial build-out of this project will take many sessions, so write a prompt called resume-prompt.md that I can point you to at the start of a scheduled Routine to have you work on this. Commit and squash-merge to main at the end of each session. I will be checking in occasionally to view your progress and to ask you to run translation tests, and I will offer guidance then on how to improve the pipeline further and make the translations closer to what my client needs. If you have any questions before you begin, please ask me.”