The question of what to build rather than how is still central to development. If the article does point to success it's not as much a technical one but of product. That said I'd take these articles with a lot of grains of salt, knowing first-person how corporations spin their successes, including internally.
replyThis is quite insightful: even the best of software engineers (presumably) already are unable to even loosely keep up with these models.
replyJust a reminder to simply embrace their superior capabilities instead of feeling threatened.
> even the best of software engineers are unable to keep up with these models.
replyIt’s more likely they used an earlier version of Claude to write v1, then a later version of Claude rewrote it.
Unless Anthropic engineers were writing code by hand prior to Mythos
There actually was lot more hand-writing of the code back then! Or, at least, only moderately assisted by Claude with a lot of human-still-typing-things-in-an-editor. The ability to delegate larger chunks of code to Claude had a noticeable, step function increase with Mythos Preview.
replyOr they suffer from skill atrophy by overreliance on LLMs.
replyWas it a first version in TypeScript then rewrite to rust situation?
replyDoes it really matter since It's one-time import pipeline.
replyWe ran the repo ingestion in a loop for several months while we were split between Scion and git to keep things in sync, so this perf win was actually impactful for us!
replyAre you already operating with multiple levels of orchestrators and agents? i.e. one human talks to one or more orchestrators who then talks to orchestrators who handles teams of agents?
replyYes, this is a common pattern. There is still an opportunity to improve how these agents write code without needlessly conflicting between themselves and we are exploring some ideas.
replyRipe for optimization against maintainability, of course, but yeah it would seem to matter if that generalizes.
reply