I believe this works very well and is what I would propose for a small team (5-8 engineers) working on related things (let say your typical react+node+mongodb s

I believe this works very well and is what I would propose for a small team (5-8 engineers) working on related things (let say your typical react+node+mongodb stack). I don't think this scales beyond that. Even with a small team it's not realistic to expect your engineer to understand both the commits in the iOS frontend, the golang backend and the AWS terraform templates. But your comment makes it clear that we should define where such workflow should be applied. One size won't fit all, especially on this regard.