Earlier quoted context omitted.
> could I get a latte today actually To me (non-American) the above sounds like sarcasm, not politeness. Adding "today" and/or "actually" could mean you've had it with their delays. I like to joke that Americans always seem to find ways to get offended by innocuous things, but in this case the joke is on me.
I would think that it depends on the context. To me it seems (without any context) that it might mean that you changed your mind about what day you wanted it. This does not seem to make sense in many contexts, though.
What Google Translate can tell us about vibecoding
91–100 of 175 posts
Re: What Google Translate can tell us about vibecoding
#92Re: What Google Translate can tell us about vibecoding
#93The distinction between what people typically imagine a translator's job is and the reality reminds me of pixar movies being "localized" instead of just translated (green beans on a plate in the Japan release instead of broccoli because that's the food that Japanese kids don't like). Lacking cultural context while reading translated texts is what made studying history finally interesting to me.
Another infamous example is Brock's "jelly filled donuts" in pokemon https://knowyourmeme.com/memes/brocks-jelly-doughnuts
First, the Pixar thing was green pepper, not green beans: https://www.businessinsider.com/why-inside-out-has-different...
Second, the Pixar one is not "mere" translation; it is full localization because they changed the visual to match the "textual" change.
The Pokemon one is where the change was limited to the "text". The translator's heart might have been in the right place (it would depend on how integral to the story it is that the item is onigiri) but didn't have the authority to make the full breadth of changes needed for such adaptation to be successful.
Re: What Google Translate can tell us about vibecoding
#94> ... a translators’ and interpreters’ work is mostly about ensuring context, navigating ambiguity, and handling cultural sensitivity. This is what Google Translate cannot currently do. Google Translate can't, but LLMs given enough context can. I've been testing and experimenting with LLMs extensively for translation between Japanese and English for more than two years, and, when properly prompted, they are really go…
You just created the software for a profitable business. People would use that and pay for it.
Re: What Google Translate can tell us about vibecoding
#95> ... a translators’ and interpreters’ work is mostly about ensuring context, navigating ambiguity, and handling cultural sensitivity. This is what Google Translate cannot currently do. Google Translate can't, but LLMs given enough context can. I've been testing and experimenting with LLMs extensively for translation between Japanese and English for more than two years, and, when properly prompted, they are really go…
It can be as simple as discuss one’s own religion
Re: What Google Translate can tell us about vibecoding
#96Fantastic closing paragraph! Loved the article
Re: What Google Translate can tell us about vibecoding
#97This article is spot on about a lot of things. One thing I think it fails to address is this: > I feel confident in asserting that people who say this would not have hired a translator or learned Japanese in a world without Google Translate; they’d have either not gone to Japan at all, or gone anyway and been clueless foreigners as tourists are wont to do. The correlation here would be something like: the people usin…
Conversely, it may create jobs. Why? Because the more elephants you have in your parade, the more jobs there are for folks to walk behind them with a broom and bucket. For decades we've seen tools that "let users write their own software" and every one of them has driven up the demand for people to clean it up, make it scale, make it secure, or otherwise clean up the mess.
Re: What Google Translate can tell us about vibecoding
#98> ... a translators’ and interpreters’ work is mostly about ensuring context, navigating ambiguity, and handling cultural sensitivity. This is what Google Translate cannot currently do. Google Translate can't, but LLMs given enough context can. I've been testing and experimenting with LLMs extensively for translation between Japanese and English for more than two years, and, when properly prompted, they are really go…
The problem with LLMs for translation is when they refuse to do so if the topic being translated isn’t following their policies, even if the context shows it’s fine here. It can be as simple as discuss one’s own religion
Re: What Google Translate can tell us about vibecoding
#99> At the dinner table a Norwegian is likely to say something like “Jeg vil ha potetene” (literally “I will have the potatoes”, which sounds presumptuous and haughty in English) where a brit might say “Could I please have some potatoes?”. I find “I will have the potatoes” to be perfectly fine English and not haughty in the slightest. Is this a difference between British English and American English?
Re: What Google Translate can tell us about vibecoding
#100Earlier quoted context omitted.
It's all cleaning up slop code. Always has been. More optimistically, you can think of "user created code" as an attempt at a design document of sorts; they were trying to tell you (and the computer) what they wanted in "your language". And that dialog is the important thing.
Seriously. Unless you're one of the vanishingly rare few working with true Greenfield projects that start with an empty text file, you're basically cleaning up other developer's legacy slop.