Earlier quoted context omitted.
it's basically a tiny statement that kind of hand waves all the 'actual stuff'.
It's "I did the first/easy 90% now someone else do the second/hard 90%". Same as it ever was.
What it feels like to work with Mythos
231–240 of 337 posts
Re: What it feels like to work with Mythos
#232Re: What it feels like to work with Mythos
#233Desperate to know what the prompt for the poem is. The idea of it felt familiar so I went down the rabbit hole and found: 14 years ago, a poem on reddit [ https://www.reddit.com/r/RedditDayOf/comments/tjjw2/may_12_a... ] . Nowhere near the length of the one the author shared but the same idea. > This is from "The Cyberiad", a collection of science-fiction fairy tales by Polish author Stanislaw Lem ... In one of the s…
Or it just swept it up in the training data given Anthropic license Reddit comments.
Re: What it feels like to work with Mythos
#234Re: What it feels like to work with Mythos
#235Earlier quoted context omitted.
Well that’s kind of the point. They can just summon bespoke software out of the ether that only handles the use cases of themselves and a few of their collaborators. Making “side projects” was mot possible for non-developers before powerful LLMs. Now it is.
Making side projects isn't a trillion dollar industry tho, adding to the fact that we are facing another global supply chain crisis due to the Iran War; the US is about to commit the biggest self-own ever in the history of empire.
But which self-own exactly do you mean, of the many there are?
Re: What it feels like to work with Mythos
#236Earlier quoted context omitted.
Well that’s kind of the point. They can just summon bespoke software out of the ether that only handles the use cases of themselves and a few of their collaborators. Making “side projects” was mot possible for non-developers before powerful LLMs. Now it is.
I don’t think that’s true, I think these authors are making a much stronger claim that AI is proficient or even an expert at software engineering. This author describes how complex and sophisticated their software is, and the only value he’ll concede to “coders” is that there might be a few bugs they’d need to fix. Imagine not being an architect and using Claude to put together a building plan, then concluding it’s b…
Re: What it feels like to work with Mythos
#237Earlier quoted context omitted.
Well that’s kind of the point. They can just summon bespoke software out of the ether that only handles the use cases of themselves and a few of their collaborators. Making “side projects” was mot possible for non-developers before powerful LLMs. Now it is.
I don’t think that’s true, I think these authors are making a much stronger claim that AI is proficient or even an expert at software engineering. This author describes how complex and sophisticated their software is, and the only value he’ll concede to “coders” is that there might be a few bugs they’d need to fix. Imagine not being an architect and using Claude to put together a building plan, then concluding it’s b…
The author specifically says:
> I am sure it is not perfect (I only spent an hour working with the results), but a software engineer would iron out the remaining potential bugs that I could not find quickly (which is one reason we may need more, not less, coders in the future, to help with the explosion of new uses for software)
which acknowledges pretty clearly that engineers bring a level of insight and experience still missing from Mythos. Saying that, I totally disagree with his contention that this will always be true. It's pretty weird that the author of an article stressing the steep improvements in a model's capability can't seem to imagine further improvements in that capability. As if Mythos is where development ends or whatever gap remains between models and experts won't steadily narrow or eventually widen in reverse.
Re: What it feels like to work with Mythos
#238Re: What it feels like to work with Mythos
#239Earlier quoted context omitted.
> Humans are very expensive, so the equation almost always falls against them. You underestimate what these models cost. Uber's budget is $1,500/dev/month. I gather that was put in place because the dev's were going through $6,000/dev/month, which Uber decided could not be cost justified. Fable costs at least twice as much, or $12,000/dev/month. Fable can apparently work for hours without supervision, which means a s…
Minor note, 2x $/tok is not 2x cost. Personally, I see Fable being significantly more token-efficient than Opus 4.8. Then, there's also the compounding costs of quality.
Re: What it feels like to work with Mythos
#240Earlier quoted context omitted.
Humans are very expensive, so the equation almost always falls against them. It's not just salary, but also safety/labor regulation, legal risk, vacations, sick time, personal conflicts, HR, benefits. Even when automation is more expensive on paper, it's generally still cheaper
> Humans are very expensive, so the equation almost always falls against them. You underestimate what these models cost. Uber's budget is $1,500/dev/month. I gather that was put in place because the dev's were going through $6,000/dev/month, which Uber decided could not be cost justified. Fable costs at least twice as much, or $12,000/dev/month. Fable can apparently work for hours without supervision, which means a s…
I kinda get why execs are excited