Now Everyone is Enterprise
I tried to run three agents on the same codebase last week. In Parallel. One for adding a feature. One for fixing a bug. One for refactoring a module I'd been avoiding. Within minutes, two of them had edited the same file, the third was working against assumptions of the code that were changed by the first, and I was sitting there, resolving merge conflicts on a Saturday like an idiot.
Congratulations, my weekend project is now enterprise software.
Software that's being used accumulates friction. The best decisions of the past haunt you with every new requirement. The natural reaction is to compartmentalize - abstract things into layers so they're easier to reason about and more flexible to change. And as a side effect, the source code becomes dispersed enough that multiple people can work on it without stepping on each other's toes. That's the whole origin of enterprise software best practices: maximum decoupling for the sake of human parallelism.
But what if, instead of humans, there's an unlimited amount of AI coding assistants at your disposal?
The same rules apply. Agents step on each other's (proverbial) toes due to either modifying the same files at the same time, or merge conflicts if we're working with git worktrees or branches. The solution is the same: more abstraction, more compartmentalization, more decoupling.
So after my Saturday of shame, I did something I never thought I'd do for a side project: I actually sat down and drew boundaries. Separated modules behind clean interfaces. Unguard in CI so agents couldn't commit the kind of slop I'd been catching by hand. I even moved my backend to use Effect, which felt like massive overkill until I ran three agents again and got three clean PRs back.
Internal architecture quality is now a real multiplier for how fast and for how long you ship. A well-structured codebase with clear boundaries lets you hand five tasks to five agents and get five pull requests back. A tangled one lets you hand five tasks to five agents and get one usable result and four conflicts.
Software of all sizes now has huge incentive to build in an enterprise-y way. The patterns always existed for parallelism. We just didn't have cheap parallelism before.
Now we do. Even for your fifth side project that you promised to ship a month ago.