> We are already past the point of anyone having a full picture of the system.
Why not split the team and each sub team is responsible for specific components and specific integrations ?
That's what's usually done when a projects starts to grow in complexity that no longer fits the brain of a single person, right?
Sure development will start to be slow because you'll need more people to sync with each other, but on the last 30 seconds I had for thinking, no other idea came up.
This is kind of what they've done with the Ethereum 2.0, "The Merge," change that they're working on now. They're splitting the consensus and the execution layers, in part to reduce complexity. I think the crux of the issue is that new fundamental components that are tightly coupled are added without putting in additional work to decouple and simplify the whole project.
Why not split the team and each sub team is responsible for specific components and specific integrations ?
That's what's usually done when a projects starts to grow in complexity that no longer fits the brain of a single person, right?
Sure development will start to be slow because you'll need more people to sync with each other, but on the last 30 seconds I had for thinking, no other idea came up.