The idea that one person can handle 95% of a complex migration alone sounds great on paper but feels like a recipe for disaster in practice. It's fine if you have a tiny codebase, but once things scale, you can't just ignore the rest of the team.
>Even complex, large changes can be 95% owned by the driving individual or team, and done in 10% of the time.That speed is exactly how you end up with broken mental models for everyone else. I've seen too many "quick" migrations leave a trail of edge cases that take months to clean up because nobody checked the downstream effects. The point about the development harness being the real bottleneck makes sense though. If your CI/CD and testing environments are trash, it doesn't matter how fast you can type code. Everything becomes much more expensive when you're constantly debugging broken builds. It's all about that
initial cost of getting things right the first time. I just don't see how this works without massive oversight or some really heavy automation. **Good luck with those edge cases
article:
https://lethain.com/revised-rules-of-engineering-leadership/