Flutterby™! : AI killed translation

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

AI killed translation

2025-08-21 22:08:16.788055+02 by Dan Lyke 0 comments

Blood in the Machine: AI Killed My Job: Translators

Machine translation hasn't even improved. There was no big OpenAI moment. I'm starting to suspect it's an unhappy coincidence of sunk costs and economic downturn forcing us all down this path. And you know what? I started learning to code—needed something to do after all. And ChatGPT and Claude started off as amazing helpful tools. Then at some point you've got the basics down and you're trying to do marginally more complex things—and you notice how quickly they lose track and fall apart, how needlessly complicated their solutions are, how your entire architecture turns into a mess of barely-functional spaghetti. Does this stuff work *anywhere*? My IT friends complain about being forced to use whatever hot new AI tool, and their companies stopped hiring junior positions. My own industry seems broken. After sending this mail, I'll have to do some tedious, underpaid post-editing. I'll hate it. Whoever will have to actually use the documents will hate it.

A thing I'm noticing is people putting together demos of things they don't understand. Use cases that nobody who's actually in that field would ever use. I think this is all further indication that we've elevated a class of people who don't do into decision-making, and the fact that they confuse language models with mental models also means they are completely out of touch with their customer base and use cases.

Via

[ related topics: Invention and Design Work, productivity and environment Heinlein Education Artificial Intelligence Architecture Economics ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.