Comments by "George Helyar" (@georgehelyar) on "You Don’t Need CODE OWNERSHIP" video.

  1. After looking it up on Martin Fowler's site, "code ownership" seems to mean only a single developer can ever make changes to the files that they own. I've never had the misfortune to work anywhere that ever did that in the last 20 years so I'm not sure how popular it ever was but I think it's probably hardly used. Sure, sometimes one person writes some code and ends up being the only person ever to touch it, but that's usually just out of convenience rather than an enforced rule. What is used is e.g. a team owning a microservice, but that's not to avoid merge conflicts, it's to abstract the inner workings of one service away from its consumers, so that you don't need to know the fine details of how every part of a large system works, you can just focus on a small part of it. This apparently is not "code ownership" though. So really it's telling you not to do a thing that as far as I can tell nobody uses anyway, but it sounds like a thing that people do use. The content here is fine but the title is misleading, it never actually says what "code ownership" means in the video and there's already another video on the channel with basically exactly the same content, but with a different sponsor.
    6