I hate the marketing-selling-linkedn style as much as anyone, but I don't think it's an LLM thing in particular. It's a style that existed before LLMs and it's very easy to make LLMs avoid it with one or two prompt paragraphs.
For what it's worth, I didn't get that vibe reading this post.
>The strike by Alibaba is described as a "distillation" effort, which Anthropic has said involves training a less capable model on the outputs of a stronger one.
Claude used TB of content without permission to train their model and it was ok for them.
Now someone else uses the output of a Claude model to train model and they cry foul.
Latinamerican here.
When you talk about "adversarial country" I think of the USA (they can kidnap a president, kill people on boats without a trial, etc) and not China.
YMMV for different regions.
Here it's important to take into account the consequences / cost of false positive vs false negatives.
If you're building a dashboard for visualizing something fun (hot dog sales in sport games) then the corner case error has low cost. I'm happy having this vibe coded dashboard that works 99/100 and my world is better with it existing.
Crypto is on the opposite scale (and I'm surprised this blog doesn't realize it): 9999/10000 isn't good enough because the corner cases have dire consequences. So, yeah, bad example for vibe coding
Read parent's post carefully.
The post starts by saying that discussing whether they have subjective emotion is a waste of time, so the post is definitely NOT saying that Claude has emotions.
I find talking about X psychosis (or generally using mental illness metaphors) unproductive. It sets up the conversation to be "nothing else to do with this person".
Maybe the problem is you, but you won't figure that out if you think the other person has psychosis.
For example, maybe you need to do a better job explaining, changing your language, simplifying things, being more concrete with consequences.
Or maybe you aren't understanding that the other person has different objectives/ loss function that makes them make seemingly weird conclusions.
The USA has the biggest incarceration rate of any developed country.
If you say that it's hard to get the state to put you in jail, then the only way I can reconcile that with facts is that people in the USA commit crimes X10 times more than in other developed countries.
Are you talking about open source or commercial products?
I can't speak for the pytorch lighting case, but I wouldn't be surprised if the maintainers didn't get any $ from it. They would be sad if the credibility of the package suffers, but ultimately it wouldn't make a big difference to them
You can evaluate the limits of a spoon by trying to cut meat with it.
The point is what are the typical use cases for the tool / what are the agreed upon areas of application?
Making the LLM do math with large numbers, I would argue, is not in its typical use case, thought it's at the border.
Asking an image generator model to calculate numbers before running an image sounds definitely NOT like a reasonable use case (do people need it? Will people try using it for this purpose?)
"curve-fitting" has a long history (centuries old) and could be regarded more as a numerical method issue.
Rigorous understanding of what is over fitting, techniques to avoid it and select the right complexity of the model, etc, are much newer. This is a statistical issue.
My point is that forecasting isn't curve fitting, even thought curve fitting is one element of it.
Not a local, but in my experience this is due to tourists not being able to speak Japanese, which makes the people working in a place very uncomfortable ("will this person follow the rules? How can I do proper service if I can't communicate?"). A 大丈夫、少し日本語をしゃべります (it's ok, I speak a bit of japanese) has been enough to open the doors for me.
That being said, they do have issues with some nationalities. For example, the average American is way too loud for the average japanese place. Even if they think they are being polite, they just talk too loud and too much for japanese sensibilities.
I get your point, but I don't think your nit-pick is useful in this case.
The point is that you can't abstract away the details of back propagation (which involve computing gradients) under some circumstances. For example, when we are using gradient descend. Maybe in other circumstances (global optimization algorithm) it wouldn't be an issue, but the leaky abstraction idea isn't that the abstraction is always an issue.
(Right now, back propagation is virtually the only way to calculate gradients in deep learning)
>But all intelligence, of any sort, is "jagged" when measured against a different set of problems or environments.
On the other hand, research on "common intelligence" AFAIK shows that most measures of different types of intelligence have a very high correlation and some (apologies, I don't know the literature) have posited that we should think about some "general common intelligence" to understand this.
The surprising thing about AI so far is how much more jagged it is wrt to human intelligence