3 ms·
If you have 10 teams working on the same product, you probably need service boundaries. Recently I started thinking that monolith or at least monorepo is bette
by p0w3n3d 8mo ago
If you have 10 teams working on the same product, you probably need service boundaries.
Recently I started thinking that monolith or at least monorepo is better for AI development, because the context and the contract are in one place...
- nosefurhairdo 8mo agoI give my agents read permissions to all repos related to a given repo. Add a bit of context to AGENTS.md or equivalent and they do just fine with understanding service boundaries. Another concept I like is that we should optimize for next year's AI. Don't migrate to a monorepo if your only motivation is the performance of today's agents, because a year from now this may be a non-issue. Of course other motivations may still be valid.