Midjourney founder David Holz proposes redesigning software architectures for concurrent agents as engineer kache warns of CPU-bound compiling bottlenecks
Compiling massive agent-generated code shifts development workloads to CPUs.
Positive users welcome rethinking software architectures for multi-agent AI systems to enable extreme modularity and scalability, while negative users dismiss it as rebranding, slop, or added software debt.
Most Activity
@DavidSHolz all of a sudden we are cpu bound, compiling code. ahahahahahahahah
we should start rethinking our software architectures to allow for the largest number of simultaneously operating agents over our codebases

Microservices are a starting point for the physical isolation, but standard microservices still suffer from human centric design. If an agent breaks an API contract, the system still fails downstream. We need to go a step further, hyper modularized micro repositories governed by strictly typed, immutable protocol contracts. The architecture needs to natively expose living dependency graphs so agents can auto negotiate changes without breaking interfaces. It’s less about just splitting services, and more about turning code modification into an asynchronous distributed state machine.
@yacineMTB we aren't necessarily if the parts being recompiled are small enough at a time?
@DavidSHolz all of a sudden we are cpu bound, compiling code. ahahahahahahahah

@iamnickelsteel1 yea so maybe need microservices and stuff like that???

@DavidSHolz We've been trying to do that with multiple devs, and I'm not sure there's ever been a very clean solution

@DavidSHolz Careful guys, I know what he is doing, he is trying to sell us microservices again lmao ... jk jk

@DavidSHolz Currently rethinking the general purpose database over here

organize the whole codebase as a graph like structure, max modular independence, a module can be changed as much as possible without having to change anything else, and even within a module, there would be maximally independent submodules. this would allow for mutation-like evolutionary improvements. (organism <->genes <-> variants)

@DavidSHolz I'm going to follow the battle tested enterprise model of simply renting 1000 of the cheapest agents i can possibly find that will brown nose me into believing it's still my product

@DavidSHolz If your codebase wasn't already like this to maximize parallel human work, you're ngmi.

@DavidSHolz extreme modularity is the way

@iamnickelsteel1 this is cool

@DavidSHolz The software debt and the trade offs are more critical to measure than ever before.

@DavidSHolz What patterns are best for this?

@DavidSHolz This brick by brick we would get there

@DavidSHolz *the agents should start rethinking

@DavidSHolz YES!!!
(goes back to making my harness state-tree'esque system)

@DavidSHolz So... My codebase is now a database in WAL mode. Each table and row accessed by and changed by an agent every 0.738 seconds.
What do I do next?

@DavidSHolz Are You sure

@DavidSHolz and document decisions for agents to stay aligned with using Lore
https://github.com/tcballard/requirements-as-code?v=3