True. I've worked on projects which required updating 3+ repos for each feature. Required carefully-timed staggered deployments.
It's often a sign of poor separation of concerns. Tight coupling and low cohesion.
On a good codebase with microservices, this should happen on rare occasions, but not every single time you add a new feature. Been there. Agreed those are particularly hard to work with using AI.
Comments
If for each story the developer needs to fetch context for 10's of micro services I could see them using a lot of tokens.
True. I've worked on projects which required updating 3+ repos for each feature. Required carefully-timed staggered deployments.
It's often a sign of poor separation of concerns. Tight coupling and low cohesion.
On a good codebase with microservices, this should happen on rare occasions, but not every single time you add a new feature. Been there. Agreed those are particularly hard to work with using AI.