Live data from Hacker News

What it feels like to work with Mythos

oneusefulthing.org

31–40 of 337 posts

Re: What it feels like to work with Mythos

#31

Earlier quoted context omitted.

Your Opus 4.8? Is it now usual to refer to LLMs like that?

Isn't it common to refer to all software like that? "Let my look at my JIRA", "I can't find anything using my Outlook's search function", "My Powerpoint is acting up today", "My browser just crashed" are all sentences I might say during a normal work day

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.

Re: What it feels like to work with Mythos

#32
post #9

> It worked for nine and a half hours. > Again, it wasn’t perfect. As an expert, I was able to spot some errors and omissions (some as a result of the design I had asked for) that I had the AI correct That's the bit that stuck out to me - that's longer than I would expect to work on a problem in a day or even expect to go back & fix the output of something that has a core reward loop of hours. My customers are curren…

I think we hit the sigmoid back when the QWEN models were released. By properly structuring my project, I can point it at any extension I want and get it going for 30 minutes to extend whatever. It can't effectively do 'god mode' on all the code, but being a mindful observer and code "professional" I don't need more than what a 128GB VRAM needs.

I'm amazed we're so far into SOTA bloat that the chinese will kill once they start etching silicon with these models.

Re: What it feels like to work with Mythos

#33
What it feels like to work with Fable:

> Switched to Opus 4.8: Fable 5 has safety measures that flag messages on most cybersecurity or biology topics. They may flag safe, normal content as well. These measures let us bring you Mythos-level capability in other areas sooner, and we're working to refine them. Send feedback or learn more.

Re: What it feels like to work with Mythos

#34

Anecdote: I fed Fable some models I’ve been hand verifying (basically, I sketch out a scenario for Opus to model, it builds it, I ask it to show me the math, I correct it, we iterate like this, then I double check its code to make sure the math matches the model logic). Fable found almost every error I found, and then had some interesting suggestions for additional variables. It also burned through my usage quota lik…

now for the best question: whats your ROI here?

Re: What it feels like to work with Mythos

#35

What are people working on that they see such a substantial difference between Mythos and Opus? I'd say I'm working with advanced stuff and more than often Deepseek is even more than enough. Why is everybody a genius in here?

We see the same thing when new laptops are announced and every employee all of a sudden needs to upgrade, despite the fact that 90% of people would be able to make do with a Macbook Neo.

Re: What it feels like to work with Mythos

#36

Earlier quoted context omitted.

My Opus 4.8 regularly works for 10+minutes on a single non-trivial coding request.

Your Opus 4.8? Is it now usual to refer to LLMs like that?

That's pretty tame, if you want to be disturbed check out r/MyBoyfriendIsAI

Re: What it feels like to work with Mythos

#37
post #6

I think Qwen 3.7-Plus is better at reasoning than Mythos, and I've used both for quite a while.

Would love to see samples of the kinds of prompts you use with both. I sometimes wonder if the specific wording is the secret sauce, I have very few issues with Opus / Claude, but when I try premier GPT models, I get weird output from what I've grown to expect with Claude.

Re: What it feels like to work with Mythos

#38
What 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 another 9.5h in tokens? I assume that the research part is domain knowledge = how different types of travel translate to time making it presentable; how did the author verify this?

These questions are even not about AI: if I were to give money to a human agency and were given something they tell me works, I would ask the same questions. If I did not know how to evaluate, I would hire people that do. With LLMs the verification part is what bothers me the most.

Re: What it feels like to work with Mythos

#39

Earlier quoted context omitted.

Your Opus 4.8? Is it now usual to refer to LLMs like that?

Isn't it common to refer to all software like that? "Let my look at my JIRA", "I can't find anything using my Outlook's search function", "My Powerpoint is acting up today", "My browser just crashed" are all sentences I might say during a normal work day

better than "The JIRA" , or "The Google" or "The Spotify"

Re: What it feels like to work with Mythos

#40
post #38

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

Being the first to release an article gives you great SEO or whatever. Doing the things you've mentioned takes time.
Post reply on HN