Live data from Hacker News

What Google Translate can tell us about vibecoding

ingrids.space

31–40 of 175 posts

Re: What Google Translate can tell us about vibecoding

#31
This is like the worst comparison since generative AI is far better at conversational translation than google translate

LLM’s will tell you idioms, slang, and the point behind it

You can take a screenshot of telegram channels for both sides of a war conflict and get all context in a minute

In classic HN fashion I’m sure I missed the point, ok translators are still in demand got it.

Google Translate has been leapfrogged by the same thing that allows for “vibecoding”

Re: What Google Translate can tell us about vibecoding

#32
post #26

This 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…

The reasonable concern people have about AI eliminating coder jobs is that they will make existing coders drastically more productive. "Productivity" is literally defined as the number X of people required to do Y amount of stuff. I'm not sure how seriously people take the threat of non-coding vibe-coders. Maybe they should! The most important and popular programming environment in the world is the spreadsheet. Befor…

> everything that is today a spreadsheet was a program some programmer had to write

That is incorrect, sir.

First, because many problems were designed to fit into spreadsheets (human systems designed around a convenient tool). It is much more likely that several spreadsheets were _paper_ before, not custom written programs. For a lot of cases, that paper work was adapted directly to spreadsheets, no one did a custom program intermediate.

Second, because many problems we have today could be solved by simple spreadsheets, but they often aren't. Instead, people choose to hire developers instead, for a variety of reasons.

Re: What Google Translate can tell us about vibecoding

#33
post #27
post #26

Earlier quoted context omitted.

The reasonable concern people have about AI eliminating coder jobs is that they will make existing coders drastically more productive. "Productivity" is literally defined as the number X of people required to do Y amount of stuff. I'm not sure how seriously people take the threat of non-coding vibe-coders. Maybe they should! The most important and popular programming environment in the world is the spreadsheet. Befor…

I'm still optimistic that the net effect of making existing programmers drastically more productive is that our value goes up , because we can produce more value for other people.

The economy has taught us that when there is an excess of worker productivity, it leads to layoffs. It certainly does not lead to raises.

Re: What Google Translate can tell us about vibecoding

#34

This 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…

I'm currently getting two types of ads on YouTube: One is about how the official Israeli Gaza humanitarian efforts are totally fine and adequate (launched during the flotilla with Greta Thunberg).

The other is about an "AI" website generator, spamming every video at the start.

I wonder what kind of honest efforts would require that kind of marketing.

Re: What Google Translate can tell us about vibecoding

#36
post #32
post #26

Earlier quoted context omitted.

The reasonable concern people have about AI eliminating coder jobs is that they will make existing coders drastically more productive. "Productivity" is literally defined as the number X of people required to do Y amount of stuff. I'm not sure how seriously people take the threat of non-coding vibe-coders. Maybe they should! The most important and popular programming environment in the world is the spreadsheet. Befor…

> everything that is today a spreadsheet was a program some programmer had to write That is incorrect, sir. First, because many problems were designed to fit into spreadsheets (human systems designed around a convenient tool). It is much more likely that several spreadsheets were _paper_ before, not custom written programs. For a lot of cases, that paper work was adapted directly to spreadsheets, no one did a custom…

I'm not sure we're really disagreeing about anything here. If you think spreadsheets didn't displace any programmers at all, that's contrary to my intuition, but not necessarily wrong --- especially because of the explosion of extrinsic demand for computer programming.

Re: What Google Translate can tell us about vibecoding

#37
post #33
post #27

Earlier quoted context omitted.

I'm still optimistic that the net effect of making existing programmers drastically more productive is that our value goes up , because we can produce more value for other people.

The economy has taught us that when there is an excess of worker productivity, it leads to layoffs. It certainly does not lead to raises.

Do you have a citation for that?

Re: What Google Translate can tell us about vibecoding

#38
post #12

Earlier quoted context omitted.

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.

Also true! But that world is one where the vast majority of time is spent cleaning up slop code, so if there's a general shift towards that, I think that still changes the job in a significant way. (I don't have extensive history in the industry yet so I may be wrong here)

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.

Re: What Google Translate can tell us about vibecoding

#39
> 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

#40

This 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…

Google translate is a good example too in terms of better-than-nothing to the completely uninitiated, helpful to someone with a little knowledge, and obviously not a replacement for a professional. That is - the more you know, the more you see its failures. I know enough Japanese to talk like a small child, make halting small talk in a taxi, and understand a dining menu / restaurant signage broadly. I also have been…

[deleted]
Post reply on HN