Man, that poem it made is terrible. Like just incredibly bad. Sure it's neat that software can make an incredibly bad poem but there is enough bad poetry in the world that we don't need it.
What it feels like to work with Mythos
61–70 of 337 posts
Re: What it feels like to work with Mythos
#62Reading the first few paragraphs of what he calls "the most sophisticated academic social science paper I have yet seen from an AI" does not impress as much as I hoped.
"Posterior beliefs about market demand are purely referencedependent: holding dollars raised constant, they track only performance relative to the founder’s self-chosen goal—jumping half a standard deviation at the threshold, responding steeply for the first ten points past it, and flattening thereafter"
Humans generally don't verbalize data this way. The summary document is also very fluffy.
Re: What it feels like to work with Mythos
#63What I find fascinating that there is so little substance in this article about the quality of produced code and the medium. Is the code documented and tested? Is it understandable and extendable? Is it secure? What language, framework, database was used? Author mentions judgement and taste - well, is the code tasteful? Will the model rearchitecture the entire thing if I ask it to add new functionality, spending anot…
I'm becoming more convinced these are questions of the Before Times. Yes, yes—heresy, I know.
Yet, I can't deny the reality that I observe working with LLMs every day. If this truly is a step-function (as some are sgguesting), then I have absolutely zero concern for the quality of the code.
Re: What it feels like to work with Mythos
#64This little line from the article scares me: "but a software engineer would iron out the remaining potential bugs that I could not find quickly"
Every sw dev knows this is a very dangerous, and unrealistic, assumption.
Re: What it feels like to work with Mythos
#65Earlier quoted context omitted.
Depends on the demographic I think. And also tells you surprisingly much about how the brain of person uttering it works. There are people that almost feel physical pain if something is unnecessarily incorrect. + That if the mental model of something is accurate, it is actually _more_ work to say something that is incorrect than just saying the correct thing.
In my mental model, "my Outlook" is the outlook instance running on my computer, on my data. My outlook crashed today. Yours might not have crashed. Similarly, my Jira contains tickets about my work, your Jira does not contain those same tickets. That might be technically the same instance on the same SaaS server, but the server I'm routed to accessing my data with my credentials turns it into "my Jira". My Jira is s…
This is completely fine, as those are your own installs, but LLMs can't be owned by the users, your Opus is the same Opus as everyone else's, your only difference is the suscription tier to their API.
If you had your own on-premises LLM, that would indeed be your LLM, and it would make sense to compare it to the on-premises LLMs of other people, as your setup particulars would affect the result.
Re: What it feels like to work with Mythos
#66Isn't it weird that we started to gauge the quality of a model by checking the vibe of the vibe coding?
Re: What it feels like to work with Mythos
#67> This is a map that shows the distance you can travel in a given length of time, and the first one was created in 1881 showing travel times from London. The first item on the article, the first thing it showed, was wrong though. It is 100% faster to go from London to New York in 1881 than Volgagrad. Or any of the Russian hinterland colored green or Turkey or Egypt.
> faster to go from London to New York in 1881 than Volgagrad
the map is for 2026, yeah?
Re: What it feels like to work with Mythos
#68>What it feels like to work with Mythos
>Looks Inside
>So I did this with fable...
What?
Re: What it feels like to work with Mythos
#69I have been using it for less than an hour so take this with a grain of salt of being excited for the new tech. In a project like mine ( https://github.com/tsz-org/tsz ) I am constantly frustrated that models were not doing enough research and were not taking into account other situations. Again and again models would produce code that would fix one thing and break 2 other tests that were "unrelated". With Fable it s…
Does this not indicate that the project might not be structured in an appropriate way that allows incrementally adding features?
Re: What it feels like to work with Mythos
#70>Ethan Mollick
Just an FYI this guy is an AI hype-beast. Some of his tweets are truly out there.