Earlier quoted context omitted.
[flagged]
I'm happy to discuss arguments if you want to add any?
What it feels like to work with Mythos
91–100 of 337 posts
Re: What it feels like to work with Mythos
#92What 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.
Re: What it feels like to work with Mythos
#93Is it a hard problem or is it just labor intensive?
Re: What it feels like to work with Mythos
#94Re: What it feels like to work with Mythos
#95Earlier quoted context omitted.
now for the best question: whats your ROI here?
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
If you get $100,000 per year as a SWE, and Anthropic offers a coding model for $100,000 per year (but working 24/7), then you'll have to give up all of those addons that make the fully burdened cost of the employee. Say goodbye to vacation, sick time, benefits, etc.
Re: What it feels like to work with Mythos
#96Reading 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 th…
Re: What it feels like to work with Mythos
#97> it is indicative of AI solving a hard problem involving research, math, visual development, taste, judgement, complex coding, and more. Is it a hard problem or is it just labor intensive?
Re: What it feels like to work with Mythos
#98> 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…
> At the same time, it is very dissonant to see the industry heading towards hour+ long workflows with an agent. At this point, pay me significantly more, and I'll do it.
Ha ha, that's how you negotiate yourself out of a job!
Re: What it feels like to work with Mythos
#99Edit: A couple hours in and I just got my first gaslighting attempt from the model. Good times!
Re: What it feels like to work with Mythos
#100I am… underwhelmed by the artifacts in the post. I don’t see why working longer is a pro. The results don’t seem much better than you’d get from putting Opus in a long loop.
Care to share the results you got from Opus working on the same prompt? It should be easy to compare quality.