> stuck in a rut where each area of code only has one maintainer/gatekeeper. Why do you assume it's a rut? It might be an organizational liability but it can b

> stuck in a rut where each area of code only has one maintainer/gatekeeper. Why do you assume it's a rut? It might be an organizational liability but it can be a great while it's working. It's common folklore that design by committee leads to poor outcomes, or at best average outcomes completed slowly. Why assume that we need to build code by consensus or a series of interchangeable cogs?