AI coding has made CI a bottleneck, so we reworked ours to keep up

Re:AI coding has made CI a bottleneck, so we reworked ours t... by rsanheim on Tuesday September 22, 2026 @05:17AM (#49798437)

If we lived in a world where people or agents could define those service boundaries up front, correctly, with some reasonable foresight for change on the horizon ...then sure...I'd agree.

However, our world is not that world. Your agents may be happy in their tiny walled kingdom of toil and ineffectiveness, but you and your users will not. Poorly drawn service boundaries will drag you down more than almost any other architectural mistake.

If there is one universal amongst organizations, its that they love walls and silos. Be wary of putting them up ahead of time, cuz tearing them down once established is nearly impossible.

[ Parent | on HN ]

Re:AI coding has made CI a bottleneck, so we reworked ours t... by CharlieDigital on Tuesday September 22, 2026 @07:34AM (#49799621)

    > If there is one universal amongst organizations, its that they love walls and silos.

What's true for human organizations isn't necessarily true for agent-driven engineering. People and human teams struggle with contracts because there's always human negotiation involved. If the decisions are instead made by a team of agents, there's no more ego, ownership, miscommunications; just decisions based on whatever rules have been given to the orchestrator.

    > Your agents may be happy in their tiny walled kingdom...

Yes indeed; the agents will always be happier if they can iterate faster, ship faster, build faster, with smaller context. That would be the point of using contracts as boundaries so the agent can iterate more autonomously so long as it maintains the externally facing contract or version the contract if it needs to.

[ Parent | on HN ]