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.
What I mean to say is that AI ghost writing is fine (I see the comment by the author). Deciding not to read poorly written content is also fine (and there's a reason why writing style has been discussed as long as the printed page has existed).
With the speed at which HN readers can identify mass produced, AI-generated word salad, it is insightful to look at a what users aren't able to stand back from their outputs and view them from the intended audience perspective
Yes, what it's doing is using continuation phrases. It wants to continue, and these token-combos, like Tekken 4, let it move from one gradient descent to the next, and like Tony Hawk, perform combo after combo, so it can just keep producing tokens.
Because thats how they're trained. In another thread, someone wished they'd taught the models "I dont know" and were extremely convinced that some how you could train a model to stop producing tokens, or whatever. You can't both train the model to generate output and also teach it not to. That's their whole bag of tricks.
But it's not trying to be clever, it's trying to keep generating.
I usually follow Divio’s documentation to reference explanations and references, but it is not suitable for a blog post
With all due respect, it shows. You have the ability to write way better than this.
I was halfway through and thought to myself, "Why is this so fucking hard to understand the author's point?"
The subject sounds extremely timely and important and is something HN readers really crave, but the rambling article just isn't doing it justice.
Which then gives you great insights like
"a team can only be effective if it carries no more complexity than it can absorb."
What? That's not my experience at all, this lost me very quickly.
I'm sure the author means well, but it comes off as someone who lacks real-world experience sharing what they think is an ideal team structure when building apps.
That's just my opinion, but yeah, the article doesn't resonate with my experience at all, and I've been at this a while.
In real life the only time I saw somebody try this "multiagentic coding" the results were...underwhelming.
And there is one notable anecdotal source proving that it is possible - https://ideas.fin.ai/p/2x-nine-months-later
"Productivity is the efficiency with which resources (like time, labor, and capital) are converted into useful goods and services"
So they increased productivity "number of PRs". Shipping more does not guarantee shipping better or more impactful features. Many orgs are constrained by product decisions, not engineering speed.
If there was so much value to unlock through AI then why did Intercom/Fin sell to Salesforce?
ref: https://www.salesforce.com/news/press-releases/2026/06/15/sa...
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.
I don't think you should avoid sharing it in any forum. Like I said it seems like a reasonable idea but I would just suggest being very I suppose blunt in 2026 because people skim and won't read things thoroughly. I would preface the article with "this is not battle tested"
Lest someone be frustrated when their stream aligned team accidentally exposes your whole company's email addresses on their new web app that whoops they forgot put it behind a login.