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

151–160 of 337 posts

Re: What it feels like to work with Mythos

#151

Post by Aperocky »

patcon wrote: post #67
Aperocky wrote: post #54

> 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?

yeah the original map was not for this purpose. Though I would say there are heavy assumption made for 2026 too, namely the flights are available immediately upon demand.

Re: What it feels like to work with Mythos

#152

Post by SupremumLimit »

I took a brief look at the code for one of the projects (https://github.com/emollick/concord/) he breathlessly praises and says "a software engineer would iron out the remaining potential bugs that I could not find quickly". The code looks like an unmaintainable mess.

Other commenters have pointed out that his isochrone map contains a lot of nonsense as well.

So the most charitable interpretation here is that this is a case of Gell-Mann amnesia.

Re: What it feels like to work with Mythos

#153

Post by Tylerian »

chickensong wrote: post #140
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.

The ingredients and composition of the tarmac is the difference between having the road full of pot holes after a week of use

Re: What it feels like to work with Mythos

#154

Post by spicyusername »

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…

    the quality of produced code and the medium
A thought I have been tossing around in my head as the models get better is that it really may not matter what the code looks like.

If the observed behavior of the software is good, then the software is good. If a bug, of whatever kind, can be fixed by a model on a vibe-coded codebase, then that's a fixable bug. If there are no exploitable vulnerabilities, then the code is secure. If the performance is adequate, then the code is performant.

It simply does not matter what the code looks like if, from the outside, it does what its supposed to, and, from the inside, a model can fix the issue if one is found.

More than ever, software engineering is now really a job about making sure the code is doing what its supposed to.

And even if it DOES matter what the code looks like, you can have a model fix that too.

Re: What it feels like to work with Mythos

#156

Post by JumpCrisscross »

Qhemlomo wrote: post #71
cyanydeez wrote: post #34

Earlier quoted context omitted.

now for the best question: whats your ROI here?

It just got released, it shouldn't matter. We know this model will be cheaper and faster with time. And we have not even reached the timespan/timeframe were we have ASIC style models. OpenAI has to do something which will beat Fable otherwise Anthropic won. China currently overtakes cars, pv, batteries and very soon silicon chip making, it has all the incentive to also take over AI.

> We know this model will be cheaper and faster with time

Why? Demand for AI compute seems to be increasing faster than new production is due to come online for the foreseeable future, particularly if more-intensive models induce demand.

Re: What it feels like to work with Mythos

#157

Post by soraminazuki »

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…

Welcome to every LLM discussion in the past 2 years or so. When asked for anything of substance, we're faced with a barrage of "but humans aren't good at this too!" Very few quantifiable evidence and lots of pure rhetoric.

Re: What it feels like to work with Mythos

#158

Post by bathtub365 »

an0malous wrote: post #138
jimbokun wrote: post #118

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

Why do they even need coders to fix these bugs? It would be an order of magnitude (at least) to ask Claude to find and fix them, and it will likely be successful.

Building in the physical world has physical and time constraints that cannot be overcome, which is one of the reasons architecture (and engineering) are so important in this domain. In software development these constraints were only inherent when people were writing the majority of the software. I feel like I’m seeing what I thought were fundamental constraints being eroded by the increasing speed and correctness of these tools and it’s making me reconsider the importance of some of the values that are held by software engineering.

It’s obviously dependent on the domain and solution, but if your software can be extremely rapidly rearranged, bugs found and fixed with little effort, and features added with only a minimum prompt, I think the entire definition of technical debt has changed. I’ve been sceptical of these tools and still approach their output with caution. I also worry that, as a software developer, if more can be accomplished in less time there will be less room on this planet for software developers.

Re: What it feels like to work with Mythos

#159

Post by skydhash »

soraminazuki wrote: post #157
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…

Welcome to every LLM discussion in the past 2 years or so. When asked for anything of substance, we're faced with a barrage of "but humans aren't good at this too!" Very few quantifiable evidence and lots of pure rhetoric.

I’ve seen this pattern again and again, and I don’t bother replying. There’s also the “strong statement, and when you contradict it, they point out some particular circumstances that no one cares about”.

Re: What it feels like to work with Mythos

#160

Post by Ferret7446 »

TheOtherHobbes wrote: post #129
Ferret7446 wrote: post #76

Earlier 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

Good to know that LLMs will be removing all regulatory and legal risks, as well as creating a consumer economy that no longer employs or pays consumers. I can't help thinking there might be some kind of strategic issue here. Perhaps someone should ask Mythos about it.

By the point where we have work hours regulation for AI, all of our current debate about AI will be long irrelevant because we've clearly achieved AGI
Post reply on HN