Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What it feels like to work with Mythos

oneusefulthing.org

Post reply on HN
Print view View original

131–140 of 337 posts

Re: What it feels like to work with Mythos

#131

Post by anematode »

mohsen1 wrote: post #85
anematode wrote: post #69

Earlier quoted context omitted.

Does this not indicate that the project might not be structured in an appropriate way that allows incrementally adding features?

the setup is solid. there are thousands of tests and CI won't let things to merge if tests are failing. But overall, this is pretty normal for compilers to have this sort of "unexpected" tests failing due to some work in an area. It happened to me when I was coding everything manually back in the day too

> there are thousands of tests and CI won't let things to merge if tests are failing.

That's not what a clean setup means... I mean good separation of concerns, established invariants, etc.

Re: What it feels like to work with Mythos

#133

Post by ElijahLynn »

Loved the article!

And I'm excited to try it, but also have a fear that I will like it too much and then won't have access to it in 2 weeks... But maybe I will and maybe it will be worth it and I'll just pay a bunch of extra for it and it'll be great!

I think the article could be improved by actually sharing more feelings. I clicked on the article for feelings but I didn't see that many feelings described.

Re: What it feels like to work with Mythos

#134

Post by shimman »

jimbokun wrote: post #118
an0malous wrote: post #114

Earlier quoted context omitted.

These posts are never written by software engineers, it’s always some tech exec, retired engineer, or VC. This author is apparently a professor at the Wharton School of Management? None of these people have to ship or maintain real products, they’re just making side projects. The only decent software engineering perspective I’ve seen has been from Mitchell Hashimoto.

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.

Re: What it feels like to work with Mythos

#135

Post by torginus »

matneyx wrote: post #11
gopalv wrote: 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…

In Claude's defense (and I cannot believe I'm defending it), I know no single dev who could create what it did (Concord), from a 19-page design document, in 9.5 working hours. We're gonna go back to the days where our bosses ask why we're just sitting around, but instead of saying "compiling," we'll just say, "waiting for Claude."

I tried to read the 'design doc' - its slop full of vague platitudes and impressive sounding but impossible to pin down management speak - in short, it's slop, and I still don't really get what its supposed to do exactly.

It's some prompt engineered AI harness, that guides the AI to create stats after it researches a subject and ingests the data, but I'm not sure what is it that the tool actually does on top of this.

Re: What it feels like to work with Mythos

#136

Post by rpdillon »

cgearhart wrote: post #83
eithed wrote: 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…

I’m starting to realize that LLMs are really good at building low-stakes projects. Your questions mostly presume that the stakes are higher. The software will last a long time; the requirements will evolve; we can’t tolerate mistakes; etc. The trick to getting good at using LLMs for software is to learn how to make _all_ projects low-stakes.

This is really insightful, but I think it also extends to making the project either low stakes or low complexity. I have this lurking feeling that the preferable architecture for software will change as a result of LLMs because they're good at working on low complexity modular components more than they are on high complexity million-line code bases.

Re: What it feels like to work with Mythos

#137

Post by mplanchard »

ianm218 wrote: post #46
selfawareMammal wrote: post #30

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?

I’ve been working on implementing some common web infra type projects in Rust lately. Basically trying to use a lot of the great primatives in Rust like rustls (modern openSSL) and Tokio (async) to build memory safe or close, nginx drop in replacements. A small portion of this effort is having a high quality Lua in Rust repo. I’m using mythos to fix some of the performance issues with my Lua interpreter that gpt 5.5/…

What’s wrong with mlua?

Re: What it feels like to work with Mythos

#138

Post by an0malous »

jimbokun wrote: post #118
an0malous wrote: post #114

Earlier quoted context omitted.

These posts are never written by software engineers, it’s always some tech exec, retired engineer, or VC. This author is apparently a professor at the Wharton School of Management? None of these people have to ship or maintain real products, they’re just making side projects. The only decent software engineering perspective I’ve seen has been from Mitchell Hashimoto.

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 basically done but we might need a real architect to double check the measurements. It may even be true but I’d be skeptical if it’s always non-architects saying this.

Re: What it feels like to work with Mythos

#139

Post by eithed »

jimbokun wrote: post #116
eithed wrote: 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…

Does it matter to the people requesting the software if it acts in the way they expect?

True, but you should say that about every thing. Does it matter to you how the car drives, as long as it takes you to your destination? Well, yes, it matters: how will it deal with a crash, and if it's possible to replace a part and if anybody can just open it if you leave it outside. I will be amazed if somebody shows me their home-printed car, but if they'll try to sell it to me like a new one...

Re: What it feels like to work with Mythos

#140

Post by chickensong »

eithed wrote: 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…

You probably don't care about the ingredients or engineering of asphalt, only if the road does its job well or is filled with potholes. Outside of the software industry, nobody gives a shit about code or databases.
Post reply on HN