It's got all the indicators of being AI generated, so really not surprising at all. I lost track of how many "this, not that" and "this, but also" within a few paragraphs. LLMs tend to prefer sounding clever over simple terminology.
I just came here to post that I couldn't read past 'The complexity was real, but distributed'. I can get past these LLM constructions when Claude uses them in chat. They seriously undermine the credibility of comment pieces or guides like this one when I encounter them. I absolutely hate it when I get them in a lengthy response to a simple question to a colleague about why we're going to do something a particular way.
With all the roles and harnessing and boiler plate, it kind of makes me wonder if we shouldn't just spend a year or two doing genuinely good software development and then everything trained on it would be good by default?
Every time I read in some blog about an unproven technique which is profitable for token sellers I'm reminded of those overpriced restaurants that became "instagram popular" because the cool kids got paid a bundle of money to promote them.
In real life the only time I saw somebody try this "multiagentic coding" the results were...underwhelming.
I like the topic and I think orgs are struggling with the question:
What do our teams look like now?
But I have some big concerns with your approach here. This post is written like an authoritative summary but you admit it's not been seen working. Why is there so much untested conjecture presented as best practice here? If you had tested it you would realize this proposal is not possible in most orgs. Their "platform" will not be extensive enough to prevent misshaps by teams comprised of non engineers.
There are about 3 named concepts in every paragraph.
There are about 15 claims about named concept being the solution to a problem that's never explained.
At some point, if you try to make 20 different points, you make no point at all.
In real life the only time I saw somebody try this "multiagentic coding" the results were...underwhelming.
I genuinely think that multi-agent is a probable future to enable coding at the scale of a big corporation.
I agree and I did not see it work yet, but the trial were most likely on small scale where it is simply over engineering.
(Btw : I do not sell tokens. I I think distributed the work through agents in a plateform is a way to control costs by optimizing specialised agents)
What do our teams look like now?
But I have some big concerns with your approach here. This post is written like an authoritative summary but you admit it's not been seen working. Why is there so much untested conjecture presented as best practice here? If you had tested it you would realize this proposal is not possible in most orgs. Their "platform" will not be extensive enough to prevent misshaps by teams comprised of non engineers.
And there is one notable anecdotal source proving that it is possible - https://ideas.fin.ai/p/2x-nine-months-later