I tend to agree. But the devil's advocate in me says that then they'd be accused of not having empathy. That sort of thing might work in Europe — but for a US company, I think you have to pay some lip service to emotions.
But then you're back at the question from the OP of "why not?" Is it lack of good examples in the training data? Is there something of code "goodness" that goes beyond phenomenon that are measurable? Is it that LLMs lack in the ability to organize and think abstractly?
Isn't that how AI written software gets better too? By steering the model towards the goals of the user?
I don't know if it's a question of how many features to feed to the model, either. Of course, overwhelm the context with too many features and it will get confused. But that's where the memory management idea that G. Huntley talks about is helpful. You're trying to steer the model within its memory limits towards a certain goal.
The problem is getting it to produce "good" code. Formalizing what that means is the task of the programmer. How do you steer a model towards always, or more often, producing good code so that you don't have to do rework? That's the same problem as with a junior engineer, but the way you do it is different. Right now we're trying to do it with mountains of prompts — which sort of works but has diminishing returns — and with onerous code reviews. We've seen this get better over time, but I think some more mechanical methods will help as we figure out how best to steer the models.
> So, why can't models do software maintainability?
I feel like the explanation does nothing to actually elucidate why models can't do it. Is it an inherent weakness of LLMs? Training processes? The typical "this is crap" that we constantly hear? It goes on to write about RL and how there's no penalty for bad design. But that sort of side-steps the question and makes you ask: "why not do RL and make a penalty for bad design?" Of course the models aren't good at it ... they're not good at anything until you've tuned them and put them in a harness that rewards good edits and throws away (improves) bad edits. That doesn't explain why "models can't do software maintainability." The real question is why harnesses can't do software maintainability, and how to build a system that can do it. (I suppose that's the purpose of the ad at the bottom of the page.)
I mean that's how I personally would define ethical. But anytime someone makes a claim like that, you have to ask "by what standard." And it's usually just "me."
Isn’t that somewhat similar to everywhere else AI is being employed? More of the same — just faster? We aren’t getting novel software architecture out of AI, those things are still important, but it does help us rule out bad things (bugs, security vulnerabilities, etc) and help us focus on the important things. In that vein, AI could help mathematicians by ruling things out faster.
Just to be clear, this doesn't mean that anything on the die actually measures 0.7nm — it means that it's roughly double the density as the previous node generation. At some point the industry decided to keep talking about "nanometers" even though the actual transistor sizes have been decoupled from the node name for years.
If resold Anthropic tokens undercut even the at-cost open-weight model tokens, because they're reselling subsidized subscription tokens, then you'd have to start selling open-weight model tokens at a loss in order to match them.
Yeah, this is relatable. Part of it comes down to "use it or lose it." We atrophy when we don't exercise. But at the same time, it might come back to the OP faster than he thinks if he went into it. Also, I've found that with AI I'm able to ask specific questions where I'm hazy and pick things up faster than if I just had to watch hours of lectures to pick something up. (There's a place for both.)
That's fair push back. In defense, my comment was motivated by the OP's assertion (multiple times) that this is merely an example of corporate greed. I don't know what the original user-agreement was, but it seems to me that common sense would say that you have to make money some way. If this business at one point offered a free service and at some point market pressures showed them that wasn't going to work, so they needed to do something else to remain solvent. Egress is not free, so merely uploading and storing is not an argument for free retrieval.
I feel like this headline is a bit over-stated. There is not a ton of evidence it was about a jailbreak, and neither was there evidence that is was about retribution.