Who Does What? Team Topologies for the Agentic Platform

The 'reading effort : meaning' ratio of this post is a bit painful.

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.

The complexity was real, and honestly that’s a good callout

"Building an application used to mean orchestrating roles over time: one person designed, another challenged the architecture, a third tested, a fourth deployed."

What? That's not my experience at all, this lost me very quickly.

Please fix your writing and make it more user friendly to the users you want to read it. As of now, it reads like unedited AI slop.

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.

[flagged]